Bug 107856 – mathml fences often look bad

• Status: RESOLVED
• Resolution: FIXED
• Component: MathML

[Ojan Vafai]

Created attachment 184564 [details]
test case

Here's a case where the open fence is stretched using font-size and the close fence is stretched using stacking of multiple characters. Just stumbled across this while working on other mathml stuff.

[Ojan Vafai]

Created attachment 184565 [details]
screenshot

[Ojan Vafai]

For those not familiar with mathml, the opening curly brace should be the same size/font as the closing paren.

[Dave Barton]

Another problem in this particular case is that the outer <mfenced> probably shouldn't have a closing fence at all, given the close="" attribute. The current implementation kind of assumes open and close are each 1 character. (I didn't write this code.)

Actually in Chrome 24 stable (24.0.1312.56) on Mac OS 10.6.8, I don't get the opening fence you're seeing in your screenshot, either with or without STIX fonts enabled. I just get a thin nice-looking brace.

[Frédéric Wang (:fredw)]

Created attachment 184906 [details]
modified testcase, mfenced replaced by mrow+mo

Here is a modified version, with mfenced replaced by the equivalent mrow+mo constructions. That looks much better in Webkit with that change.

Some MathML WG members have said in the past that mfenced was only there because of demands from some math communities but they are not really fond of this element: it duplicates the mrow+mo construction and uses a different format (attributes for operators, no way to use mo attributes on them). This has been the source of many bugs in Firefox, MathJax, MathPlayer essentially because the two constructions are not always consistent. Personally, I would encourage people not to use it.

[Dave Barton]

I agree about <mfenced> being a bad idea.

Actually, as I read the spec, the <mfenced> in this case isn't even really legal, since there's no closing fence.

[Frédéric Wang (:fredw)]

(In reply to comment #5)
> I agree about <mfenced> being a bad idea.
> 
> Actually, as I read the spec, the <mfenced> in this case isn't even really legal, since there's no closing fence.

I think this testcase has been generated by a previous version of MathJax which incorrectly used <mfenced> to convert thinks like

\left{ ... \right.

into

<mfenced open="{" close=""> ... </mfenced>

which per http://www.w3.org/TR/MathML3/chapter3.html#presm.mfenced is equivalent to

<mrow>
   <mo>{</mo>
   <mrow>
     ...
   </mrow>
   <mo></mo>
</mrow>

I'm not sure it is very good semantically to have this empty <mo> as a closing fence. That's one more good reason not to use the <mfenced> element. Fortunately, MathJax stopped using that element in the most recent versions.

[Frédéric Wang (:fredw)]

Created attachment 233520 [details]
Screenshot Nightly WebKitGTK+

Here is a screenshot of the testcase in a nightly build with Latin Modern Math. We no longer do stretching via font-size and the closing parenthesis is not displayed for close="", as expected.