-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Demix DocumentOrShadowRoot #9045
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have run the collector's update script with all the results we have and commented on non-trivial disagreements. Unfortunately I couldn't make inline suggestions where the relevant bit was outside the diff.
I ignored a bunch of smaller off-by-one issues, which I think we can deal with as updates after this lands.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, I've now checked for prefixes and alt. names that didn't seem very plausible on ShadowRoot
.
Thanks, this was really helpful @foolip! It shows real benefits of having mixins treated properly. The data is quite different from interface to interface. |
So, here we saw quite early version numbers, probably to fix #3504.
I've left those early versions for the Document part here.
For the ShadowRoot part, I've temporarily added a root compat data object api.ShadowRoot to this file, so the consistency checker would complain (it currently doesn't, I filed #9044). I've then bumped the versions up to the basic support of ShadowRoot for all features of ShadowRoot.
I've removed the documentorshadowroot feature from ShadowRoot. It makes no sense with the new mixin approach, imo.
It would be cool if some automation could actually verify the version numbers here, since I want to focus on demixing instead of on researching the correct data for two interfaces. (cc @foolip)