Issue metadata
Sign in to add a comment
|
Content is not shown on the page
Reported by
rusterho...@gmail.com,
Oct 24
|
||||||||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.67 Safari/537.36 Example URL: https://gavekort.legoland.dk/pages/privacy-policy.aspx Steps to reproduce the problem: 1. Go to the site: https://gavekort.legoland.dk/pages/privacy-policy.aspx 2. Scroll down without selecting things on the page and then bottom content should not be visible. What is the expected behavior? When you enter the site, it stops showing content at a certain point, so that HTML is simply not visible! What went wrong? Content on the page is not visible. Does it occur on multiple sites: N/A Is it a problem with a plugin? No Did this work before? Yes I belive it worked before 69.0.3497.100. Does this work in other browsers? Yes Chrome version: 70.0.3538.67 Channel: stable OS Version: 10.0 Flash Version:
,
Oct 24
,
Oct 25
Able to reproduce the issue on reported chrome version #70.0.3538.67 and latest chrome #72.0.3590.0 using Windows 10. Note: For reproducing the issue need to enable #network-service flag and this issue is windows specific only. The behavior is seen from old M-60 builds(#60.0.3112.113). This is a non-regression issue, hence marking it as untriaged and requesting someone from the dev team to kindly look into this. Thanks.!
,
Oct 25
Looks like a paint issue.
,
Oct 26
,
Oct 26
Are we sure about the #network-service flag? Seem like this is a networking issue if that is the case. swarnasree.mukkala@, could you please confirm that reproduction step.
,
Oct 29
In reply to comment#6, the following are the steps to reproduce the issue. Steps: ===== 1.Launched chrome. 2.Enabled "#network-service" flag. 3.Navigated to "https://gavekort.legoland.dk/pages/privacy-policy.aspx ". 4.Scroll down the page and observed that only background of the page gets loaded but the content of the page does not load. 5.Tried clicking on the button "BETINGELSER" button. 6.Observed same behaviour as the background of the page gets loaded but the content does not load. Note: When checked today on Linux(Ubuntu 17.10) and Mac OS 10.13.1 observed inconsistent behaviour on reported chrome version #70.0.3538.67, as the issue gets reproduced after when tried to load pages by clicking multiple times on "BETINGELSER" and "PRIVATLIVSPOLITIK" buttons. Thanks.!
,
Oct 29
,
Oct 31
,
Nov 2
,
Nov 6
,
Nov 6
,
Nov 6
I bisected back to r576753 (69.0.3497.100) and this bug existed there too. Note: this isn't 100% reproducible (at least on linux64), but with two launches of Chromium it almost always is. This is a render/layout bug. If the page gets into a state where it isn't rendered it can be fixed by resizing the window. I was able to reproduce this several times *without* the network service enabled at 605739.
,
Nov 6
Forgot to note. The best way to reproduce is to invoke directly from the command line. out/Debug/chrome --user-data-dir=~/.chrome_dev https://gavekort.legoland.dk/pages/privacy-policy.aspx 3-5 invocations (just launch and scroll the page down) will usually reproduce.
,
Nov 6
,
Nov 6
,
Nov 6
Did a bit more bisecting on Linux and Windows using: tools/bisect-builds.py --good=506753 --bad=605739 --archive=linux64 --use-local-cache --command="%p %a https://gavekort.legoland.dk/pages/privacy-policy.aspx" For Windows it reported: https://chromium.googlesource.com/chromium/src/+log/481e6b0f05f34b8fbf9ae580e0bf226dca6765f3..26121cb9c1988b713d8a4ad2fe849ef7f5399099 For Linux it reported: https://chromium.googlesource.com/chromium/src/+log/481e6b0f05f34b8fbf9ae580e0bf226dca6765f3..42baf2077e5075c5ae967038f2404fff3262ba66 My guess is that this is the cause of this regression: https://chromium.googlesource.com/chromium/src/+/b3b5e3b9da74b2da80010f7a4c558bcc0b0d007a which first appeared in 69.0.3473.0
,
Nov 6
Oh, sorry for spamming the comments, but here are more reliable repro steps: 1. Launch Chrome from the command line as so: path/to/chrome https://gavekort.legoland.dk/pages/privacy-policy.aspx 2. Wait for page to load and for the green favicon to be displayed. 3. Scroll down the page.
,
Nov 7
reassigning based on C#17.
,
Nov 7
,
Nov 7
I'm seeing a consistent repro on current# 70.0.3538.77 & previous stable# 69.0.3497.100 version of chrome on Win10 (With Network service flag enabled). Not very sure if this blocks M70 stable since it's exists from M69.
,
Nov 7
hmm interesting.. if you launch chrome from command line then this issue is reproducible even without 'Network service' flag enabled for the chrome versions mentioned in c#21.
,
Nov 7
Are there any workaround flags that can be passed through command line to circumvent this issue? Is this also present in M69?
,
Nov 8
,
Nov 9
Reduced test case attached. Before the bug is fixed, the web page can use one of the following methods to work around the issue: 1. Add style="height: auto" to either <html> or <body>; 2. Add style="z-index: auto" to <div id="container">; 3. Add style="position: static" to <div id="container">.
,
Nov 9
Note for release managers. This issue has shown up in various forms in several reports. I'll do my best to merge them all in, but be aware that this might warrant a Stable re-spin when it's fixed.
,
Nov 10
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/9fccf8f9603f9dd5766fe64db8a5cdbd9fb550c2 commit 9fccf8f9603f9dd5766fe64db8a5cdbd9fb550c2 Author: Xianzhu Wang <wangxianzhu@chromium.org> Date: Sat Nov 10 00:11:05 2018 [PE] Cached subsequence should retain previous paint result If a subsequence previously partially painted, when we use the cached without repainting, we should still treat the layer as partially painted, otherwise we'll fail to repaint on paint dirty rect change. Bug: 898435 Change-Id: I27ec2689377aaf408a819f2849675640c439fcd9 Reviewed-on: https://chromium-review.googlesource.com/c/1329701 Reviewed-by: Chris Harrelson <chrishtr@chromium.org> Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#607041} [modify] https://crrev.com/9fccf8f9603f9dd5766fe64db8a5cdbd9fb550c2/third_party/blink/renderer/core/paint/paint_layer_painter.cc [modify] https://crrev.com/9fccf8f9603f9dd5766fe64db8a5cdbd9fb550c2/third_party/blink/renderer/core/paint/paint_layer_painter_test.cc
,
Nov 10
The fix is straight-forward and quite safe to merge. I'm not in office and don't have a machine that can test canary build. Anyone please help verify on the next Canary build. Thanks.
,
Nov 11
This bug requires manual review: M71 has already been promoted to the beta branch, so this requires manual review Please contact the milestone owner if you have questions. Owners: benmason@(Android), kariahda@(iOS), kbleicher@(ChromeOS), govind@(Desktop) For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 12
The NextAction date has arrived: 2018-11-12
,
Nov 12
Approving this merge for M71. Rejecting this for M70.
,
Nov 12
Pls merge your change to M71 branch 3578 ASAP. Thank you.
,
Nov 12
Reg c#29: The fix is working as intended (tested reduced test case (c#26) as well) on Latest Canary# 72.0.3608.0 for Win, Mac & Linux platforms.
,
Nov 13
Issue 900660 has been merged into this issue.
,
Nov 13
,
Nov 13
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/e28dfd14714f213f6b6c3d1a4718fa0254f26556 commit e28dfd14714f213f6b6c3d1a4718fa0254f26556 Author: Xianzhu Wang <wangxianzhu@chromium.org> Date: Tue Nov 13 03:26:56 2018 [PE] Cached subsequence should retain previous paint result If a subsequence previously partially painted, when we use the cached without repainting, we should still treat the layer as partially painted, otherwise we'll fail to repaint on paint dirty rect change. TBR=wangxianzhu@chromium.org (cherry picked from commit 9fccf8f9603f9dd5766fe64db8a5cdbd9fb550c2) Bug: 898435 Change-Id: I27ec2689377aaf408a819f2849675640c439fcd9 Reviewed-on: https://chromium-review.googlesource.com/c/1329701 Reviewed-by: Chris Harrelson <chrishtr@chromium.org> Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#607041} Reviewed-on: https://chromium-review.googlesource.com/c/1332968 Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/branch-heads/3578@{#650} Cr-Branched-From: 4226ddf99103e493d7afb23a4c7902ee496108b6-refs/heads/master@{#599034} [modify] https://crrev.com/e28dfd14714f213f6b6c3d1a4718fa0254f26556/third_party/blink/renderer/core/paint/paint_layer_painter.cc [modify] https://crrev.com/e28dfd14714f213f6b6c3d1a4718fa0254f26556/third_party/blink/renderer/core/paint/paint_layer_painter_test.cc
,
Nov 13
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/e28dfd14714f213f6b6c3d1a4718fa0254f26556 Commit: e28dfd14714f213f6b6c3d1a4718fa0254f26556 Author: wangxianzhu@chromium.org Commiter: wangxianzhu@chromium.org Date: 2018-11-13 03:26:56 +0000 UTC [PE] Cached subsequence should retain previous paint result If a subsequence previously partially painted, when we use the cached without repainting, we should still treat the layer as partially painted, otherwise we'll fail to repaint on paint dirty rect change. TBR=wangxianzhu@chromium.org (cherry picked from commit 9fccf8f9603f9dd5766fe64db8a5cdbd9fb550c2) Bug: 898435 Change-Id: I27ec2689377aaf408a819f2849675640c439fcd9 Reviewed-on: https://chromium-review.googlesource.com/c/1329701 Reviewed-by: Chris Harrelson <chrishtr@chromium.org> Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#607041} Reviewed-on: https://chromium-review.googlesource.com/c/1332968 Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/branch-heads/3578@{#650} Cr-Branched-From: 4226ddf99103e493d7afb23a4c7902ee496108b6-refs/heads/master@{#599034}
,
Nov 14
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/0dc2d7e6ea2e94b6d757f0ff263dc0949edcd71b commit 0dc2d7e6ea2e94b6d757f0ff263dc0949edcd71b Author: Wei-Yin Chen (陳威尹) <wychen@chromium.org> Date: Wed Nov 14 05:51:42 2018 Revert "[PE] Cached subsequence should retain previous paint result" This reverts commit e28dfd14714f213f6b6c3d1a4718fa0254f26556. Reason for revert: https://crbug.com/905159 Original change's description: > [PE] Cached subsequence should retain previous paint result > > If a subsequence previously partially painted, when we use the cached > without repainting, we should still treat the layer as partially > painted, otherwise we'll fail to repaint on paint dirty rect change. > > TBR=wangxianzhu@chromium.org > > (cherry picked from commit 9fccf8f9603f9dd5766fe64db8a5cdbd9fb550c2) > > Bug: 898435 > Change-Id: I27ec2689377aaf408a819f2849675640c439fcd9 > Reviewed-on: https://chromium-review.googlesource.com/c/1329701 > Reviewed-by: Chris Harrelson <chrishtr@chromium.org> > Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> > Cr-Original-Commit-Position: refs/heads/master@{#607041} > Reviewed-on: https://chromium-review.googlesource.com/c/1332968 > Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org> > Cr-Commit-Position: refs/branch-heads/3578@{#650} > Cr-Branched-From: 4226ddf99103e493d7afb23a4c7902ee496108b6-refs/heads/master@{#599034} TBR=wangxianzhu@chromium.org,chrishtr@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 898435 Change-Id: Ifcae06c91020b392e3690aa2c155fc32082bd140 Reviewed-on: https://chromium-review.googlesource.com/c/1335276 Reviewed-by: Wei-Yin Chen (陳威尹) <wychen@chromium.org> Cr-Commit-Position: refs/branch-heads/3578@{#677} Cr-Branched-From: 4226ddf99103e493d7afb23a4c7902ee496108b6-refs/heads/master@{#599034} [modify] https://crrev.com/0dc2d7e6ea2e94b6d757f0ff263dc0949edcd71b/third_party/blink/renderer/core/paint/paint_layer_painter.cc [modify] https://crrev.com/0dc2d7e6ea2e94b6d757f0ff263dc0949edcd71b/third_party/blink/renderer/core/paint/paint_layer_painter_test.cc
,
Nov 14
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/0dc2d7e6ea2e94b6d757f0ff263dc0949edcd71b Commit: 0dc2d7e6ea2e94b6d757f0ff263dc0949edcd71b Author: wychen@chromium.org Commiter: wychen@chromium.org Date: 2018-11-14 05:51:42 +0000 UTC Revert "[PE] Cached subsequence should retain previous paint result" This reverts commit e28dfd14714f213f6b6c3d1a4718fa0254f26556. Reason for revert: https://crbug.com/905159 Original change's description: > [PE] Cached subsequence should retain previous paint result > > If a subsequence previously partially painted, when we use the cached > without repainting, we should still treat the layer as partially > painted, otherwise we'll fail to repaint on paint dirty rect change. > > TBR=wangxianzhu@chromium.org > > (cherry picked from commit 9fccf8f9603f9dd5766fe64db8a5cdbd9fb550c2) > > Bug: 898435 > Change-Id: I27ec2689377aaf408a819f2849675640c439fcd9 > Reviewed-on: https://chromium-review.googlesource.com/c/1329701 > Reviewed-by: Chris Harrelson <chrishtr@chromium.org> > Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> > Cr-Original-Commit-Position: refs/heads/master@{#607041} > Reviewed-on: https://chromium-review.googlesource.com/c/1332968 > Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org> > Cr-Commit-Position: refs/branch-heads/3578@{#650} > Cr-Branched-From: 4226ddf99103e493d7afb23a4c7902ee496108b6-refs/heads/master@{#599034} TBR=wangxianzhu@chromium.org,chrishtr@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 898435 Change-Id: Ifcae06c91020b392e3690aa2c155fc32082bd140 Reviewed-on: https://chromium-review.googlesource.com/c/1335276 Reviewed-by: Wei-Yin Chen (陳威尹) <wychen@chromium.org> Cr-Commit-Position: refs/branch-heads/3578@{#677} Cr-Branched-From: 4226ddf99103e493d7afb23a4c7902ee496108b6-refs/heads/master@{#599034}
,
Nov 14
Pls do not merge this change to M71 anymore as cl got reverted at #40 due to https://crbug.com/905159 .
,
Nov 14
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/998257d310ff20ec29b978012e914669fed71276 commit 998257d310ff20ec29b978012e914669fed71276 Author: Xianzhu Wang <wangxianzhu@chromium.org> Date: Wed Nov 14 06:39:38 2018 Reland "[PE] Cached subsequence should retain previous paint result" This is a reland of e28dfd14714f213f6b6c3d1a4718fa0254f26556 Original change's description: > [PE] Cached subsequence should retain previous paint result > > If a subsequence previously partially painted, when we use the cached > without repainting, we should still treat the layer as partially > painted, otherwise we'll fail to repaint on paint dirty rect change. > > TBR=wangxianzhu@chromium.org > > (cherry picked from commit 9fccf8f9603f9dd5766fe64db8a5cdbd9fb550c2) > > Bug: 898435 > Change-Id: I27ec2689377aaf408a819f2849675640c439fcd9 > Reviewed-on: https://chromium-review.googlesource.com/c/1329701 > Reviewed-by: Chris Harrelson <chrishtr@chromium.org> > Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> > Cr-Original-Commit-Position: refs/heads/master@{#607041} > Reviewed-on: https://chromium-review.googlesource.com/c/1332968 > Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org> > Cr-Commit-Position: refs/branch-heads/3578@{#650} > Cr-Branched-From: 4226ddf99103e493d7afb23a4c7902ee496108b6-refs/heads/master@{#599034} Bug: 898435 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel Change-Id: I4356acd7fde95d9277e3f76ff3276d6fedf99573 Reviewed-on: https://chromium-review.googlesource.com/c/1335073 Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/branch-heads/3578@{#680} Cr-Branched-From: 4226ddf99103e493d7afb23a4c7902ee496108b6-refs/heads/master@{#599034} [modify] https://crrev.com/998257d310ff20ec29b978012e914669fed71276/third_party/blink/renderer/core/paint/paint_layer_painter.cc
,
Nov 14
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/998257d310ff20ec29b978012e914669fed71276 Commit: 998257d310ff20ec29b978012e914669fed71276 Author: wangxianzhu@chromium.org Commiter: wangxianzhu@chromium.org Date: 2018-11-14 06:39:38 +0000 UTC Reland "[PE] Cached subsequence should retain previous paint result" This is a reland of e28dfd14714f213f6b6c3d1a4718fa0254f26556 Original change's description: > [PE] Cached subsequence should retain previous paint result > > If a subsequence previously partially painted, when we use the cached > without repainting, we should still treat the layer as partially > painted, otherwise we'll fail to repaint on paint dirty rect change. > > TBR=wangxianzhu@chromium.org > > (cherry picked from commit 9fccf8f9603f9dd5766fe64db8a5cdbd9fb550c2) > > Bug: 898435 > Change-Id: I27ec2689377aaf408a819f2849675640c439fcd9 > Reviewed-on: https://chromium-review.googlesource.com/c/1329701 > Reviewed-by: Chris Harrelson <chrishtr@chromium.org> > Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> > Cr-Original-Commit-Position: refs/heads/master@{#607041} > Reviewed-on: https://chromium-review.googlesource.com/c/1332968 > Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org> > Cr-Commit-Position: refs/branch-heads/3578@{#650} > Cr-Branched-From: 4226ddf99103e493d7afb23a4c7902ee496108b6-refs/heads/master@{#599034} Bug: 898435 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel Change-Id: I4356acd7fde95d9277e3f76ff3276d6fedf99573 Reviewed-on: https://chromium-review.googlesource.com/c/1335073 Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/branch-heads/3578@{#680} Cr-Branched-From: 4226ddf99103e493d7afb23a4c7902ee496108b6-refs/heads/master@{#599034} |
|||||||||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||||||||
Comment 1 by dtapu...@chromium.org
, Oct 24