Closed
Bug 347496
Opened 19 years ago
Closed 18 years ago
Dynamic changes to MathML table lines don't work
Categories
(Core :: MathML, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: jruderman, Assigned: rbs)
References
Details
(Keywords: testcase)
Attachments
(3 files, 2 obsolete files)
769 bytes,
application/xhtml+xml
|
Details | |
6.08 KB,
application/xhtml+xml
|
Details | |
28.35 KB,
patch
|
roc
:
review+
roc
:
superreview+
|
Details | Diff | Splinter Review |
Reporter | ||
Comment 1•19 years ago
|
||
Attachment #237665 -
Attachment is obsolete: true
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
Reporter | ||
Comment 9•17 years ago
|
||
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.
Description
•