Issue metadata
Sign in to add a comment
|
Form elements disappears after scroll
Reported by
kakarot...@gmail.com,
Oct 25
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36 Steps to reproduce the problem: 1. Open Chrome 70.0.3538.77 - Windows 10 2. Open attach file, see there one text input at top. 3. Reduce height of Chrome to get Scroll. 4. Scroll down and up, text input disappears. What is the expected behavior? Text input don't disappears What went wrong? Text input disappears. Did this work before? Yes I think 2 updates berore... Does this work in other browsers? Yes Chrome version: 70.0.3538.77 Channel: stable OS Version: 10.0 Flash Version: Hi, I just reporting, I already fixed my old CSS workaround for ie6, issue is overflow on style, but it worked on other browser. Maybe it can help if similar issue. Cya.
,
Oct 26
Thanks for filing the issue! Unable to reproduce the issue on reported chrome version 70.0.3538.77 using Windows 10 with the below mentioned steps. 1. Launched Chrome 2. Opened chrome-bug-02553.html in a new tab 3. Resized the tap/window 4. Scrolled the page. We didn't observe any elements getting disappeared when scrolled. Attaching the screencast of the same. @Reporter: Could you please have a look at the screen cast and let us know if we have missed anything in the process. Any further inputs from your end may be helpful.
,
Oct 26
Hi. The process is correct, I'm tested 4 on computers and problem appears too. What's the screen cast software you are using ? Another information, I tested on Chrome 69 and there no problem (after update to 70 the problem appears). Thanks.
,
Oct 26
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 29
Thanks for filling the issue... Retried the issue on reported chrome version 70.0.3538.77 using Windows 10. Attaching screen-cast for reference. Steps: --------- 1. Launched Chrome 2. Opened chrome-bug-02553.html in a new tab 3. Resized the tap/window and scrolled the page. As We have not seen any elements getting disappeared when scrolled down and up. @Reporter:Can you verify this issue with fresh profile that is not having any extensions and apps or reset all the flags and Requesting someone from Blink>Scroll team to look in to it for further triaging it. Removing Needs-Bisect label to it feel free to if required. Thanks.!
,
Oct 29
Hi! I removed my user profile on Chrome, uninstalled and wiped folder in %appdata%, executed all updates on Windows 10 ver.1803, update Video Driver for GeForce GT 640. Restarted several times. New fresh install of Chrome 70.0.3538.77. Tested with and without hardware accellaration. The issue still there, I don't known witch test I can do now. The issue appears on all computer I tested (+/-10)... maybe is our Windows or Localization.. Thanks.
,
Nov 1
Looks more like an invalidation issue. Changing component to Blink>Paint. Is there anything else reporter can try to narrow down the cause? One more thing to try - make sure you reset all flags in chrome://flags.
,
Nov 1
Hi! I reseted all flags and the issue still there (screen cast: screeencast-20181101a.mp4). But, messing around with flags, I discovery with flag fix problem: LCD text antialiasing If I disable it, the problem is fixed (screen cast: screeencast-20181101b.mp4). Worked too on 72.0.3598.0 (Official Build) canary (64-bit). Also I tired change on Windows some related settings, but didn't work: - Performance Options->Visual Effects->"Smooth edges of screen fonts" - Windows Settings->Personalization->Fonts->"Clear Type" I hope this help narrow down the cause. Thanks.
,
Nov 2
Able to reproduce the issue on Windows 10 using chrome reported version #70.0.3538.77 and latest canary #72.0.3599.0. Issue is specific to OS-win. Bisect Information: ===================== Good build: 70.0.3534.0 Bad Build : 70.0.3535.0 Change Log URL: https://chromium.googlesource.com/chromium/src/+log/7e27cfaca58d81d74a25460d2021592ce6174841..87237f87304e8ee3c9857c9499b4dd4d4a52ca2a From the above change log suspecting below change Change-Id: Ia48ad8ddc5d63225ccca1a2b8d6f26920de605a5 Reviewed-on: https://chromium-review.googlesource.com/1190923 chrishtr@ - Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner. Note: Adding stable blocker for M-70 as it seems to be a recent regression. Please feel free to remove the same if not appropriate. Thanks...!!
,
Nov 2
,
Nov 5
M71 Stable promotion is coming VERY soon. Your bug is labelled as Stable ReleaseBlock, pls make sure to land the fix and request a merge into the release branch ASAP. Thank you.
,
Nov 6
Reduced testcase attached.
,
Nov 6
I think the bug has to do with an optimization to skip the float paint phase.
,
Nov 7
,
Nov 8
M71 Stable promotion is coming VERY soon. Your bug is labelled as Stable ReleaseBlock, pls make sure to land the fix and request a merge into the release branch ASAP. Thank you.
,
Nov 8
This issue is marked as a release blocker with no milestone associated. Please add an appropriate milestone. All release blocking issues should have milestones associated to it, so that the issue can tracked and the fixes can be pushed promptly. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 8
,
Nov 9
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/7f6f0f6a7cb3b0845cd39f930c17d4c915ed8c9b commit 7f6f0f6a7cb3b0845cd39f930c17d4c915ed8c9b Author: Chris Harrelson <chrishtr@chromium.org> Date: Fri Nov 09 02:21:06 2018 [PE] Get rid of empty paint phase detection. This caused issues in cases where we skip caches, have special paint paths, and culling in the presence of non-composited overflow clipping. There are still optimizations for absence of paint phases generally. This CL just removes ones where we detect "empty" by means of no change to the display list. Bug: 898995 , 901302 Change-Id: Ib3f79a615c88d0e97f4c9cec78056bf00e1358c6 Reviewed-on: https://chromium-review.googlesource.com/c/1320972 Commit-Queue: Chris Harrelson <chrishtr@chromium.org> Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#606696} [modify] https://crrev.com/7f6f0f6a7cb3b0845cd39f930c17d4c915ed8c9b/third_party/WebKit/LayoutTests/FlagExpectations/enable-slimming-paint-v2 [add] https://crrev.com/7f6f0f6a7cb3b0845cd39f930c17d4c915ed8c9b/third_party/WebKit/LayoutTests/paint/invalidation/float-offscreen-expected.html [add] https://crrev.com/7f6f0f6a7cb3b0845cd39f930c17d4c915ed8c9b/third_party/WebKit/LayoutTests/paint/invalidation/float-offscreen.html [add] https://crrev.com/7f6f0f6a7cb3b0845cd39f930c17d4c915ed8c9b/third_party/WebKit/LayoutTests/platform/linux/paint/invalidation/float-offscreen-expected.txt [add] https://crrev.com/7f6f0f6a7cb3b0845cd39f930c17d4c915ed8c9b/third_party/WebKit/LayoutTests/platform/mac/paint/invalidation/float-offscreen-expected.txt [add] https://crrev.com/7f6f0f6a7cb3b0845cd39f930c17d4c915ed8c9b/third_party/WebKit/LayoutTests/platform/win/paint/invalidation/float-offscreen-expected.txt [modify] https://crrev.com/7f6f0f6a7cb3b0845cd39f930c17d4c915ed8c9b/third_party/blink/renderer/core/paint/README.md [modify] https://crrev.com/7f6f0f6a7cb3b0845cd39f930c17d4c915ed8c9b/third_party/blink/renderer/core/paint/paint_layer.cc [modify] https://crrev.com/7f6f0f6a7cb3b0845cd39f930c17d4c915ed8c9b/third_party/blink/renderer/core/paint/paint_layer.h [modify] https://crrev.com/7f6f0f6a7cb3b0845cd39f930c17d4c915ed8c9b/third_party/blink/renderer/core/paint/paint_layer_painter.cc [modify] https://crrev.com/7f6f0f6a7cb3b0845cd39f930c17d4c915ed8c9b/third_party/blink/renderer/core/paint/paint_layer_painter_test.cc [modify] https://crrev.com/7f6f0f6a7cb3b0845cd39f930c17d4c915ed8c9b/third_party/blink/renderer/core/paint/pre_paint_tree_walk.cc
,
Nov 9
Will request merge on Monday.
,
Nov 12
,
Nov 12
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
As this is regressed in M70 and M71 is very close to stable promotion, could you pls justify the merge?
,
Nov 12
The justification is that the circumstances when this can happen are probably common, because it just involves floats and non-composited scrolling. The CL to fix just removed an optimization, and did not change core business logic, so I think it should be relatively safe.
,
Nov 12
Approving merge to M71 branch 3578 based on comment #25.
,
Nov 12
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/e4cf4c697e7355340b145f97f16ada7be7ee5173 commit e4cf4c697e7355340b145f97f16ada7be7ee5173 Author: Chris Harrelson <chrishtr@chromium.org> Date: Mon Nov 12 17:55:18 2018 [PE] Get rid of empty paint phase detection. This caused issues in cases where we skip caches, have special paint paths, and culling in the presence of non-composited overflow clipping. There are still optimizations for absence of paint phases generally. This CL just removes ones where we detect "empty" by means of no change to the display list. Bug: 898995 , 901302 TBR=chrishtr@chromium.org (cherry picked from commit 7f6f0f6a7cb3b0845cd39f930c17d4c915ed8c9b) Change-Id: Ib3f79a615c88d0e97f4c9cec78056bf00e1358c6 Reviewed-on: https://chromium-review.googlesource.com/c/1320972 Commit-Queue: Chris Harrelson <chrishtr@chromium.org> Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#606696} Reviewed-on: https://chromium-review.googlesource.com/c/1331628 Reviewed-by: Chris Harrelson <chrishtr@chromium.org> Cr-Commit-Position: refs/branch-heads/3578@{#635} Cr-Branched-From: 4226ddf99103e493d7afb23a4c7902ee496108b6-refs/heads/master@{#599034} [add] https://crrev.com/e4cf4c697e7355340b145f97f16ada7be7ee5173/third_party/WebKit/LayoutTests/paint/invalidation/float-offscreen-expected.html [add] https://crrev.com/e4cf4c697e7355340b145f97f16ada7be7ee5173/third_party/WebKit/LayoutTests/paint/invalidation/float-offscreen.html [add] https://crrev.com/e4cf4c697e7355340b145f97f16ada7be7ee5173/third_party/WebKit/LayoutTests/platform/linux/paint/invalidation/float-offscreen-expected.txt [add] https://crrev.com/e4cf4c697e7355340b145f97f16ada7be7ee5173/third_party/WebKit/LayoutTests/platform/mac/paint/invalidation/float-offscreen-expected.txt [add] https://crrev.com/e4cf4c697e7355340b145f97f16ada7be7ee5173/third_party/WebKit/LayoutTests/platform/win/paint/invalidation/float-offscreen-expected.txt [modify] https://crrev.com/e4cf4c697e7355340b145f97f16ada7be7ee5173/third_party/blink/renderer/core/paint/README.md [modify] https://crrev.com/e4cf4c697e7355340b145f97f16ada7be7ee5173/third_party/blink/renderer/core/paint/paint_layer.cc [modify] https://crrev.com/e4cf4c697e7355340b145f97f16ada7be7ee5173/third_party/blink/renderer/core/paint/paint_layer.h [modify] https://crrev.com/e4cf4c697e7355340b145f97f16ada7be7ee5173/third_party/blink/renderer/core/paint/paint_layer_painter.cc [modify] https://crrev.com/e4cf4c697e7355340b145f97f16ada7be7ee5173/third_party/blink/renderer/core/paint/paint_layer_painter_test.cc [modify] https://crrev.com/e4cf4c697e7355340b145f97f16ada7be7ee5173/third_party/blink/renderer/core/paint/pre_paint_tree_walk.cc
,
Nov 12
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/e4cf4c697e7355340b145f97f16ada7be7ee5173 Commit: e4cf4c697e7355340b145f97f16ada7be7ee5173 Author: chrishtr@chromium.org Commiter: chrishtr@chromium.org Date: 2018-11-12 17:55:18 +0000 UTC [PE] Get rid of empty paint phase detection. This caused issues in cases where we skip caches, have special paint paths, and culling in the presence of non-composited overflow clipping. There are still optimizations for absence of paint phases generally. This CL just removes ones where we detect "empty" by means of no change to the display list. Bug: 898995 , 901302 TBR=chrishtr@chromium.org (cherry picked from commit 7f6f0f6a7cb3b0845cd39f930c17d4c915ed8c9b) Change-Id: Ib3f79a615c88d0e97f4c9cec78056bf00e1358c6 Reviewed-on: https://chromium-review.googlesource.com/c/1320972 Commit-Queue: Chris Harrelson <chrishtr@chromium.org> Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#606696} Reviewed-on: https://chromium-review.googlesource.com/c/1331628 Reviewed-by: Chris Harrelson <chrishtr@chromium.org> Cr-Commit-Position: refs/branch-heads/3578@{#635} Cr-Branched-From: 4226ddf99103e493d7afb23a4c7902ee496108b6-refs/heads/master@{#599034}
,
Nov 12
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by swarnasree.mukkala@chromium.org
, Oct 26