|
|
Chromium Code Reviews
DescriptionDisable scrollbars on the root scroller when using visual viewport scrollbars.
On Android, the VisualViewport supplies the scrollbars for the root FrameView
and the FrameView blocks its scrollbars from being created. When setting a
different element is set as the document.rootScroller, this scrollbar
suppression behavior needs to occur as well to prevent two sets of scrollbars
from appearing.
BUG=505516
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Committed: https://crrev.com/f5a4f9d38de7403d172ad20f78c462048eae37bc
Cr-Commit-Position: refs/heads/master@{#432965}
Patch Set 1 #Patch Set 2 : Rebase #
Total comments: 4
Patch Set 3 : Nit #Patch Set 4 : Fix tests - only disable if viewportEnabled() is on #Patch Set 5 : Fixed overlay check in FrameView #Patch Set 6 : Unset upstream #Patch Set 7 : Fix build after bad rebase #Patch Set 8 : Fix (?) Graphics2D test #Dependent Patchsets: Messages
Total messages: 59 (40 generated)
Description was changed from ========== Disable scrollbars on the root scroller when using visual viewport scrollbars. On Android, the VisualViewport supplies the scrollbars for the root FrameView and the FrameView blocks its scrollbars from being created. When setting a different element is set as the document.rootScroller, this scrollbar suppression behavior needs to occur as well to prevent two sets of scrollbars from appearing. BUG=505516 ========== to ========== Disable scrollbars on the root scroller when using visual viewport scrollbars. On Android, the VisualViewport supplies the scrollbars for the root FrameView and the FrameView blocks its scrollbars from being created. When setting a different element is set as the document.rootScroller, this scrollbar suppression behavior needs to occur as well to prevent two sets of scrollbars from appearing. BUG=505516 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 ==========
Description was changed from ========== Disable scrollbars on the root scroller when using visual viewport scrollbars. On Android, the VisualViewport supplies the scrollbars for the root FrameView and the FrameView blocks its scrollbars from being created. When setting a different element is set as the document.rootScroller, this scrollbar suppression behavior needs to occur as well to prevent two sets of scrollbars from appearing. BUG=505516 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 ========== to ========== Disable scrollbars on the root scroller when using visual viewport scrollbars. On Android, the VisualViewport supplies the scrollbars for the root FrameView and the FrameView blocks its scrollbars from being created. When setting a different element is set as the document.rootScroller, this scrollbar suppression behavior needs to occur as well to prevent two sets of scrollbars from appearing. BUG=505516 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 ==========
bokan@chromium.org changed reviewers: + skobes@chromium.org
ptal.
The CQ bit was checked by bokan@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...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: cast_shell_linux on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/cast_shell_linu...)
The CQ bit was checked by bokan@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...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: cast_shell_linux on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/cast_shell_linu...)
lgtm w/ nits https://codereview.chromium.org/2501723003/diff/20001/third_party/WebKit/Sour... File third_party/WebKit/Source/core/frame/FrameView.h (right): https://codereview.chromium.org/2501723003/diff/20001/third_party/WebKit/Sour... third_party/WebKit/Source/core/frame/FrameView.h:919: bool visualViewportSuppliesScrollbars(); Why can't this be const anymore? https://codereview.chromium.org/2501723003/diff/20001/third_party/WebKit/Sour... File third_party/WebKit/Source/core/paint/PaintLayerScrollableArea.cpp (right): https://codereview.chromium.org/2501723003/diff/20001/third_party/WebKit/Sour... third_party/WebKit/Source/core/paint/PaintLayerScrollableArea.cpp:1757: layoutBox()->document().frameHost()->globalRootScrollerController(); You could just do frame->host() here.
bokan@chromium.org changed reviewers: + jbroman@chromium.org
+jbroman@ for platform OWNER https://codereview.chromium.org/2501723003/diff/20001/third_party/WebKit/Sour... File third_party/WebKit/Source/core/frame/FrameView.h (right): https://codereview.chromium.org/2501723003/diff/20001/third_party/WebKit/Sour... third_party/WebKit/Source/core/frame/FrameView.h:919: bool visualViewportSuppliesScrollbars(); On 2016/11/15 20:18:43, skobes wrote: > Why can't this be const anymore? Because of the check: root scroller == layoutViewportScrollableArea(), layoutViewportScrollableArea can't be const because if RLS is disabled it returns `this`. The solution would be to add a const overload of layoutViewportScrollableArea() but we've decided long ago that the ship has sailed on const-correctness. https://codereview.chromium.org/2501723003/diff/20001/third_party/WebKit/Sour... File third_party/WebKit/Source/core/paint/PaintLayerScrollableArea.cpp (right): https://codereview.chromium.org/2501723003/diff/20001/third_party/WebKit/Sour... third_party/WebKit/Source/core/paint/PaintLayerScrollableArea.cpp:1757: layoutBox()->document().frameHost()->globalRootScrollerController(); On 2016/11/15 20:18:44, skobes wrote: > You could just do frame->host() here. Done.
platform rs lgtm
The CQ bit was checked by bokan@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...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: cast_shell_linux on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/cast_shell_linu...)
The CQ bit was checked by bokan@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...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
The CQ bit was checked by bokan@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from skobes@chromium.org, jbroman@chromium.org Link to the patchset: https://codereview.chromium.org/2501723003/#ps100001 (title: "Unset upstream")
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 bokan@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from skobes@chromium.org, jbroman@chromium.org Link to the patchset: https://codereview.chromium.org/2501723003/#ps120001 (title: "Fix build after bad rebase")
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: android_arm64_dbg_recipe on master.tryserver.chromium.android (JOB_TIMED_OUT, no build URL) android_clang_dbg_recipe on master.tryserver.chromium.android (JOB_TIMED_OUT, no build URL) android_compile_dbg on master.tryserver.chromium.android (JOB_TIMED_OUT, no build URL) android_cronet on master.tryserver.chromium.android (JOB_TIMED_OUT, no build URL) cast_shell_android on master.tryserver.chromium.android (JOB_TIMED_OUT, no build URL)
The CQ bit was checked by bokan@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: linux_chromium_chromeos_ozone_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
bokan@chromium.org changed reviewers: + victorhsieh@chromium.org
victorhsieh@: Adding you from blame in the failing test. My change is causing the OutOfProcessPPAPITest.Graphics2D test to fail. This patch might change some paint invalidation timing in Blink, particularly around overlay scrollbars. I suspect that the problem is that the invalidation was forcing a flush to happen. Adding a flush to happen before the draw command seems to fix this but I have no idea how this test works or anything around PPAPI so it'd be reassuring if you could confirm this is the right way to fix it. Thanks!
The CQ bit was checked by bokan@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/11/17 17:27:49, bokan wrote: > victorhsieh@: Adding you from blame in the failing test. > > My change is causing the OutOfProcessPPAPITest.Graphics2D test to fail. This > patch might change some paint invalidation timing in Blink, particularly around > overlay scrollbars. I suspect that the problem is that the invalidation was > forcing a flush to happen. Adding a flush to happen before the draw command > seems to fix this but I have no idea how this test works or anything around > PPAPI so it'd be reassuring if you could confirm this is the right way to fix > it. Thanks! Sorry, I do remember I did something to Graphics2D offscreen, but as I only worked on PPAPI for a short period, I don't remember the details :( I'm not sure if bbudge@ is still the maintainer, but he might be help to chime in.
bbudge@chromium.org changed reviewers: + bbudge@chromium.org
ppapi/tests lgtm
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: win_chromium_x64_rel_ng on master.tryserver.chromium.win (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)
The CQ bit was checked by bokan@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from skobes@chromium.org, jbroman@chromium.org Link to the patchset: https://codereview.chromium.org/2501723003/#ps140001 (title: "Fix (?) Graphics2D test")
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: linux_layout_tests_slimming_paint_v2 on master.tryserver.chromium.linux (JOB_TIMED_OUT, no build URL)
The CQ bit was checked by bokan@chromium.org
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.
Description was changed from ========== Disable scrollbars on the root scroller when using visual viewport scrollbars. On Android, the VisualViewport supplies the scrollbars for the root FrameView and the FrameView blocks its scrollbars from being created. When setting a different element is set as the document.rootScroller, this scrollbar suppression behavior needs to occur as well to prevent two sets of scrollbars from appearing. BUG=505516 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 ========== to ========== Disable scrollbars on the root scroller when using visual viewport scrollbars. On Android, the VisualViewport supplies the scrollbars for the root FrameView and the FrameView blocks its scrollbars from being created. When setting a different element is set as the document.rootScroller, this scrollbar suppression behavior needs to occur as well to prevent two sets of scrollbars from appearing. BUG=505516 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 ==========
Message was sent while issue was closed.
Committed patchset #8 (id:140001)
Message was sent while issue was closed.
Description was changed from ========== Disable scrollbars on the root scroller when using visual viewport scrollbars. On Android, the VisualViewport supplies the scrollbars for the root FrameView and the FrameView blocks its scrollbars from being created. When setting a different element is set as the document.rootScroller, this scrollbar suppression behavior needs to occur as well to prevent two sets of scrollbars from appearing. BUG=505516 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 ========== to ========== Disable scrollbars on the root scroller when using visual viewport scrollbars. On Android, the VisualViewport supplies the scrollbars for the root FrameView and the FrameView blocks its scrollbars from being created. When setting a different element is set as the document.rootScroller, this scrollbar suppression behavior needs to occur as well to prevent two sets of scrollbars from appearing. BUG=505516 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 Committed: https://crrev.com/f5a4f9d38de7403d172ad20f78c462048eae37bc Cr-Commit-Position: refs/heads/master@{#432965} ==========
Message was sent while issue was closed.
Patchset 8 (id:??) landed as https://crrev.com/f5a4f9d38de7403d172ad20f78c462048eae37bc Cr-Commit-Position: refs/heads/master@{#432965} |
