-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Details block: opening and closing impacts background of header #51248
Comments
@annezazu I don't think this is an issue with the details block, but more with the aubergine variation and how the background is implemented, so it's probably a core trac ticket. It would happen for just about any block that can change the page height (like third party accordion blocks) and might become more apparent with the interactivity experiments. |
This is a theme design issue. The background gradient will be problematic on any pages with a shortened height. Here's the background gradient that's used: linear-gradient(180deg, var(--wp--preset--color--base) 0 min(24rem, 10%), var(--wp--preset--color--secondary) 0% 30%, var(--wp--preset--color--base) 100%) In particular, the |
Thanks for clarifying and giving more insight, @justintadlock. Where do you think is the best place to leave this feedback? Trac or here? It also just might be "by design", meaning it could be closed out. |
Yeah, I believe this is probably best on core Trac. @anarieldesign might have some insight into whether it's "by design" or could be altered since she was the original author of the variation. |
https://core.trac.wordpress.org/ticket/58475 closing out- thank you. |
This was found as part of the FSE Outreach Program's rapid revamp call for testing:
To replicate, switch to the Aubergine style variation for TT3 and add a details block to a page with some text inside. View on the front end of your site and notice when opening the details block, the heading/background appears to move.
This was found using the Aubergine style variation and Gutenberg 15.9.1 with WordPress 6.2.2. I wonder if this is potentially related to #46782
The text was updated successfully, but these errors were encountered: