Better control/distinction between console autocomplete native and custom items
Reported by
maurice....@gmail.com,
Mar 11 2016
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.87 Safari/537.36 Steps to reproduce the problem: 1. open devtools and pull up the console drawer (or go to tab) 2. type Array.prototyp and press enter 3. type Array.prototypes and press enter 4. type Array.pro and observer the autocomplete items What is the expected behavior? There should be a better distinction between autocomplete suggestions that are properties of the object and previously typed console commands. Additionally, there should be a way to remove custom input. What went wrong? Though native suggestions appear first in order, it's not readily apparent. Also if one were to have typos when typing or prematurely hit enter by accident, that will still register as custom input, but have little to no value. mockup attached Did this work before? No Chrome version: 49.0.2623.87 Channel: stable OS Version: OS X 10.11.2 Flash Version: Shockwave Flash 21.0 r0
,
Mar 23 2016
This is also discussed in this google group thread: https://groups.google.com/forum/#!topic/google-chrome-developer-tools/zaSxnoa-1Jw The addition of "custom" autocomplete is a regression as it is currently implemented. Previously autocomplete could be used to determine what properties were available on an object (for example on different angularjs scopes).
,
May 26 2016
This got fixed.
,
Sep 29 2016
,
Sep 29 2016
|
||||
►
Sign in to add a comment |
||||
Comment 1 by alph@chromium.org
, Mar 12 2016Labels: -OS-Mac OS-All
Owner: lushnikov@chromium.org
Status: Assigned (was: Unconfirmed)