New history/suggestions in devtools console is disruptive
Reported by
majorzb...@gmail.com,
Mar 15 2016
|
||||||
Issue description
Chrome Version : 49.0.2623.87
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 5:
Firefox 4.x:
IE 7/8/9:
What steps will reproduce the problem?
1. Open DevTools console
2. Type something like "docament" (misspelled document)
3. Go to any other page
4. Start typing "do"
What is the expected result?
"docament" is not in the history/autocomplete
What happens instead of that?
"docament" is suggested by the autocomplete, no way of knowing if it is a real window property/local variable or just a random word you accidentally typed on another page.
Please provide any additional information below. Attach a screenshot if
possible.
UserAgentString: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.87 Safari/537.36
,
Mar 16 2016
Hi, I couldn't find your screen recording. I attach my screen recording for a simple scenario where I type some random string and from that moment on it becomes a suggestion. Now think of a real world scenario where I am debugging some function and type some variable name "myVar". Then I go to a completely different page and debug another function. I still get "myVar" as a suggestion of autocomplete. This is very confusing as I have no way of knowing if this is an incorrect suggestion from another page or an actual variable defined in the scope. If this is a bug please fix it. If this is a feature, please add an option to disable it. Thanks.
,
Mar 16 2016
Thank you for providing more feedback. Assigning to requester "rnimmagadda@chromium.org" for another review. For more details visit https://sites.google.com/a/chromium.org/dev/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 17 2016
@majorzbzzn: Now attached the screen-recording, please have a look. Thank you.
,
Mar 17 2016
Hi, Your screen recording has absolutely no connection with my bug report. The problem is only *within* the DevTools console not the URL. Here are the updated steps: 1. Open DevTools console 2. Type something like "docament" (misspelled document) 3. Go to any other page 4. Start typing "do" in the DevTools console - You are getting "docament" as a valid suggestion for the current scope (i.e. window)
,
Mar 17 2016
@majorzbzzn: Please provide us the screen-recording for better understanding. Please have a look at the attached-screening and let us know if this is the correct behavior. Thank you.
,
Mar 17 2016
I did provide a screen recording in comment #2 Ok, I will update the steps again to be exact to the letter: 1. Open DevTools console by pressing F12, place the cursor within the console. 2. Type "docament" (without the apostrophes) and press Enter. Make sure that an error message is shown. 3. Click within the URL area of the same tab and type some URL (for example www.github.com) 4. Open DevTools console again (if it is not already open), place the cursor within the console. 5. Start typing "do". Result - "docament" is a suggestion in the opened suggestions popup.
,
Mar 17 2016
Confirmed this behaviour can be faithfully reproduced. I've read complaints from a few developers that the new autocomplete/history suggestions behaviour is useful, but not enough control is provided around: * Limiting autocompletions to specific origins (autocompletions against foo.com and bar.com should be kept separate). When working on multiple projects or sites, there's questionable value in providing the complete history here. It's just not as relevant. * Inability to switch off the new suggestions behaviour if they find it disruptive. It's unclear atm if just limiting suggestions on a per origin basis would remove the need to just disable the feature. I'd personally like to see us address global suggestions cross-tab/origin as I use the console heavily and am similarly finding this new feature more annoying than useful after a few days use. Can we limit to origin or rethink the UX here?
,
Apr 19 2016
,
Apr 25 2016
Issue was resolved in the latest Chromium. Please close the it. Thank you.
,
Apr 25 2016
Closing this issue as per the comment #10 |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by rnimmagadda@chromium.org
, Mar 16 2016Labels: Needs-Feedback