Closed Bug 347496 Opened 19 years ago Closed 18 years ago

Dynamic changes to MathML table lines don't work

Categories

(Core :: MathML, defect)

PowerPC
macOS
defect
Not set
minor

Tracking

()

RESOLVED FIXED

People

(Reporter: jruderman, Assigned: rbs)

References

Details

(Keywords: testcase)

Attachments

(3 files, 2 obsolete files)

Attached file testcase
Blocks: 347580
The fix will follow-up from bug 179619.
Depends on: 179619
Attached file extended testcase (obsolete) —
Attached file extended testcase
Attachment #237665 - Attachment is obsolete: true
Attached patch patch (obsolete) — Splinter Review
Follow-up to bug 179619, where AttributeChanged was hooked on mtr and mtd. Here, - AttributeChanged is hooked on mtable itself. Plus some cosmetics: - remove the utopic loop over the rowgroups to face reality. - rename aFlagsToUpdate to aWhichFlags. - rename a couple of bit flags in mPresentationData.flags. - map 'false' to '0' in FindAttrValueIn to ease the mapping in the brain when reading that code.
Attachment #237674 - Flags: superreview?(roc)
Attachment #237674 - Flags: review?(roc)
+ static nsIContent::AttrValuesArray strings[] = + {&nsMathMLAtoms::_false, &nsMathMLAtoms::_true, nsnull}; + switch (mContent->FindAttrValueIn(kNameSpaceID_None, nsMathMLAtoms::displaystyle_, + strings, eCaseMatters)) { + case 0: + mPresentationData.flags &= ~NS_MATHML_DISPLAYSTYLE; + mPresentationData.flags |= NS_MATHML_EXPLICIT_DISPLAYSTYLE; + break; + case 1: + mPresentationData.flags |= NS_MATHML_DISPLAYSTYLE; + mPresentationData.flags |= NS_MATHML_EXPLICIT_DISPLAYSTYLE; + break; This code could be shared somehow, right? Otherwise looks good.
Attachment #237674 - Attachment is obsolete: true
Attachment #239033 - Flags: superreview?(roc)
Attachment #239033 - Flags: review?(roc)
Attachment #237674 - Flags: superreview?(roc)
Attachment #237674 - Flags: review?(roc)
Attachment #239033 - Flags: superreview?(roc)
Attachment #239033 - Flags: superreview+
Attachment #239033 - Flags: review?(roc)
Attachment #239033 - Flags: review+
Checked in.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
I checked in a reftest based on the original testcase. Should rbs's extended testcase also be a series of reftests? (Note that the "refdyn" tool is great for finding bugs in dynamic rendering, as long as there is a reftest or crashtest file that covers the features in question.)
Flags: in-testsuite+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: