New in @ChromeDevTools (in Chrome Canary): You can now force more states – such as :active, :focus, … – onto elements.
For example, when inspecting an <input> element you can now also force states such as :enabled, :valid, etc.
New in @ChromeDevTools (in Chrome Canary): You can now force more states – such as :active, :focus, … – onto elements. For example, when inspecting an <input> element you can now also force states such as :enabled, :valid, etc. 3 comments
@bramus can we also have an ability for the emulated states like hover or focus to propagate to the parents? Very often I want to apply :hover on dive element, and it trigger all the :hover on all the ancestral events. Same for :focus-within triggering for focus/focus-visible. |
These extra states depend on the context. When inspecting a <label> element, you get different options than when inspecting <input>.