- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Wed, 21 Jan 2026 18:02:32 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed ``Define possibly inheritable behaviour for `app-region` ``, and agreed to the following: * `RESOLVED: window-drag is inherited` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> diekus: next is related<br> <TabAtkins> diekus: we had talked in tpac about looking at the inheritance behavior, so I opened an issue<br> <TabAtkins> diekus: doing a bit more research, I think the behavior is something that should inherit, and you can choose which parts of the UI you can use for dragging or not.<br> <TabAtkins> diekus: but we hit another interesting point. in some OSes like Linux, some apps like Firefox, they have a similar behavior that happens without the default triggering<br> <TabAtkins> diekus: recall, to enable this behavior, the default UX for dragging windows...<br> <TabAtkins> diekus: Emilio brought up a point that in some OSes this isn't the behavior<br> <TabAtkins> diekus: we got to a point where there's no breaking change in apps that are already using window dragging, when we add this feature<br> <TabAtkins> diekus: so first we want to confirm that making this inherited is fine<br> <TabAtkins> diekus: and second to confirm that we *remove* the idea that using this removes the default dragging behavior for an app, so you can still drag from the menu bar or whatever if that's the default on the OS<br> <astearns> ack fantasai<br> <TabAtkins> fantasai: confirming I understand<br> <TabAtkins> fantasai: first is, property is inheritable.<br> <TabAtkins> fantasai: second, property takes effect regardless of whether other window control APIs are working<br> <smfr> q+<br> <TabAtkins> diekus: yes, with the caveat that it depends on the OS supporting the concept<br> <fantasai> s/are working/have been used to enable or disable normal window controls/<br> <TabAtkins> diekus: before you had to trigger the specific API that removes the title bar, and *that's* what allowed this API to start working. But Linux works differently, you can still drag via menu bar *and* potentially from spots inside<br> <astearns> ack smfr<br> <TabAtkins> diekus: so we want to match that<br> <TabAtkins> smfr: so in any OS that supports window dragging, you can put an element in the middle of the page that allows dragging the window around?<br> <TabAtkins> fantasai: yes, but not in a browser. it needs to be a standalone app<br> <TabAtkins> smfr: okay, how does that get enabled?<br> <tantek> does it apply to native app embedded webviews?<br> <TabAtkins> diekus: on Macos you can add a webapp to the dock, and if your app allows title bar dragging...<br> <astearns> ack fantasai<br> <TabAtkins> TabAtkins: yeah there's already a CSS feature that exposes this, letting a page specify whether, when it's saved as an "app", it's displayed in the browser or as standalone or wahtever<br> <fantasai> https://drafts.csswg.org/mediaqueries-5/#display-modes<br> <TabAtkins> fantasai: there's display-mode MQ related to that<br> <TabAtkins> fantasai: several modes listed in here. are there specific modes that allow this?<br> <TabAtkins> florian: yes, and I think it's set via the app-manifest<br> <TabAtkins> diekus: yes, certain modes are standalone. "standalone", "minimal-ui"<br> <lwarlow> q+<br> <TabAtkins> diekus: so long as the app is running in its own window, this will work. if it's in a tab it won't.<br> <TabAtkins> astearns: overtime, let's get the resolution in<br> <florian> I support it being inherited<br> <TabAtkins> lwarlow: I was assuming it only applies in standalone and minimal-ui, not Fullscreen?<br> <kbabbitt> +1 to it being inherited<br> <TabAtkins> diekus: yes<br> <lwarlow> +1<br> <TabAtkins> astearns: objections to making it inheritable?<br> <TabAtkins> RESOLVED: window-drag is inherited<br> <TabAtkins> astearns: rest can be a separate issue, or just editorial<br> <TabAtkins> fantasai: maybe in the issue we can clarify which display modes have this work, that would probably make it easier to define<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13101#issuecomment-3780196874 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 21 January 2026 18:02:33 UTC