FF146 MDN docs work for this can be tracked in https://github.com/mdn/content/issues/41878 I'd love to mention this in the release note and also browser compatibility, but I'm not sure I understand it :-(. I have read https://people.igalia.com/fwang/mathml-operator-mirroring-explainer.html and https://cr-status.appspot.com/feature/6317308531965952 1. What MathML elements are are affected? This essentially tells me where I need to add a compatibility subfeature. I think - the `<mo>` element for operators that are mirrorable (i.e. containing Unicode characters with Bidi_Mirrored=Yes). - Implicit fences (from `<mfenced>` or inferred by `<mrow>`) - What else? Square root discussed in your examples so is `<msqrt>` affected? It looks like it is not in the example in https://developer.mozilla.org/en-US/docs/Web/MathML/Reference/Global_attributes/dir 2. Would you like to propose a release note? I can do so for your comment if you prefer. 3. Is there anything that needs to be said in the body of MDN, and if so where? I was thinking that if needed maybe slightly expand the example in https://developer.mozilla.org/en-US/docs/Web/MathML/Reference/Global_attributes/dir Broadly my understanding of this change is that previously mirroring didn't work and now it does :-). The explainer says: >Currently for <mo> element is made of a single character c, steps 2 and 3 of layout of operators determine the glyph corresponding to a given character c, and uses that glyph as an input to the MathVariant tables in order to obtain a larger glyph or a glyph assembly. The same is done for the radical symbol of the <msqrt> and <mroot> elements, using character U+221A SQUARE ROOT. > > The proposal is simply to amend these steps, so that the input glyph is instead obtain by one of the HTML RTL mirroring techniques (Character-level via Unicode or Glyph-level mirroring) from the character c. So what I think you're saying is that you used to get the glyph from the MathVariant tables. Now you get them using character level unicode or glyp-level mirroring. I don't get why that matters, but perhaps if you propose a release note it will.
Bug 1994172 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
FF146 MDN docs work for this can be tracked in https://github.com/mdn/content/issues/41878 I'd love to mention this in the release note and also browser compatibility, but I'm not sure I understand it :-(. I have read https://people.igalia.com/fwang/mathml-operator-mirroring-explainer.html and https://cr-status.appspot.com/feature/6317308531965952 1. What MathML elements are are affected? This essentially tells me where I need to add a compatibility subfeature. I think - the `<mo>` element for operators that are mirrorable (i.e. containing Unicode characters with Bidi_Mirrored=Yes). - Implicit fences (from `<mfenced>` or inferred by `<mrow>`) - What else? Square root discussed in your examples so is `<msqrt>` affected? It looks like it is not in the example in https://developer.mozilla.org/en-US/docs/Web/MathML/Reference/Global_attributes/dir 2. Would you like to propose a release note? I can do so for your comment if you prefer. 3. Is there anything that needs to be said in the body of MDN, and if so where? I was thinking that if needed maybe slightly expand the example in https://developer.mozilla.org/en-US/docs/Web/MathML/Reference/Global_attributes/dir Broadly my understanding of this change is that previously mirroring didn't work and now it does :-). The explainer says: >Currently for <mo> element is made of a single character c, steps 2 and 3 of layout of operators determine the glyph corresponding to a given character c, and uses that glyph as an input to the MathVariant tables in order to obtain a larger glyph or a glyph assembly. The same is done for the radical symbol of the <msqrt> and <mroot> elements, using character U+221A SQUARE ROOT. > > The proposal is simply to amend these steps, so that the input glyph is instead obtain by one of the HTML RTL mirroring techniques (Character-level via Unicode or Glyph-level mirroring) from the character c. So what I think you're saying is that you used to get the glyph from the MathVariant tables. Now you get them using character level unicode or glyp-level mirroring. I don't get why that matters, but perhaps if you propose a release note it will. Have tagged both Fred and Eri - sorry if that counts as spam.