Closed Bug 487449 Opened 15 years ago Closed 15 years ago

Figure out correct prevSibling in nsCSSFrameConstructor::ContentAppended

Categories

(Core :: Layout, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: bzbarsky, Assigned: bzbarsky)

References

Details

Attachments

(1 file)

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.
Oh, that was all about nsCSSFrameConstructor::ContentAppended.
Summary: Figure out correct prevSibling in ContentAppended → Figure out correct prevSibling in nsCSSFrameConstructor::ContentAppended
Blocks: 484448
Depends on: 487895
Depends on: 487899
Attached patch Proposed fixSplinter Review
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+
Pushed http://hg.mozilla.org/mozilla-central/rev/11714b1d9aa4
Status: NEW → RESOLVED
Closed: 15 years ago
Flags: in-testsuite+
Resolution: --- → FIXED
Depends on: 488388
Depends on: 489479
Depends on: 505482
Depends on: 496360
Depends on: 496823
No longer depends on: 496360
Product: Core → Core Graveyard
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.

Attachment

General

Created:
Updated:
Size: