-
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
.wp-element-caption
class incorrectly applied to Quote block <cite>
element in Editor
#62208
Comments
For the The front end doesn't have the Based on that, we have the following approaches:
The second option will be appropriate if we don't consider the citation as a caption and then reuse the new component for other |
This option would also create back-compatibility styling issues for themes. But I'd consider it a non-starter because citations and captions are two different things that serve different purposes
Is a new component needed or just the ability to overrule the class of the existing component? I'd be OK with either direction. |
@justintadlock , thank you for the feedback. I've prepared a PR (my first one) following the overrule approach. In the future, if we end up adding too many options/rules to the utility components, we can think of organizing and standardizing them for better consitency. |
Fixed by #62485 |
Description
Since the addition of the toggle button to show/hide the Quote citation in the editor in Gutenberg 18.1, it has applied the
.wp-element-caption
class to the<cite>
element: #59073It creates inconsistent styling between the editor and front end because of the addition of the class, which means that it picks up caption styling (it should only have cite styling in both places)
Step-by-step reproduction instructions
.wp-element-caption
class on the editor side.Screenshots, screen recording, code snippet
Editor:
Front end:
Environment info
Please confirm that you have searched existing issues in the repo.
Yes
Please confirm that you have tested with all plugins deactivated except Gutenberg.
Yes
The text was updated successfully, but these errors were encountered: