UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.94 Safari/537.36

Steps to reproduce the problem:
1. Click on an element which usually have pseudoclasses, like an anchor ('<a>') and inspect it
2. In "Styles" tab in DevTools, check for the line with the keyframes button and the push pin to test hover and visited states 
3. The push pin is not there; instead, there is a ":hov" button, which can be taken mistakenly as if you where forcing the hover state, not accessing another menu to force several element states

What is the expected behavior?
There should be a push pin button or another button indicating that you will sunsequently change whatever state you want, which should not correspond with a SPECIFIC state (':hov')

What went wrong?
Two or three versions ago you changed the push pin button for a ":hov" button. Everytime I want to force a state, whatever it is :hover, :active or :visited, now I get confused because when I'm searching for the push pin button to change whatever state I find a :hov button which mistakenly makes me think that I'm forcing the :hover state. The previous button was much better for this purpose.

Did this work before? Yes Until two or three versoins ago

Chrome version: 50.0.2661.94  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 21.0 r0

Those changes in UI should be made more carefully. First, it wasn't needed; why did you change it? Secondly, the new button is prone to misinterpretation.