Closed
Bug 30589
Opened 25 years ago
Closed 24 years ago
White space affects <mfenced>
Categories
(Core :: MathML, defect, P3)
Tracking
()
RESOLVED
FIXED
People
(Reporter: gartside, Assigned: rbs)
References
()
Details
mfenced will not work without additional space: Works <mi>n</mi><mi>w</mi> <mfenced open="(" close=")"><mi>Y</mi> </mfenced> (giving latex equivalent $nw(Y)$) Doesnt work <mi>w</mi> <mfenced open="(" close=")"><mi>X</mi></mfenced> (latex equivalent $w(X)$) The only difference is the extra white space between </mi> and </mfenced>
That's a curious one...
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Reporter | ||
Comment 2•24 years ago
|
||
...and also. Adding the extra space results in spurious commas `,' .
Fixed in my tree. The problem came from the fact that an unrelated temporary return-value was getting out of nsMathMLContainerFrame::SetInitialChildList(): nsIFrame* next = mFrames.FirstChild(); while (next) { nsIFrame* child = next; - rv = next->GetNextSibling(&next); + next->GetNextSibling(&next); if (!IsOnlyWhitespace(child)) { nsInlineFrame* inlineFrame = nsnull; - rv = child->QueryInterface(nsInlineFrame::kInlineFrameCID, (void**)&inlineFrame); - if (NS_SUCCEEDED(rv) && inlineFrame) { + nsresult res = child->QueryInterface(nsInlineFrame::kInlineFrameCID, (void**)&inlineFrame); + if (NS_SUCCEEDED(res) && inlineFrame) {
Code checked in. Marking bug as fixed.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Comment 5•24 years ago
|
||
Testcase is now 404. :-( Paul: Do you still have a copy of your testcase? If you do, could you verify the fix? Thanks...
QA Contact: ian → gartside
You need to log in
before you can comment on or make changes to this bug.
Description
•