DevTools: Fix console input to avoid scrolling issues
Reported by
cont...@ehsankia.com,
May 22 2016
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.54 Safari/537.36 Steps to reproduce the problem: 1. Go to a website that sends many console log events rapidly 2. scroll to the bottom and try typing commands in the console What is the expected behavior? You can see what you are typing at all times What went wrong? The console input keeps jumping out of view as new log events come in Did this work before? Yes Chrome 49 (not completely sure on this one) Chrome version: 51.0.2704.54 Channel: beta OS Version: 10.0 Flash Version: Shockwave Flash 21.0 r0 Here is a short gif displaying the problem: https://gfycat.com/EssentialWeepyAmphibian
,
May 23 2016
If you scroll console to the bottom, it should stick and input line should be visible all the time. Does this work for you?
,
May 23 2016
After looking into it further, it seems like there are certain console messages which break the auto scroll. I believe one of these are multi-line warning messages. Here's a repro that consistently works for me: 1. Go to https://jsfiddle.net/zpx0ypz0/ 2. Open console 3. Wait for the messages to fill the page Expected result: Page stays scrolled at the bottom as new message come in Actual result: After a few messages, page fails to properly scroll down and input disappears below. Here's another short video displaying the issue: https://gfycat.com/HealthyShamelessIcterinewarbler Note that I'm not touching anything in this video
,
May 25 2016
Can confirm, multi-line warnings break console scrolling in Version 50.0.2661.94 (64-bit). It's really driving me crazy.
,
Jul 15 2016
,
Jul 15 2016
,
Jul 22 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/2dbbaccdef5a4b1f1348792a8b5be93e58507d33 commit 2dbbaccdef5a4b1f1348792a8b5be93e58507d33 Author: luoe <luoe@chromium.org> Date: Fri Jul 22 04:43:07 2016 DevTools: remove isTrusted check and isUserGesture from ViewportControl Previously, the ViewportControl never stuck to the bottom after a scroll event. The event.isTrusted check was always true, so it was not correctly distinguishing user-generated scroll events from script-generated ones. This CL removes isUserGesture accordingly. BUG= 613879 Review-Url: https://codereview.chromium.org/2154893002 Cr-Commit-Position: refs/heads/master@{#407062} [modify] https://crrev.com/2dbbaccdef5a4b1f1348792a8b5be93e58507d33/third_party/WebKit/LayoutTests/inspector/console/console-viewport-selection-expected.txt [modify] https://crrev.com/2dbbaccdef5a4b1f1348792a8b5be93e58507d33/third_party/WebKit/LayoutTests/inspector/console/console-viewport-selection.html [modify] https://crrev.com/2dbbaccdef5a4b1f1348792a8b5be93e58507d33/third_party/WebKit/LayoutTests/inspector/console/console-viewport-stick-to-bottom.html [modify] https://crrev.com/2dbbaccdef5a4b1f1348792a8b5be93e58507d33/third_party/WebKit/Source/devtools/front_end/ui/ViewportControl.js
,
Jul 26 2016
The CL above should fix this bug on Canary. For reference, rapidly logging messages that include DOM nodes, functions, or custom formatters doesn't behave well yet. That should be addressed in issue #603294 |
||||
►
Sign in to add a comment |
||||
Comment 1 by eostroukhov@chromium.org
, May 23 2016Status: Assigned (was: Unconfirmed)