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
In the Hacker News discussion someone mentions support for browsers with Javascript disabled seeing the teaser text and I think it's a legitimate concern. I posted a proof of concept in the thread, and will post it here for discussion. This is a purely CSS only solution for users with Javascript disabled.
What do you think of this proof of concept?
this is teaser text
.teasertext { background: #000; color: #000; }
.teasertext:focus { background: inherit; color: inherit; outline: none; }
I think perhaps it could reveal the text a little bit when you hover over it by perhaps bumping up the color of the text to 444 and background to 333 or something. Or RGBa values could be used instead or perhaps for text the text-shadow (although not widely supported) could also be considered.
The text was updated successfully, but these errors were encountered:
Additionally, these fallback options should be overridden. I can't think of a way to do this automatically tbh since CSS definitions and the actual css selector for the jQuery command don't necessarily have to be the same.
In the Hacker News discussion someone mentions support for browsers with Javascript disabled seeing the teaser text and I think it's a legitimate concern. I posted a proof of concept in the thread, and will post it here for discussion. This is a purely CSS only solution for users with Javascript disabled.
What do you think of this proof of concept?
this is teaser text
.teasertext { background: #000; color: #000; }
.teasertext:focus { background: inherit; color: inherit; outline: none; }
I think perhaps it could reveal the text a little bit when you hover over it by perhaps bumping up the color of the text to 444 and background to 333 or something. Or RGBa values could be used instead or perhaps for text the text-shadow (although not widely supported) could also be considered.
The text was updated successfully, but these errors were encountered: