Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upcustomElements.define isn't checking disabledFeatures and formAssociated when expected #25017
Labels
Projects
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
WPT custom-elements/CustomElementRegistry has various tests that set up call-trace proxies around a custom class and then call customElements.define to see which fields are accessed. In general,
disabledFeaturesandformAssociatedare expected to be accessed but aren't. A quick grep of servo's codebase suggests these strings might not even be in it.https://html.spec.whatwg.org/multipage/custom-elements.html#custom-elements-api specifies getting them, in substeps 14-6 and 14-12 of the define method.