Regression : Content disappears after dragging horizontal/vertical scrollbar on chrome://supervised-user-internals/ page.
Reported by
vineetha...@etouch.net,
Oct 9 2017
|
||||||
Issue descriptionChrome version: 63.0.3236.0 2fa96eead8c5eea003b5b7fb4f9262b3d136d76b-refs/heads/master@{#507286}(32/64 Bit) OS: Windows (7,8,10),Linux (14.04 LTS), Mac(10.12.6). Pre - condition : Enough entries should be present in "Filtering Results" box so that scroll bars appear. Steps to reproduce: 1. Launch Chrome. Navigate to chrome://supervised-user-internals/. 2. Now try to scroll horizontally and vertically on "Filtering Results" and observe. Actual Result: Content disappears after dragging scroll bars. Expected Result: Content should not disappear after dragging scroll bars. This is Regression Issue broken in M-63 and will soon update other info, Good Build: 63.0.3222.0 Bad Build: 63.0.3223.0
,
Oct 9 2017
This is Regression Issue broken in M-63 and using the per-revision bisect providing the bisect results, Good Build: 63.0.3222.0((Revision: 503583) Bad Build: 63.0.3223.0((Revision: 503964) You are probably looking for a change made after 503936 (known good), but no later than 503937 (first known bad). CHANGELOG URL: The script might not always return single CL as suspect as some perf builds might get missing due to failure. https://chromium.googlesource.com/chromium/src/+log/bfc521be486382153ebe7a4397ad332b3f1fe8f8..32627dcf9b7657f76d2d86ba3f762fba8dda7f1b Suspect : https://chromium.googlesource.com/chromium/src/+/32627dcf9b7657f76d2d86ba3f762fba8dda7f1b @chrishtr : Could you please look into the issue, pardon me if it has nothing to do with your changes and if possible please assign it to concern owner.
,
Oct 10 2017
Tagging with blocker label, please undo if not the case.
,
Oct 11 2017
,
Oct 12 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/a2c40a2255d7157442e40f1ec384f5e5bced0e0d commit a2c40a2255d7157442e40f1ec384f5e5bced0e0d Author: Chris Harrelson <chrishtr@chromium.org> Date: Thu Oct 12 20:00:44 2017 Don't include scroll offset in paint offset translation for fragmented content. This fixes a bug in which we would incorrectly include local scroll offset in the paint offset translation, due to updating paint_offset_root too early (needs to be set after paint offset is updated). Bug: 772853 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 Change-Id: I1c4c80f3a8d2dc1b737f4b0bb7955b4d8c95fb26 Reviewed-on: https://chromium-review.googlesource.com/714438 Commit-Queue: Chris Harrelson <chrishtr@chromium.org> Reviewed-by: Tien-Ren Chen <trchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#508409} [modify] https://crrev.com/a2c40a2255d7157442e40f1ec384f5e5bced0e0d/third_party/WebKit/Source/core/paint/PaintPropertyTreeBuilder.cpp [modify] https://crrev.com/a2c40a2255d7157442e40f1ec384f5e5bced0e0d/third_party/WebKit/Source/core/paint/PaintPropertyTreeBuilderTest.cpp
,
Oct 12 2017
,
Oct 13 2017
[Auto-generated comment by a script] We noticed that this issue is targeted for M-63; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-63 label, otherwise remove Merge-TBD label. Thanks.
,
Oct 13 2017
M63 (branch #3239) is branched at chromium revision 508578. So cl listed at #6 is already in M63. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by ranjitkan@chromium.org
, Oct 9 2017Status: Untriaged (was: Unconfirmed)