Closed
Bug 141289
Opened 22 years ago
Closed 22 years ago
:before/:after content doubled on some elements
Categories
(Core :: CSS Parsing and Computation, defect, P1)
Core
CSS Parsing and Computation
Tracking
()
VERIFIED
FIXED
mozilla1.1alpha
People
(Reporter: dbaron, Assigned: dbaron)
References
Details
(Keywords: testcase)
Attachments
(2 files)
|
497 bytes,
text/html
|
Details | |
|
3.41 KB,
patch
|
attinasi
:
review+
waterson
:
superreview+
|
Details | Diff | Splinter Review |
We doubly-create :before/:after content for some elements. In particular, CSS describes :before/:after content as being created as the first-child or last-child of the content to which the selectors match, not the previous sibling or next sibling. However, it gives *examples* with img:before that contradict this, so we put a hack in ConstructHTMLFrame to support :before/:after on leaf frames. This hack causes a bunch of serious problems (bugs related to HR and RemoveGeneratedContentFrameSiblings). However, since we don't check |processChildren| in ConstructHTMLFrame, we create the content the correct way too in the case where the element isn't a leaf. Testcase and patch to be attached.
| Assignee | ||
Comment 1•22 years ago
|
||
| Assignee | ||
Updated•22 years ago
|
Status: NEW → ASSIGNED
Priority: -- → P1
Target Milestone: --- → mozilla1.1alpha
| Assignee | ||
Comment 2•22 years ago
|
||
Comment 3•22 years ago
|
||
This fix makes no sense to me, but it works. Hold my hand and explain why? (It would seem to me like it would preclude creating of the :before and :after content on the <legend> element itself, for example.)
| Assignee | ||
Comment 4•22 years ago
|
||
If |ProcessChildren| is true, then we call ProcessChildren, which creates the generated content in the correct place, in the child list.
Comment 5•22 years ago
|
||
Adding bugs with doubled GC so they get tested when this is fixed.
Comment 6•22 years ago
|
||
Comment on attachment 81733 [details] [diff] [review] patch r=attinasi - thanks for the explanation David. Could you include a comment saying why !processChildren is used? The comment you have is interesting, but does not explain how ProcessChildren creates the generated content...
Attachment #81733 -
Flags: review+
Comment 7•22 years ago
|
||
Comment on attachment 81733 [details] [diff] [review] patch sr=waterson
Attachment #81733 -
Flags: superreview+
| Assignee | ||
Comment 8•22 years ago
|
||
Fix checked in to trunk 2002-04-30 17:51 PDT.
Comment 9•22 years ago
|
||
Fixed in new Linux CVS trunk build.
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 10•22 years ago
|
||
Reopening since I might want this on 1.0...
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
| Assignee | ||
Updated•22 years ago
|
Status: REOPENED → ASSIGNED
Comment 11•22 years ago
|
||
cc'ing myself
| Assignee | ||
Comment 12•22 years ago
|
||
Ok, never mind about the branch, unless we want it in order to land the fix for bug 141054.
Status: ASSIGNED → RESOLVED
Closed: 22 years ago → 22 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 14•22 years ago
|
||
*** Bug 168740 has been marked as a duplicate of this bug. ***
You need to log in
before you can comment on or make changes to this bug.
Description
•