- From: Aleksandr Hovhannisyan via GitHub <sysbot+gh@w3.org>
- Date: Wed, 11 Jan 2023 19:55:35 +0000
- To: public-css-archive@w3.org
Just thinking out loud beyond this issue: Maybe there needs to be more granular versioning for CSS (and HTML) in the future so that authors can opt into new behaviors without user browser versions introducing breaking changes. Imagine if authors could set a meta tag in their document opting into `css3.x.y` and incrementally adopting new features like they would with an open-source library, so long as the user's browser version supports that new feature. This way, an old project running jQuery wouldn't have to worry about naming clashes—it could just lock the CSS version to the one before `:has` was introduced. (I understand that this is likely a lot harder to achieve in practice than it sounds. I also understand that this clashes with the cross-browser developer experience that we're all familiar with, where features are tied to browser versioning and not author-specified versions.) The change here was harmless. I'm just not sure how backwards compatible the CSS spec will need to be moving forward so that it doesn't accidentally introduce breaking changes or conflicting behaviors for older, unrelated technologies that were ahead of their time and supported syntaxes that CSS itself did not yet have. -- GitHub Notification of comment by AleksandrHovhannisyan Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7676#issuecomment-1379407272 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 11 January 2023 19:55:36 UTC