Re: [csswg-drafts] New name for `app-region` property? (#13102)

The CSS Working Group just discussed ``New name for `app-region` property?``, and agreed to the following:

* `RESOLVED: rename to window-drag:none|move`

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> diekus: I think next two item sin agenda are related. start with app-region name<br>
&lt;TabAtkins> diekus: we have convo at TPAC. as reminder, app-region property sets an element to being the drag target for a window, in a standalone app page<br>
&lt;TabAtkins> diekus: two issues came out of the meeting in tpac<br>
&lt;TabAtkins> diekus: first, as Tim pointed out, app-region isn't very descriptive<br>
&lt;TabAtkins> diekus: we started an issue to look for new names<br>
&lt;TabAtkins> diekus: I think there's a vibe to window-drag<br>
&lt;fantasai> +1<br>
&lt;fantasai> much clearer<br>
&lt;TabAtkins> diekus: so if people are okay with that, great, or if people have other ideas to discuss<br>
&lt;astearns> ack fantasai<br>
&lt;Zakim> fantasai, you wanted to ask about values<br>
&lt;TabAtkins> fantasai: window-drag sounds way clearer, +1. what are the proposed values?<br>
&lt;TabAtkins> diekus: drag | nodrag<br>
&lt;smfr> q+<br>
&lt;TabAtkins> astearns: we don't usually repeat part of the property name in the values<br>
&lt;dbaron> TabAtkins: border-collapse: collapse<br>
&lt;TabAtkins> TabAtkins: not true, we have several properties that do so. border-collapse:collapse<br>
&lt;bramus> `nowrap` is another one<br>
&lt;dbaron> smfr: background-repeat: no-repeat<br>
&lt;astearns> ack smfr<br>
&lt;TabAtkins> smfr: background-repeat:repeat<br>
&lt;tantek> box-sizing is another example of such naming with content-box and border-box<br>
&lt;TabAtkins> smfr: is this doing anything on platforms that don't have a window dragging concept? like on mobile<br>
&lt;fantasai> I like the suggestion in the issue for `none | move`<br>
&lt;TabAtkins> diekus: I think it's scoped to the idea of desktop paradigm<br>
&lt;TabAtkins> diekus: if you have an app that can behave like a desktop environment, it might work there. but it woudln't do anything in an environment where you don't move the frame of a window, like on phones<br>
&lt;astearns> ack fantasai<br>
&lt;TabAtkins> fantasai: on value naming, there was a none|move suggestion, think that's reasonable<br>
&lt;fantasai> window-drag: none | move<br>
&lt;TabAtkins> (I do like avoiding the ugly "nofoo" pattern we've shackled ourselves to)<br>
&lt;TabAtkins> astearns: Kevin had another suggestion, is that okay?<br>
&lt;lwarlow> +1 to none and move<br>
&lt;TabAtkins> kbabbitt: I'm happy with window-drag:none|move<br>
&lt;TabAtkins> smfr: is this applied on an element basis?<br>
&lt;TabAtkins> diekus: yes, but that's related to next issue<br>
&lt;TabAtkins> smfr: I feel like at some point we'll want clip-region, etc...<br>
&lt;TabAtkins> diekus: oh, no, if you put this on something round it'll be a round target. the pretend rectangle corners won't be drag handles<br>
&lt;TabAtkins> smfr: okay, so it follows border-shape and respects clip-path? normal hit-testing rules.<br>
&lt;TabAtkins> diekus: correct<br>
&lt;TabAtkins> astearns: proposed resolution: rename to window-drag:none|move<br>
&lt;lwarlow> +1<br>
&lt;TabAtkins> +1<br>
&lt;TabAtkins> RESOLVED: rename to window-drag:none|move<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13102#issuecomment-3780122829 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 17:53:43 UTC