Chrome 62 Developer Tools - tabbing (pressing tab key) from css property to value deselects instead of selecting.

[Simon Barnett]

This may not seem like a biggie, but since it's a micro-step involved in my workflow it's a repeated annoyance which adds up to what could be termed an issue.

My Dev Tools workflow consists of selecting an HTML element, then adding a CSS rule for it to the Inspector Stylesheet.

When done, I copy everything I've created from Sources > Inspector Stylesheet, and paste it into my stylesheet.

The Issue

I used to be able to

1. tap the plus sign,
   
2. then hit the tab key to create an empty property,
   
3. start typing.
   

Now - as of Chrome 61 or 62 - it either removes the rule completely, which is less common,

Or if not, then it always deselects the property, forcing me to have to

1. tap the plus sign
2. hit the tab key, after which it deselects *
3. switch to the trackpad
   
4. manually line up the pointer with the property field
   
5. tap there
   
6. switch to the keyboard
7. then start typing.
   

* Note: leaving out the step with the tab key doesn't help.

Manually tapping in the property field also deselects the property.

Sure, I'm breaking it into micro-steps by making "switch to the trackpad" and "switch to the keyboard" into whole steps,

but when compared with my previous workflow, they are steps.

The numbering on these screenshots refer only the pics, and don't correspond with my steps above.

Pow! .. nothing. It deselects..

[Kayce Basques]

In Canary on Mac I think it's working like it used to.

I click New Style Rule and it creates a new rule:

Then I press the Tab key and the cursor changes to an empty property name:

If you're on Mac or Windows, can you try Canary and let me know if you're still seeing the issue?

[Simon Barnett]

Ah, so it's been picked up.. hooray

Thanks Kayce

[PhistucK]

Yes, it was recently fixed -

https://github.com/ChromeDevTools/devtools-frontend/commit/3993cb1b43b1036e2a0e6480dd826b15c3aa30c5

☆PhistucK

--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-developer-tools+unsub...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/1d78e5c1-3b1c-4cbf-9f61-697a192faa91%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[shane.m...@kmstools.com]

I am still getting this behavior on chrome 63 on windows. I just did the update to chrome and still nothing. Is there a way to fix this ? 

[PhistucK]

It was fixed during the main Chrome 64 development time frame. It was not a critical bug, so it was not merged to Chrome 63.

☆PhistucK

On Sat, Jan 6, 2018 at 12:20 AM, <shane.m...@kmstools.com> wrote:

I am still getting this behavior on chrome 63 on windows. I just did the update to chrome and still nothing. Is there a way to fix this ? 

--

You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-developer-tools+unsub...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/a8b0b820-8881-4e1c-9d36-441651f3e4da%40googlegroups.com.

[Kayce Basques]

If the fix is in Chrome 64, and you're currently on 63, that means that you'll get the fix in 6 weeks maximum (probably less, I think 63 has been out for a bit).

If you're on Windows or Mac, you can download Chrome Canary to get the bleeding-edge Chrome code. It's unstable, but has the latest features.