Skip to content
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

Revert 66431 (Site editor: remove "default" admin CSS) #66540

Merged
merged 1 commit into from
Oct 28, 2024

Conversation

andrewserong
Copy link
Contributor

What?

Reverts #66431

Why?

While a well-intentioned change to remove unnecessary CSS, it turns out #66431 caused a regression in the site editor in mobile viewport sizes where the admin markup is exposed unexpectedly.

A longer-term solution might be to see if we can skip the admin markup entirely for site-editor.php, however for now, in order to ensure things are working well on trunk, this PR proposes reverting.

How?

Revert the change in #66431

Testing Instructions

  1. On trunk open up the site editor in a mobile viewport size. Notice that above the content of the site editor the WP admin UI markup is unexpectedly displayed.
  2. With this PR applied, the site editor should work as it did before on mobile and other viewport sizes

Screenshots or screencast

Before After
image image

@andrewserong andrewserong added [Type] Regression Related to a regression in the latest release [Feature] Site Editor Related to the overarching Site Editor (formerly "full site editing") labels Oct 28, 2024
@andrewserong andrewserong requested review from ellatrix and a team October 28, 2024 22:45
@andrewserong andrewserong requested review from draganescu and removed request for a team and spacedmonkey October 28, 2024 22:45
Copy link

github-actions bot commented Oct 28, 2024

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: andrewserong <[email protected]>
Co-authored-by: ramonjd <[email protected]>
Co-authored-by: tellthemachines <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@andrewserong andrewserong self-assigned this Oct 28, 2024
@andrewserong andrewserong added the No Core Sync Required Indicates that any changes do not need to be synced to WordPress Core label Oct 28, 2024
Copy link
Member

@ramonjd ramonjd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yip. Good spotting

😦 😄
Screenshot 2024-10-29 at 9 52 27 am Screenshot 2024-10-29 at 9 52 57 am

Copy link
Contributor

@tellthemachines tellthemachines left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for fixing this! Pages in the site editor are now working as expected ✅

@andrewserong andrewserong enabled auto-merge (squash) October 28, 2024 22:57
@andrewserong
Copy link
Contributor Author

Thanks for the quick reviews! 🙇

@andrewserong andrewserong merged commit c4b8e51 into trunk Oct 28, 2024
78 of 81 checks passed
@andrewserong andrewserong deleted the revert/66431 branch October 28, 2024 23:21
@github-actions github-actions bot added this to the Gutenberg 19.6 milestone Oct 28, 2024
karthick-murugan pushed a commit to karthick-murugan/gutenberg that referenced this pull request Nov 13, 2024
Co-authored-by: andrewserong <[email protected]>
Co-authored-by: ramonjd <[email protected]>
Co-authored-by: tellthemachines <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] Site Editor Related to the overarching Site Editor (formerly "full site editing") No Core Sync Required Indicates that any changes do not need to be synced to WordPress Core [Type] Regression Related to a regression in the latest release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants