-
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
Save entities panel: update styles #58706
Conversation
Size Change: +58 B (0%) Total Size: 1.69 MB
ℹ️ View Unchanged
|
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 Core SVNCore Committers: Use this line as a base for the props when committing in SVN:
GitHub Merge commitsIf you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
- The individual global style changes are shown below the checkbox, typography $gray-700 color and $helptext-font-size. - The individual items next to the checkbox are no longer bold, they are regular text. - The wording has been changed for pages being edited, to avoid the widow. Instead of "The following content has been modified." it's "The following has been modified.
ccbcc9b
to
7c8e059
Compare
Flaky tests detected in 7c8e059. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/7807136576
|
Thanks again for the quick feedback!! 🍺
There was a version of this feature on the original PR: #56577 (comment) It involves rejigging the output of the compare function to enable grouping by blocks, settings, elements etc. The results can be still limited to I reckon this would be be better addressed in another PR as I'd need to update tests etc Happy to spin one up to try it out. I'll try with text for block names first to test my assumptions.
This PR takes care of that already, if I've not missed something 🤔 |
Right, sorry for doubling back on that conversation. I still think it's worth going back to that, though I'd not do the "Blocks: " in bold, I'd just have " blocks." at the end. Speaking of, what might go in the "and 1 more change"? — if we can't tell you what it is, so you can't decide whether to save it or not, we shouldn't show it at all, IMO. Definitely okay to look at separately, and not urgent. Got the entire beta period for this, and thank you for helping. And yes indeed, this looks right, I don't know why, perhaps a vestige of my env, but previously I saw something else in my local branch: |
Excellent! I'll add it to the list.
Good question. It's definitely possible to make the There could be 1 change there could be 100, so there has to be some level of truncation. At the moment, there is an order of priority, however, whereby body styles and blocks will be at the start of the list, so I suppose there'll be some "meat in the sandwich" regardless. 😄 I'll look at this when I start the list tweaking above.
Thank you too! |
What?
This PR:
$gray-700
color and$helptext-font-size
."The following changes have been made to your site, templates, and content."
to"There are <strong>%d site changes</strong> waiting to be saved."
Why?
Design updates
See:
Testing Instructions
In the site editor, create some changes to:
Save the site and checkout the save panel.
Do the same in the post editor (minus global styles).
Thank you!
Screenshots or screencast
Before
After