Changing CSS rule values in the element inspector focuses on the console input
Reported by
robbygr...@quicknet.nl,
Mar 21 2016
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.87 Safari/537.36 Steps to reproduce the problem: 1. Inspect a random element on the page 2. Click on the value of any CSS rule 2. Try to edit the value using arrow keys or typing a new value 3. What is the expected behavior? To edit the value whilst keeping focus on the editor, and not lose focus after typing 1 character or pressing up/down key once. What went wrong? Instead, it opens the Console view and focuses on the input, even when the console is closed. It loses focus on the value editor and continues typing in the console. Did this work before? Yes Chrome v48 Chrome version: 49.0.2623.87 Channel: stable OS Version: 6.3 Flash Version: Shockwave Flash 21.0 r0 For me personally, I am unable to properly use this feature of chrome. I was really used to it because it's really easy to test style changes this way.
,
Mar 25 2016
I am also having this exact same issue.
,
Mar 30 2016
It seems to happen when the following error message occurs: Failed to parse SourceMap: http://localhost:55556/assets/css/________.css.map This makes the debugger focus on the console instead, and thus unable to properly continue editing the css values.
,
Mar 30 2017
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||
►
Sign in to add a comment |
||
Comment 1 by robbygr...@quicknet.nl
, Mar 21 2016