Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(732)

Issue 2150933002: Fix crash when removing contents from a document having multiple bodies (Closed)

Created:
4 years, 5 months ago by Xianzhu
Modified:
4 years, 5 months ago
Reviewers:
CC:
chromium-reviews, krit, szager+layoutwatch_chromium.org, drott+blinkwatch_chromium.org, Rik, zoltan1, blink-reviews-platform-graphics_chromium.org, ajuma+watch_chromium.org, blink-reviews-layout_chromium.org, pdr+renderingwatchlist_chromium.org, eae+blinkwatch, leviw+renderwatch, Justin Novosad, jbroman, pdr+graphicswatchlist_chromium.org, f(malita), jchaffraix+rendering, blink-reviews, Stephen Chennney, dshwang, danakj+watch_chromium.org, rwlbuis
Base URL:
https://chromium.googlesource.com/chromium/src.git@2785
Target Ref:
refs/pending/branch-heads/2785
Project:
chromium
Visibility:
Public.

Description

Fix crash when removing contents from a document having multiple bodies Removed the early return under condition 'isBody()' from LayoutObjectChildList::invalidatePaintOnRemoval() to ensure the painting layer and body object are invalidated. BTW fixed issues of DisplayItemClient aliveness checking which made it not actually work for subsequences. (If we didn't have the issues, we should have caught this bug through aliveness-checking.) Still not sure if we could have more reduced test. For the test, removing anything from the test would make the test not reproducing the bug. A normal removal of <body> couldn't reproduce the bug because we will invalidate the painting layer in other paths (e.g. layout triggered invalidation, etc.). BUG=626182 Review-Url: https://codereview.chromium.org/2133603002 Cr-Commit-Position: refs/heads/master@{#404552}

Patch Set 1 #

Messages

Total messages: 1 (0 generated)
Xianzhu
4 years, 5 months ago (2016-07-14 16:36:30 UTC) #1
Message was sent while issue was closed.
Committed patchset #1 (id:1) to pending queue manually as
0cc71100558e3ab2a888ac1361b83689ecc9ac9d.

Powered by Google App Engine
This is Rietveld 408576698