Bug 118843 - mfenced element and its expanded form do not use the same spacing
Summary: mfenced element and its expanded form do not use the same spacing
Status: RESOLVED DUPLICATE of bug 115787
Alias: None
Product: WebKit
Classification: Unclassified
Component: MathML (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on: 99620
Blocks:
  Show dependency tree / graph
 
Reported: 2013-07-18 03:38 PDT by Frédéric Wang (:fredw)
Modified: 2014-02-21 15:12 PST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Frédéric Wang (:fredw) 2013-07-18 03:38:07 PDT 
mfenced should be equivalent to its expanded form

<mrow>
   <mo fence="true"> opening-fence </mo>
   <mrow>
      arg#1
      <mo separator="true"> sep#1 </mo>
      ...
      <mo separator="true"> sep#(n-1) </mo>
      arg#n
   </mrow>
   <mo fence="true"> closing-fence </mo>
</mrow>

However, the spacing for mfenced is
- .1em before and after the fences
- 0em/.25em before/after the separators

while the spacing for mo is
- .1em before and after the operator when it is the first or last child of an mrow
- .2em otherwise.

Bug 115787 should solve that issue.
Comment 1 Frédéric Wang (:fredw) 2014-02-21 15:12:19 PST 
This will be fixed by bug 115787.

*** This bug has been marked as a duplicate of bug 115787 ***