feat: Rename HTMLOrSVGElement to HTMLOrForeignElement

[ExE-Boss]

Part of #4702

• At least two implementers are interested (and none opposed):
  • All of them
• Tests are written and can be reviewed and commented upon at:
  • …
• Implementation bugs are filed:
  • Chrome: https://bugs.chromium.org/p/chromium/issues/detail?id=835571
  • Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1571487
  • Safari: https://bugs.webkit.org/show_bug.cgi?id=200470

(See WHATWG Working Mode: Changes for more details.)

Closes #5248

---

/dom.html ( diff )
/urls-and-fetching.html ( diff )

[domenic]

This does not contain the normative changes as was indicated in #4702.

Are the corresponding changes to the MathML spec landed yet? (It should first reference HTMLOrSVGElement, with an outstanding pull request to change it to HTMLOrForeignElement.)

Do those changes meet the WHATWG working mode criteria, i.e. are multiple implementers planning on landing dataset, nonce, autofocus, tabIndex, focus(), and blur() on MathML elements? (Note: given that Chromium does not implement MathML, this must require both Gecko and WebKit to be landing such changes.)

Are there tests showing the functionality of all of those pieces on MathML elements?

A renaming pull request is the very last piece that will land in the specification ecosystem, since it has no normative impact. First we must achieve the normative results indicated above.

[fred-wang]

cc @bkardell

This does not contain the normative changes as was indicated in #4702.

Are the corresponding changes to the MathML spec landed yet? (It should first reference HTMLOrSVGElement, with an outstanding pull request to change it to HTMLOrForeignElement.)

MathML Core uses HTMLOrForeignElement with a link to HTMLOrSVGElement: https://mathml-refresh.github.io/mathml-core/#dom-and-javascript

If you really want a PR to change the link to HTMLOrForeignElement it's straightforward to open one.

Do those changes meet the WHATWG working mode criteria, i.e. are multiple implementers planning on landing dataset, nonce, autofocus, tabIndex, focus(), and blur() on MathML elements? (Note: given that Chromium does not implement MathML, this must require both Gecko and WebKit to be landing such changes.)

Gecko and WebKit implement the HTMLOrForeignElement interface for MathML elements and the same is true for Chromium when experimental web platform features are enabled.

Are there tests showing the functionality of all of those pieces on MathML elements?

Yes they are.

A renaming pull request is the very last piece that will land in the specification ecosystem, since it has no normative impact. First we must achieve the normative results indicated above.

Is there anything else blocking this change?

[domenic]

If you really want a PR to change the link to HTMLOrForeignElement it's straightforward to open one.

Yes, it'd be good to have such a PR.

Gecko and WebKit implement the HTMLOrForeignElement interface for MathML elements and the same is true for Chromium when experimental web platform features are enabled.

Are the former two intending to ship to stable? (I know for Chromium the Intent to Ship has not been sent, much less approved.)

Yes they are.

Can you link to them?

[domenic]

I forgot:

Is there anything else blocking this change?

The contributor for this pull request is not currently able to contribute to WHATWG standards, due to their use of a pseudonym. They need to update their data at https://github.com/whatwg/participant-data/blob/master/individuals.json before we can verify them and accept contributions. (See whatwg/sg#93 for more.)

[fred-wang]

If you really want a PR to change the link to HTMLOrForeignElement it's straightforward to open one.
Yes, it'd be good to have such a PR.

Done: w3c/mathml-core#19

Are the former two intending to ship to stable? (I know for Chromium the Intent to Ship has not been sent, much less approved.)

It has been shipped in Firefox release since last year: https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/71#MathML

It's also in Safari Tech Preview but because of https://trac.webkit.org/wiki/FAQ#Releases I'd rather let @rniwa or someone else from Apple comment, if they are willing to.

Regarding Chromium, I'm not sure I understand how I should read your comment... It sounds you are quite pessimistic but maybe that's just a text communication issue.

Can you link to them?

Here are the tests from the Gecko patch to add MathMLElement:

https://w3c-test.org/mathml/relations/html5-tree/clipboard-event-handlers.tentative.html
https://w3c-test.org/mathml/relations/html5-tree/css-inline-style-dynamic.tentative.html
https://w3c-test.org/mathml/relations/html5-tree/css-inline-style-interface.tentative.html
https://w3c-test.org/mathml/relations/html5-tree/html-or-foreign-element-interfaces.tentative.html
https://w3c-test.org/mathml/relations/html5-tree/math-global-event-handlers.tentative.html
https://w3c-test.org/mathml/relations/html5-tree/tabindex-001.html
https://w3c-test.org/mathml/relations/html5-tree/tabindex-002.html

I can't find tests for nonce or autofocus ; @bkardell do you remember why they are not tested ?

[fred-wang]

The contributor for this pull request is not currently able to contribute to WHATWG standards, due to their use of a pseudonym. They need to update their data at https://github.com/whatwg/participant-data/blob/master/individuals.json before we can verify them and accept contributions. (See whatwg/sg#93 for more.)

@ExE-Boss Thank you very much for working on this PR and for your persistent effort on this change at the WHATWG. Can you please rebase your PR? Are you comfortable with @domenic 's request? If not, Igalia will be happy to take over this.

[ExE-Boss]

I’m not comfortable with putting my real identity into any VCS repository.

[bkardell]

@domenic @annevk can either of you advise what we should do here? should igalia send a different PR, or can we transfer this one to us somehow or...?

[domenic]

A different PR makes sense. Be sure to fill out the template.

[ExE-Boss]

Closing in favour of #5248.