- From: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
- Date: Tue, 07 Nov 2023 23:11:56 +0000
- To: public-css-archive@w3.org
> I don't know how CSSWG could impact this On the one hand CSSWG can't tell browsers what features to implement. On the other hand CSSWG is _mostly_ browser vendors. Maybe more to the point, user styles are (currently) designed for a more 'preference'-like use-case, which browsers do support through limited GUI forms. To do real custom overrides from the user origin, you'd be back in the world of `!important`. Or we'd need some other extension to user origins, which browsers and users find compelling. > Also, all of this only covers one of the cases Yep. Totally. --- But to back up through some of the previous discussion here, and maybe reframe the feature request… Assigning unlayered styles a universal-but-custom priority is what causes many of the issues, because 'unlayered' is a shared default. Usually, each stylesheet can namespace its own layers, and avoid conflicts when needed. But you can't name a layer that isn't there, and you shouldn't be moving around a layer that every other stylesheet treats as a default. Change its position for one stylesheet, and it breaks for others. If every stylesheet has the same layer, it's the default layer, and anyone can move it around…? That gets pretty confusing and unreliable. But the ability to _layer a stylesheet_ is localized, it doesn't impact other unlayered styles, and it doesn't even impact the relation between layered and unlayered styles _inside that stylesheet_. Stylesheets remain internally consistent, even when layered. So it's already possible to position unlayered styles in the cascade layer order, right? The solution to unlayered styles might just be… layering those styles? For the individual user cases, I think that should be possible for JS to do on the client side? Which an extension would be perfect for, since it can guarantee layer support. And applications like mastodon and wordpress can start layering their own styles, if they want to expose customization features to their users? I hope they do! I know Wordpress has active discussions about it. So the only remaining question might be: can I as a masto admin override what Mastodon provides as part of their app? Which… I'm not sure if that makes sense as a CSS feature? Isn't that a feature request on the applications themselves? -- GitHub Notification of comment by mirisuzanne Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6323#issuecomment-1800349286 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 7 November 2023 23:11:58 UTC