554428 - MathML tag mfenced fails to show opening and closing default fence

Status: RESOLVED FIXED

(Core :: MathML, defect)

Description

[Joe Java]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.5; en-US; rv:1.9.2.2) Gecko/20100316 Firefox/3.6.2
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.5; en-US; rv:1.9.2.2) Gecko/20100316 Firefox/3.6.2

On a OS X leopard system without STIX Bets fonts, the opening and closing default fence for a MathMl mfenced tag does not always show.  In the image supplied note that the first row of the last column has an equation (right after the word 'sphere') that should have the default opening and closing boundaries of '(' and ')', but instead nothing is shown (even if the font does not have the correct symbols SOMETHING should be shown).

Reproducible: Always

Steps to Reproduce:
1. go to https://eyeasme.com/Joe/MathML/MathML_browser_test.html
2. look at the row labeled "Sphere Volume", last column (first row in that column)
3. no boundaries are shown for the equation 
Actual Results:  
The equation in question has no boundaries shown.

Expected Results:  
The equation in question should be bounded by '(' and ')'.

There should be boundaries or some symbols showing that a boundary glyph should be present.

Comment 1

[Joe Java]

Attachment: Note first line of last column has no boundaries around equation

Note first line of last column has no boundaries around equation that begins with 4/3

Comment 2

[Karl Tomlinson (:karlt)]

Is this a regression from Firefox 3.5 (or 3.0)?

Comment 3

[Karl Tomlinson (:karlt)]

Do the parentheses ever appear, e.g. after scrolling out of the viewport and back, minimize/restore, or zoom?

Comment 4

[Joe Java]

The parentheses only appear when the image is zoomed in.

Comment 5

[Joe Java]

I never previously tested this page without STIX Beta fonts being used, so I am not sure if this a regression or not.

Comment 6

[Joe Java]

This bug appears to be fixed with STIX fonts on OS X Intel machine FF 4.0b11pre 20110201

Comment 7

[Joe Java]

Seems fixed with FF 4