Closed
Bug 481591
Opened 16 years ago
Closed 16 years ago
fix problems with content: counter() and counters() serialization
Categories
(Core :: CSS Parsing and Computation, defect, P4)
Core
CSS Parsing and Computation
Tracking
()
RESOLVED
FIXED
mozilla1.9.2a1
People
(Reporter: dbaron, Assigned: dbaron)
Details
Attachments
(4 files)
22.87 KB,
patch
|
bzbarsky
:
review+
bzbarsky
:
superreview+
|
Details | Diff | Splinter Review |
1.19 KB,
patch
|
bzbarsky
:
review+
bzbarsky
:
superreview+
|
Details | Diff | Splinter Review |
3.29 KB,
patch
|
bzbarsky
:
review+
bzbarsky
:
superreview+
|
Details | Diff | Splinter Review |
2.35 KB,
patch
|
Details | Diff | Splinter Review |
I noticed a bunch of problems with serialization of content:counter() and counters() functions. Patches to follow.
Assignee | ||
Comment 1•16 years ago
|
||
Note that these patches apply on top of the patches in bug 478160.
Assignee | ||
Comment 2•16 years ago
|
||
This splits eCSSUnit_String into String (quoted), Ident (unquoted), and Families (font-family list). Note that the font-family descriptor is String rather than Families.
(I'd like to eventually change Families into some other data type; there's even an existing bug on that.)
Attachment #365616 -
Flags: superreview?(bzbarsky)
Attachment #365616 -
Flags: review?(bzbarsky)
Assignee | ||
Comment 3•16 years ago
|
||
Attachment #365617 -
Flags: superreview?(bzbarsky)
Attachment #365617 -
Flags: review?(bzbarsky)
Assignee | ||
Comment 4•16 years ago
|
||
Attachment #365618 -
Flags: superreview?(bzbarsky)
Attachment #365618 -
Flags: review?(bzbarsky)
Assignee | ||
Updated•16 years ago
|
Attachment #365616 -
Attachment description: patch 1: split eCSSUnit_String into String, Ident, and Families → patch 1: split eCSSUnit_String into String, Ident, and Families (which gives us quotes around the separator-part of counters())
Assignee | ||
Updated•16 years ago
|
Attachment #365617 -
Attachment description: patch 2: serialization bug 1, fix computed style to output keywords rather than integers → patch 2: fix computed style serialization to output keywords rather than integers
Assignee | ||
Comment 5•16 years ago
|
||
I wrote these tests while looking at the code coverage output in http://people.mozilla.org/~mnandigama/codecoverage/src/layout/style/nsCSSDeclaration.cpp.gcov.html , which led me to the bugs fixed here.
Updated•16 years ago
|
Attachment #365616 -
Flags: superreview?(bzbarsky)
Attachment #365616 -
Flags: superreview+
Attachment #365616 -
Flags: review?(bzbarsky)
Attachment #365616 -
Flags: review+
Comment 6•16 years ago
|
||
Comment on attachment 365616 [details] [diff] [review]
patch 1: split eCSSUnit_String into String, Ident, and Families (which gives us quotes around the separator-part of counters())
Can we add an assert on the unit in the nsCSSFontFaceStyleDecl::GetPropertyValue eCSSFonDesc_Family case, where the comment talks about knowing the unit?
Do we still need to Trim() the quote from the eCSSFontDesc_Family in InsertFontFaceRule?
With the assert added and the Trim() checked, looks good.
Updated•16 years ago
|
Attachment #365617 -
Flags: superreview?(bzbarsky)
Attachment #365617 -
Flags: superreview+
Attachment #365617 -
Flags: review?(bzbarsky)
Attachment #365617 -
Flags: review+
Updated•16 years ago
|
Attachment #365618 -
Flags: superreview?(bzbarsky)
Attachment #365618 -
Flags: superreview+
Attachment #365618 -
Flags: review?(bzbarsky)
Attachment #365618 -
Flags: review+
Assignee | ||
Comment 7•16 years ago
|
||
(In reply to comment #6)
> Do we still need to Trim() the quote from the eCSSFontDesc_Family in
> InsertFontFaceRule?
No, and I don't think we did before this patch either.
Assignee | ||
Comment 8•16 years ago
|
||
http://hg.mozilla.org/mozilla-central/rev/3428afb4e233
http://hg.mozilla.org/mozilla-central/rev/3b13a87771fe
http://hg.mozilla.org/mozilla-central/rev/36da7fe92b5f
http://hg.mozilla.org/mozilla-central/rev/ac91e21d53c5
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Priority: -- → P4
Resolution: --- → FIXED
Target Milestone: --- → mozilla1.9.2a1
You need to log in
before you can comment on or make changes to this bug.
Description
•