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
HTMLOrForeignElement is a mixin that describes several features common to the HTMLElement, SVGElement and MathMLElement interfaces. It even has it's own page (HTMLOrForeignElement)and its members are documented on pages that are children pages to that page. Yet, for some reason __compat data about members of HTMLOrForeignElement lives under corresponding elements.
We should consider either of the two things:
Create a single separate file api/HTMLOrForeignElement.json HTMLOrForeignElement.dataset says "Please change the compat macro's paramter to api.HTMLOrForeignElement.dataset after BCD is updated."
Create separate BCD entries for HTMLElement, SVGElement and MathMLElement but make a single documentation page
E.g., for HTMLOrForeignElement.nonce each of HTMLElement.nonce, SVGElement.nonce, and MathMLElement.nonce will have a separate __compat like they do now, but they will link to a single article HTMLOrForeignElement.nonce.
The text was updated successfully, but these errors were encountered:
HTMLOrForeignElement
is a mixin that describes several features common to theHTMLElement
,SVGElement
andMathMLElement
interfaces. It even has it's own page (HTMLOrForeignElement
)and its members are documented on pages that are children pages to that page. Yet, for some reason__compat
data about members ofHTMLOrForeignElement
lives under corresponding elements.We should consider either of the two things:
api/HTMLOrForeignElement.json
HTMLOrForeignElement.dataset
says "Please change the compat macro's paramter to api.HTMLOrForeignElement.dataset after BCD is updated."HTMLElement
,SVGElement
andMathMLElement
but make a single documentation pageE.g., for
HTMLOrForeignElement.nonce
each ofHTMLElement.nonce
,SVGElement.nonce
, andMathMLElement.nonce
will have a separate__compat
like they do now, but they will link to a single articleHTMLOrForeignElement.nonce
.The text was updated successfully, but these errors were encountered: