-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is this spec ready to move into a main W3C working group? #74
Comments
I think it's actually past time it moved to a WG (and the CSSWG is a good one). Regardless of whether there are bugs left, this has traction and shipping implementations. It should get the broader exposure of a WG, and that IPR protection that comes along with it. If anyone thinks this API is harmful, that could change things, but I'm not aware of any such position. |
Agreed. Any advice on how to start that process? I can take a look at turning this into some PRs against the appropriate spec (I guess CSSOM View?) but wondering if there's any other steps that need to be taken first? |
I'd suggest filing an issue in the CSSWG's repo suggesting adoption of the spec, with a pointer to the spec (and it's explainer if it has one), and adding the "Agenda+" label to get it some attention. |
Thanks @frivoal, I've filed w3c/csswg-drafts#6339 but aren't a contributor so can't add the label. |
I was wondering if this spec is ready to graduate into a main W3C working group (such as the CSS WG).
If not, are there specific issues or tasks blocking such a move?
The text was updated successfully, but these errors were encountered: