- From: Sebastian Zartner via GitHub <sysbot+gh@w3.org>
- Date: Mon, 25 Dec 2023 21:58:59 +0000
- To: public-css-archive@w3.org
> > That is my point. To allow CSS to detect HTML features, the engines need to have some kind of registry it can use and check against. Additional standardization across user agents don't seem to be necessary, engines only need to ensure their registries are consistent and kept up-to-date. > > If engines already had a registry that they are already using I would be happy to leverage it, but the current registries that are available are not great. I obviously don't understand enough about the internals of the engines. Though I am wondering why engines e.g. have a consistent registry for CSS properties but not for HTML elements and attributes they can handle. And a way to test for those features would pave the way for WPTs to test for them. And by having tests for all the different HTML features, we avoid the issue of implementations becoming outdated and push them towards introducing proper registries, so they don't have to manually maintain them. > I still stand by my point that any mechanism used here should be required to be kept up to date by design. @nt1m Which other mechanism than the above could you imagine that allows for a comprehensive solution? Should the HTML spec. maintain machine readable definitions for all HTML elements and attributes? Sebastian -- GitHub Notification of comment by SebastianZ Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9746#issuecomment-1869129980 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 25 December 2023 21:59:02 UTC