- From: Robin Métral via GitHub <noreply@w3.org>
- Date: Thu, 18 Sep 2025 10:45:55 +0000
- To: public-css-archive@w3.org
@mirabilos a feature with known pitfalls doesn't warrant its removal from the spec. Even if it did, a breaking change would go against the [first design principle](https://www.w3.org/TR/2007/WD-html-design-principles-20071126/#support-existing-content) of the web: support existing content, a.k.a. don't break things. Quoting from the design principle: > the fact that something is part of the supported language does not by itself mean that relying on it is condoned or encouraged I think this is the situation we're in. How about giving feedback on @NightFurySL2001's suggestion in https://github.com/w3c/csswg-drafts/issues/3658#issuecomment-3303510348 for the phrasing of a warning about `system-ui` use? (actually, maybe it's time to open a PR?) Once we have something we're satisfied with in the spec, I'm happy to open a PR on [mdn/content](https://github.com/mdn/content) to reflect it over there and make the problems more visible to authors (not everyone reads specs). -- GitHub Notification of comment by robinmetral Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3658#issuecomment-3306768668 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 18 September 2025 10:45:56 UTC