You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What information was incorrect, unhelpful, or incomplete?
In #30349 we decided to not record HTMLElement* constructor data for now. We should add this data all at once, if we want to record it. It is a separate project, not a drive-by task.
The HTML specification added these HTML element constructors ca. 2016 to make them sub-classable for custom elements.
What browsers does this problem apply to, if applicable?
No response
What did you expect to see?
HTML element constructor keys.
Did you test this? If so, how?
Didn't test, the collector tests need to be fixed so we could collect this data all at once.
Can you link to any release notes, bugs, pull requests, or MDN pages related to this?
MDN content needs to decide if it wants content pages. Maybe mentioning the constructor in HTMLElement* interface pages is enough.
Because the builtin element constructors are not direct callable (they throw an "illegal constructor" error), the test for this data is something along the lines of:
Subclass a builtin-element.
Call the constructor on the subclass (implicitly calling the builtin constructor).
Activity
ddbeck commentedon Sep 1, 2026
Because the builtin element constructors are not direct callable (they throw an "illegal constructor" error), the test for this data is something along the lines of: