|
|
Chromium Code Reviews|
Created:
4 years, 2 months ago by Stephen Chennney Modified:
4 years, 2 months ago Reviewers:
flackr CC:
blink-reviews, blink-reviews-layout_chromium.org, chromium-reviews, eae+blinkwatch, jchaffraix+rendering, leviw+renderwatch, pdr+renderingwatchlist_chromium.org, szager+layoutwatch_chromium.org, zoltan1 Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionRevert the removal of CompositingReasonOutOfFlowClipping
Change https://codereview.chromium.org/2382563002/ modified
the logic for compositing layers with a clip parent when
we prefer compositing to LCD text. Revert that change to fix
painting of fixed position clipped elements over accelerated
scrolling elements.
R=flackr@chromium.org
BUG=650446
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Committed: https://crrev.com/2d9b508d37b0fac7f0b3c4fcce5f8a278d4fb9d7
Cr-Commit-Position: refs/heads/master@{#423609}
Patch Set 1 #Patch Set 2 : New baseline for compositing/overflow/scroll-parent-absolute-with-backdrop-filter.html #Patch Set 3 : Add virtual expectation, update style #Patch Set 4 : Fix type in DCHECK #
Total comments: 2
Patch Set 5 : Fix missing DCHECKS #
Total comments: 2
Patch Set 6 : Improve DCHECKs. #
Messages
Total messages: 37 (22 generated)
Description was changed from ========== Revert the removal of CompositingReasonOutOfFlowClipping Change https://codereview.chromium.org/2382563002/ modified the logic for compositing layers with a clip parent when we prefer compositing to LCD text. Revert that change to fix painting of fixed position clipped elements over accelerated scrolling elements. R=flackr@chromium.org BUG=650446 ========== to ========== Revert the removal of CompositingReasonOutOfFlowClipping Change https://codereview.chromium.org/2382563002/ modified the logic for compositing layers with a clip parent when we prefer compositing to LCD text. Revert that change to fix painting of fixed position clipped elements over accelerated scrolling elements. R=flackr@chromium.org BUG=650446 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 ==========
The CQ bit was checked by schenney@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
lgtm
The CQ bit was unchecked by schenney@chromium.org
The CQ bit was checked by schenney@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: mac_chromium_rel_ng on master.tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)
The CQ bit was checked by schenney@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from flackr@chromium.org Link to the patchset: https://codereview.chromium.org/2389293002/#ps20001 (title: "New baseline for compositing/overflow/scroll-parent-absolute-with-backdrop-filter.html")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)
The CQ bit was checked by schenney@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
I think this needs another review after I changed all the ASSERTS and some formatting. There is really no contentful change, but a sanity check would be good.
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: cast_shell_android on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/cast_shell_a...) chromeos_x86-generic_chromium_compile_only_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/chromeos_x86-ge...)
The CQ bit was checked by schenney@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
On 2016/10/06 at 16:24:39, schenney wrote: > I think this needs another review after I changed all the ASSERTS and some formatting. There is really no contentful change, but a sanity check would be good. I don't understand, why did all of these ASSERTS need to be changed? I didn't see any failures other than the one test in the tryjob run for patch 3. Also, if they were causing failures, won't the DCHECKs fire in debug mode?
On 2016/10/06 16:52:22, flackr wrote: > On 2016/10/06 at 16:24:39, schenney wrote: > > I think this needs another review after I changed all the ASSERTS and some > formatting. There is really no contentful change, but a sanity check would be > good. > > I don't understand, why did all of these ASSERTS need to be changed? I didn't > see any failures other than the one test in the tryjob run for patch 3. Also, if > they were causing failures, won't the DCHECKs fire in debug mode? The pre-submit check barfed on all the ASSERTS and I did not see a "continue anyway" option. I'm guessing that something recently changed after the great line width reformat. The asserts need to be changed at some point. We might as well deal with it now.
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: linux_chromium_chromeos_ozone_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
On 2016/10/06 at 16:55:55, schenney wrote: > On 2016/10/06 16:52:22, flackr wrote: > > On 2016/10/06 at 16:24:39, schenney wrote: > > > I think this needs another review after I changed all the ASSERTS and some > > formatting. There is really no contentful change, but a sanity check would be > > good. > > > > I don't understand, why did all of these ASSERTS need to be changed? I didn't > > see any failures other than the one test in the tryjob run for patch 3. Also, if > > they were causing failures, won't the DCHECKs fire in debug mode? > > The pre-submit check barfed on all the ASSERTS and I did not see a "continue anyway" option. I'm guessing that something recently changed after the great line width reformat. > > The asserts need to be changed at some point. We might as well deal with it now. Ah okay, I suppose it is just requiring chromium style checks.
https://codereview.chromium.org/2389293002/diff/60001/third_party/WebKit/Sour... File third_party/WebKit/Source/core/layout/compositing/CompositingRequirementsUpdater.cpp (right): https://codereview.chromium.org/2389293002/diff/60001/third_party/WebKit/Sour... third_party/WebKit/Source/core/layout/compositing/CompositingRequirementsUpdater.cpp:138: (fastAnswer == slowAnswer); DCHECK_EQ? https://codereview.chromium.org/2389293002/diff/60001/third_party/WebKit/Sour... third_party/WebKit/Source/core/layout/compositing/CompositingRequirementsUpdater.cpp:157: (layer->stackingNode()->isStackingContext()); DCHECK?
The CQ bit was checked by schenney@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
On 2016/10/06 17:01:14, flackr wrote: > https://codereview.chromium.org/2389293002/diff/60001/third_party/WebKit/Sour... > File > third_party/WebKit/Source/core/layout/compositing/CompositingRequirementsUpdater.cpp > (right): > > https://codereview.chromium.org/2389293002/diff/60001/third_party/WebKit/Sour... > third_party/WebKit/Source/core/layout/compositing/CompositingRequirementsUpdater.cpp:138: > (fastAnswer == slowAnswer); > DCHECK_EQ? > > https://codereview.chromium.org/2389293002/diff/60001/third_party/WebKit/Sour... > third_party/WebKit/Source/core/layout/compositing/CompositingRequirementsUpdater.cpp:157: > (layer->stackingNode()->isStackingContext()); > DCHECK? Fixed those. This is embarrassing, but I'm on a Macbook with a poor internet connection so building to verify changes is a real pain.
LGTM with nits https://codereview.chromium.org/2389293002/diff/80001/third_party/WebKit/Sour... File third_party/WebKit/Source/core/layout/compositing/CompositingReasonFinder.cpp (right): https://codereview.chromium.org/2389293002/diff/80001/third_party/WebKit/Sour... third_party/WebKit/Source/core/layout/compositing/CompositingReasonFinder.cpp:44: DCHECK(potentialCompositingReasonsFromStyle(layer->layoutObject()) == nit: DCHECK_EQ(potentialCompositingReasonsFromStyle(layer->layoutObject()), layer->potentialCompositingReasonsFromStyle()) https://codereview.chromium.org/2389293002/diff/80001/third_party/WebKit/Sour... File third_party/WebKit/Source/core/layout/compositing/CompositingRequirementsUpdater.cpp (right): https://codereview.chromium.org/2389293002/diff/80001/third_party/WebKit/Sour... third_party/WebKit/Source/core/layout/compositing/CompositingRequirementsUpdater.cpp:138: DCHECK_EQ(fastAnswer, slowAnswer); nit: expected value should come first for equality checks (I'm not sure if it technically matters for DCHECK but for many of our macros the error message shows "expected" and "actual" in the resulting message), in this case slowAnswer would be the expected value since we don't normally compute it.
The CQ bit was checked by schenney@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from flackr@chromium.org Link to the patchset: https://codereview.chromium.org/2389293002/#ps100001 (title: "Improve DCHECKs.")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Message was sent while issue was closed.
Committed patchset #6 (id:100001)
Message was sent while issue was closed.
Description was changed from ========== Revert the removal of CompositingReasonOutOfFlowClipping Change https://codereview.chromium.org/2382563002/ modified the logic for compositing layers with a clip parent when we prefer compositing to LCD text. Revert that change to fix painting of fixed position clipped elements over accelerated scrolling elements. R=flackr@chromium.org BUG=650446 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 ========== to ========== Revert the removal of CompositingReasonOutOfFlowClipping Change https://codereview.chromium.org/2382563002/ modified the logic for compositing layers with a clip parent when we prefer compositing to LCD text. Revert that change to fix painting of fixed position clipped elements over accelerated scrolling elements. R=flackr@chromium.org BUG=650446 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 Committed: https://crrev.com/2d9b508d37b0fac7f0b3c4fcce5f8a278d4fb9d7 Cr-Commit-Position: refs/heads/master@{#423609} ==========
Message was sent while issue was closed.
Patchset 6 (id:??) landed as https://crrev.com/2d9b508d37b0fac7f0b3c4fcce5f8a278d4fb9d7 Cr-Commit-Position: refs/heads/master@{#423609} |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
