-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cover Block: Add Hover Reveal style #20402
Comments
Nice ticket! This seems like a fine enhancement to add to the Cover block in my opinion. I'm assuming that focus also reveals? |
Do you mean when focusing with a keyboard? It does not in Dalston, although it definitely should. |
I think it's possible to do this animation with the block cover and a bit of CSS, no? |
Yep, I was thinking that if you tab into the block, the content should be revealed. Or even if you click on the hoverable area, that sets a lingering focus there, this should keep the content visible even as you mouse out and only disappear when you click somewhere else. To phrase it even simpler, instead of
Absolutely. I read this ticket as posing the question: does this have so much value that it should be a toggle in the block, as opposed to require custom CSS? |
I love this idea as feels like a great addition to the cover image block. Let's get this a 'needs dev' label and move into that. |
Hey, do we have any update on that? |
Has this been implemented yet? |
Is your feature request related to a problem? Please describe.
Hovering over an image to reveal text/link is a popular web design pattern. It would be great if the Cover block enabled that by adding dedicated block style.
The screenshot comes from Dalston theme ( source ) where "Hover reveal" is added as a custom style to the Cover block.
Here's how it looks like in the editor:
The behaviour is the same in the editor and on the frontend -- with "Hover reveal" style applied, the text shows up when hovering over an image. Clicking on the text makes it editable. Not sure if that particular behaviour in the editor would cause accessibility issues or not, but I'm sure we can iron out that part, if we agree that having this style added would be useful.
The text was updated successfully, but these errors were encountered: