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

Thanks for the quick response, I get the motivation to make the name more intuitive and align with the web platform design principles around naming. The hesitation isn’t really about whether `window-drag` is a better name in isolation, but about when this change is happening. Standardization (and any renaming) should have happened before unprefixing, which would have allowed us to settle on the right name without compatibility risk. In this case, the naming decision effectively happened when we unprefixed `-webkit-app-region`, and at that point developers started to adopt app-region as the unprefixed surface. From my understanding, that was the moment where a rename would have made the most sense. At this stage, it feels like reopening a decision that users have already acted on.
 
I also don’t think the existence of adoption should be discounted just because the property wasn’t standardized yet. In practice, developers see an unprefixed, shipped feature as “real,” regardless of spec status or documentation quality. A rename now primarily shifts cost onto existing implementers and developers. So, while I understand the desire to avoid spreading a confusing name further, I’m not convinced that a rename at this point actually nets out as a platform improvement given the transition and deprecation burden it introduces.

-- 
GitHub Notification of comment by kyerebo
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13102#issuecomment-4056604158 using your GitHub account


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

Received on Friday, 13 March 2026 17:03:16 UTC