[chrisdavidmills]

…relList, and referrerPolicy properties

Summary

Firefox Nightly 159 adds support for the MathMLAnchorElement download, ping, rel, relList, and referrerPolicy properties; see https://bugzilla.mozilla.org/show_bug.cgi?id=2064612.

This PR adds data points for these new properties.

Note that the spec URL situation is a bit odd — the impl bug points to https://w3c.github.io/mathml-core/#the-a-element for the spec, which I guess isn't totally unreasonable, as download, ping, rel, and referrerPolicy at least are just reflected properties.

I couldn't find a spec URL of any kind for relList, so I've just marked that as non-standard for now.

Test results and supporting details

I tested all of these, and verified that they worked in Nightly 159. I viewed the example at https://developer.mozilla.org/en-US/docs/Web/API/MathMLAnchorElement#examples in the MDN Playground. I updated the first link to include these attributes:

download="yes"
ping="https://example-tracking.com https://example-analytics.com"
rel="help alternate"
referrerPolicy="no-referrer"

Then I added the following code to access the new properties:

outputValue("download");
outputValue("ping");
outputValue("rel");
console.log(mathAnchor.relList[0]);
outputValue("referrerPolicy");

Related issues

[github-actions]

Tip: Review these changes grouped by change (recommended for most PRs), or grouped by feature (for large PRs).

[Elchi3]

I couldn't find a spec URL of any kind for relList, so I've just marked that as non-standard for now.

@fred-wang I don't see relList in w3c/mathml-core#335. Was that an oversight?

[Elchi3]

Also, I wondered why I didn't detect these new IDL properties from webref and the reason is in the Firefox patch:

// FIXME: This is different from the current MathML core spec.
// We should move attributes below to HyperlinkElementUtils mixin
// once we are ready to share the mixin with HTML and SVG anchor element.
// We have these attributes temporarily in MathMLAnchorElement.idl for now.
[CEReactions, SetterThrows] attribute DOMString download;
[CEReactions, SetterThrows] attribute USVString ping;
[CEReactions, SetterThrows] attribute DOMString rel;
[PutForwards=value] readonly attribute DOMTokenList relList;
[CEReactions, SetterThrows] attribute DOMString referrerPolicy;

So, it is not really standardized for now, but I guess it is likely that this will end up in some spec, either MathMLAnchorElement or HyperlinkElementUtils. Strictly speaking that makes everything here non-standard for now. I could maybe live with your workaround to mark it as standardized if you point me to another vendor that feels positive towards this plan.

[chrisdavidmills]

Strictly speaking that makes everything here non-standard for now.

I think you're right. I've set them all to non-standard for now.

[Elchi3]

Thank you, Chris! 👍