Input fields adding focus-visible on click about focus-visible HOT 2 CLOSED

Yes it's expected behavior, meant to match the way that the browser works today. For instance, if you mouse click a <button> in Chrome it will not draw a focus indicator, but if you mouse click a <input type=text> it will. I believe the basis of this assumption is that for any area where it's assumed the user is going to provide keyboard input, the browser will draw a focus indicator.

In the spec this is articulated in the second half of the opening statement:

The :focus-visible pseudo-class applies while an element matches the :focus pseudo-class and the UA determines via heuristics that the focus should be made evident on the element.

For example, UAs typically display focus indicators on text fields any time they’re focused, to draw attention to the fact that keyboard input will affect their contents.

On the other hand, UAs typically only display focus indicators on buttons when they were focused by a keyboard interaction (such as tabbing through the document)—because it’s not always immediately obvious where the focus has gone after such an interaction, but is sufficiently self-evident when the button was focused by more obviously-targetted interactions, like clicking on the button with a mouse pointer.

from focus-visible.

Ok cool, thanks very much for the explanation. That went past me for some reason, I assumed that they would all act the same.

from focus-visible.