Issue metadata
Sign in to add a comment
|
(inspector tools) New styles keyboard tabindex (tab to next line) no longer works
Reported by
klinefo...@gmail.com,
Dec 19 2017
|
||||||||||||||||||||||||
Issue description
Chrome Version : 63.0.3239.84
OS Version: OS X 10.12.6
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari:
Firefox:
IE/Edge:
What steps will reproduce the problem?
1. highlight text on screen
2. right click and inspect element
3. In the upper right - click the "+" to add a new style
--
now onto the bug/glitch/headache
--
4. press tab - notice where your cursor went.
What is the expected result?
I expected that - as in the past - the curser would move to the next line and allow me to start typing CSS statements.
What happens instead of that?
Curser disappears and now I have to adjust my hand to the mouse and re-click on the intended spot. As someone who uses the keyboard shortcuts constantly, this is a major issue for me. It makes my days longer because I am always having to move my hand.
Please provide any additional information below. Attach a screenshot if
possible.
UserAgentString: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.84 Safari/537.36
,
Dec 20 2017
,
Dec 20 2017
Duplicate of issue 757364 Fixed in 64.0.3263.0, currently beta, stable on Jan 23 so I'd say it would make sense to back-merge the fix into Chrome 63.
,
Dec 21 2017
Able to reproduce the issue on reported version 63.0.3239.84 and the same is not seen on latest canary 65.0.3299.0 and Beta 64.0.3282.39 using Windows 10, Ubuntu 14.04 and Mac 10.12.6, hence providing reverse bisect info Bisect Info: ================ Last Bad build: 64.0.3262.0 First Good build: 64.0.3263.0 You are probably looking for a change made after 514753 (known good), but no later than 514754 (first known bad). https://chromium.googlesource.com/chromium/src/+log/ea365a520d4ef1d4943179e060e0538f82738819..6ab0eb4e7f4f2f1c00467cacaf4f30cef760f9e9 Reviewed on: https://chromium-review.googlesource.com/677128 Suspecting same from changelog. @Joel Einbinder: Please confirm the issue and help in re-assigning if it is not related to your change, help in merging this issue to M-63 if applicable Thanks!
,
Dec 21 2017
,
Dec 26 2017
Issue 797490 has been merged into this issue.
,
Jan 2 2018
since the issue doesn't reproduce on M64 and above can we live with this for M63, Since M64 would hit stable on Jan-23rd(if all go's well) since at this point we don't have any plans can we live with this for next 3 weeks. Please correct me if I am not accessing the impact of the bug.
,
Jan 2 2018
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by krajshree@chromium.org
, Dec 20 2017