Closed
Bug 487449
Opened 16 years ago
Closed 16 years ago
Figure out correct prevSibling in nsCSSFrameConstructor::ContentAppended
Categories
(Core :: Layout, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: bzbarsky, Assigned: bzbarsky)
References
Details
Attachments
(1 file)
|
(deleted),
patch
|
roc
:
review+
roc
:
superreview+
|
Details | Diff | Splinter Review |
ContentAppended doesn't look for the prevsibling. Unfortunately, WipeContainingBlock could really use knowing what the right prevsibling is to avoid reframes when content starting with whitespace is appended to a table or table row.
It should be doable to make ContentAppended find the prevSibling and to only have to do it once.
|
Assignee | |
Comment 1•16 years ago
|
||
Oh, that was all about nsCSSFrameConstructor::ContentAppended.
|
|
Assignee | |
Updated•16 years ago
|
Summary: Figure out correct prevSibling in ContentAppended → Figure out correct prevSibling in nsCSSFrameConstructor::ContentAppended
|
|
Assignee | |
Comment 2•16 years ago
|
||
Attachment #372511 -
Flags: superreview?(roc)
Attachment #372511 -
Flags: review?(roc)
Attachment #372511 -
Flags: superreview?(roc)
Attachment #372511 -
Flags: superreview+
Attachment #372511 -
Flags: review?(roc)
Attachment #372511 -
Flags: review+
|
|
Assignee | |
Comment 3•16 years ago
|
||
Status: NEW → RESOLVED
Closed: 16 years ago
Flags: in-testsuite+
Resolution: --- → FIXED
|
||
Updated•6 years ago
|
Product: Core → Core Graveyard
|
||
Updated•6 years ago
|
Component: Layout: Misc Code → Layout
Product: Core Graveyard → Core
You need to log in
before you can comment on or make changes to this bug.
Description
•