- From: Diego Gonzalez via GitHub <noreply@w3.org>
- Date: Thu, 12 Mar 2026 12:15:28 +0000
- To: public-css-archive@w3.org
Hola @kyerebo! I don't particularly agree on the comment above. I believe if we're going to standardize this property we have the opportunity to make it better. Yes, naming is hard, but in this case we didn't name the property. When we discussed about this renaming we always knew there needed to be a transition plan to deprecate the old `app-region` and `-webkit-app-region`. These might be shipped, but they're not standardised and unless I am mistaken, they're not particularly well documented. I don't think this resolution should be reconsidered, as we have a chance to improve and comply with the web platform design principle [2.3](https://www.w3.org/TR/design-principles/#name-thoughtfully) of naming things throughly. I rather have a deprecation plan on Chromium than spreading a confusingly named property onto Webkit and Gecko, if this makes sense. WDYT? -- GitHub Notification of comment by diekus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13102#issuecomment-4046287433 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 12 March 2026 12:15:29 UTC