Re: [csswg-drafts] Standardizing `app-region` for draggable app windows (#7017)

The CSS Working Group just discussed `app-region for draggable app windows`.

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> Topic: app-region for draggable app windows<br>
&lt;astearns> zakim, open queue<br>
&lt;Zakim> ok, astearns, the speaker queue is open<br>
&lt;fantasai> diekus: windows have default ux for moving<br>
&lt;fantasai> ... several APIs to expand the viewport area<br>
&lt;fantasai> ... when api is enabled, can do things like create custom title bars<br>
&lt;kbabbitt> github: https://github.com/w3c/csswg-drafts/issues/7017<br>
&lt;fantasai> ... but then the default dragable area disappears<br>
&lt;fantasai> ... so propose to specify app-region<br>
&lt;fantasai> ... [shows slides that expands the viewport area, losing the titlebar area]<br>
&lt;fantasai> ... This exists, but no definition of how ti exists<br>
&lt;fantasai> ... And this is the behavior. It's enabled only when default platforms UX is not visible<br>
&lt;ntim> q+<br>
&lt;fantasai> ... works for inline and block elements<br>
&lt;fantasai> ... property consumes all pointer events<br>
&lt;fantasai> ... can use it to drag the window etc.<br>
&lt;astearns> ack oriol<br>
&lt;fantasai> ... won't work if it is overlapped by other elements<br>
&lt;fantasai> ... works even when animating<br>
&lt;fantasai> ... suppose here I have a button in the middle of the window, I set app-region on it, andI can use it to drag the window<br>
&lt;astearns> q+<br>
&lt;fantasai> ... propose to spec it in css-ui-4<br>
&lt;hober> q?<br>
&lt;hober> q+<br>
&lt;fantasai> ntim: Multiple things to think about<br>
&lt;fantasai> ... what happens if you put no-drag and then child is drag<br>
&lt;fantasai> ... does the property inherit, what wins?<br>
&lt;astearns> ack ntim<br>
&lt;fantasai> diekus: Depends on which element absorbs the pointer events<br>
&lt;fantasai> ntim: I implemented moz-window-dragging for GTK port, so some prior art<br>
&lt;fantasai> emilio: Gecko has similar property. We don't expose it to Web content<br>
&lt;fantasai> emilio: for PWA cases makes sense<br>
&lt;fantasai> emilio: If you have a native titlebar, is this property expected to work?<br>
&lt;fantasai> diekus: no<br>
&lt;ntim> q+<br>
&lt;fantasai> diekus: before you enable window controls overlay, you can define the drag region<br>
&lt;fantasai> emilio: That's weird. E.g. macos has toolbar where you have native titlebar, and toolbar, but the toolbar is also draggable<br>
&lt;fantasai> diekus: I fyou want to create that effect in a PWA you would enable window controls<br>
&lt;fantasai> diekus: It's used to create a custom titlebar<br>
&lt;jyasskin> +1 emilio<br>
&lt;fantasai> emilio: Annoying if I have to rebuild a titlebar in order to drag the toolbar<br>
&lt;fantasai> emilio: In Gecko if you drag anywhere in the toolbar, it also take sthe window, not just the titelbar<br>
&lt;fantasai> diekus: you could move from any element you set it on<br>
&lt;fantasai> diekus: but the titlebar would have to be off<br>
&lt;fantasai> emilio: that seems unfortunate<br>
&lt;fantasai> astearns: Is this a -webkit- property?<br>
&lt;astearns> ack astearns<br>
&lt;fantasai> ntim: It was unshipped from Safari<br>
&lt;astearns> ack hober<br>
&lt;fantasai> hober: Yeah, it was asserted that it already exists. It's not actually all the things.<br>
&lt;fantasai> ntim: It's only shipping in Chrome apparently<br>
&lt;fantasai> ntim: I don't think app-region is a good name for this<br>
&lt;astearns> ack ntim<br>
&lt;fantasai> ntim: Could reuse for other things<br>
&lt;fantasai> diekus: agree the name is not descriptive at all<br>
&lt;fantasai> diekus: but do we agree on having the behavior?<br>
&lt;emilio> q+<br>
&lt;astearns> ack fantasai<br>
&lt;emilio> fantasai: This seems something that should be inherited<br>
&lt;emilio> ... so that you can put on and off<br>
&lt;astearns> ack emilio<br>
&lt;fantasai> ... and only affects element you set it on<br>
&lt;fantasai> ... that would solve the toolbar case, as long as it works even with titlebar<br>
&lt;adamargyle> maybe just a new touch-action value?<br>
&lt;fantasai> diekus: details in explainer<br>
&lt;fantasai> astearns: Anyone in the room to oppose this feature? Is this not something to work on?<br>
&lt;fantasai> hober: I'd have to ask ppl in the wrong time zone<br>
&lt;fantasai> astearns: Given in one engine, was in anotther, and third has something similar...<br>
&lt;fantasai> hober: unsure it was ever in safari<br>
&lt;fantasai> astearns: Answer seems to be "maybe"<br>
&lt;fantasai> diekus: as long as it's fine overall, I can write the spec text<br>
&lt;fantasai> emilio: fine to work on it. issue on name, inheritance, when it applies<br>
&lt;fantasai> astearns: We'll work on this and decide if it goes into a draft or not<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7017#issuecomment-3526122905 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 13 November 2025 07:44:11 UTC