You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would argue that Psuedo-classes such as :hover, :active, and :focus (move these out of psuedo-classes and consider them psuedo-styles?) should come after Psuedo-elements (if not at the very end of our ordering). Example: often a psuedo-element will need to respond to the :hover of its parent. Isn't it more organized to wrap all of that up in a single declaration?
The text was updated successfully, but these errors were encountered:
I would argue that Psuedo-classes such as :hover, :active, and :focus (move these out of psuedo-classes and consider them psuedo-styles?) should come after Psuedo-elements (if not at the very end of our ordering). Example: often a psuedo-element will need to respond to the :hover of its parent. Isn't it more organized to wrap all of that up in a single declaration?
The text was updated successfully, but these errors were encountered: