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
Setting display: block; on elements will overwrite the hidden attribute's functionality. Currently cssremedy is putting display block on a variety of elements.
I guess the preferred way is to have img:not([hidden]) { display: block; } etc.
Or perhaps specify [hidden] { display: none } to save on filesize?
The text was updated successfully, but these errors were encountered:
Merged the initial fix, which addresses a problem caused by other remedies. But then I started digging into the potential for adding !important here, as a remedy in it's own right.
The html spec is clear that users can override the [hidden] attribute, and I think browsers are implementing it as a zero-specificity author-origin presentational hint similar to width/height. That's why it's so easy to override right now. But the spec also says that hidden should only be used when hiding completely, which implies users should not override it even though they can.
All that to say: I think !important might make sense on this as a remedy for the current browser handling.
Setting
display: block;
on elements will overwrite thehidden
attribute's functionality. Currently cssremedy is putting display block on a variety of elements.I guess the preferred way is to have
img:not([hidden]) { display: block; }
etc.Or perhaps specify
[hidden] { display: none }
to save on filesize?The text was updated successfully, but these errors were encountered: