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
Post Featured Image
inconsistent style between Editor and front end
#52238
Comments
@carolinan kindly please assign this issues |
Hi @albarin - thanks for reporting this. I'm interested to know - is this occurring for you with one of the default themes (like TwentyTwentyThree) or is it only with your current theme? I'd appreciate it if you could install and activate TwentyTwentyThree and see if the issue occurs then as well. |
Hey @jordesign, this is happening with TwentyTwentyThree (it's the theme I was using to take the screenshots above) and other themes as well, I've tried TwentyTwentyTwo and I got the same result. |
Help us move this issue forward. This issue is being marked stale since it has no activity after 15 days of requesting more information. Please add info requested so we can help move the issue forward. Note: The triage policy is to close stale issues that need more info and no response after 2 weeks. |
Thanks for the explanation @albarin - I can confirm this in testing as well following your instructions.
I do note that adding |
Description
The
Post Featured Image
has different behavior in the editor and in the front end.When inserted in a column, if the image is wider than the column it shows under the second column content in the editor, but over it in the front-end.
It should have the same behavior in both cases.
Step-by-step reproduction instructions
Post Featured Image
in the left column and give it a width larger than the column.Paragraph
with some text).Screenshots, screen recording, code snippet
Environment info
WordPress 6.2.2
Gutenberg 16.0.0
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: