Conversation
Test using WordPress PlaygroundThe changes in this pull request can previewed and tested using a WordPress Playground instance. WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser. Some things to be aware of
For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation. |
Co-authored-by: Erik <11491369+kebbet@users.noreply.github.com>
Co-authored-by: Erik <11491369+kebbet@users.noreply.github.com>
Co-authored-by: Erik <11491369+kebbet@users.noreply.github.com>
Co-authored-by: Erik <11491369+kebbet@users.noreply.github.com>
|
Reverting and moving backward won't help get this in the best shape for the final release. Cropping is now fixed. Going to spend some time today getting things finalized for commit |
…4370-site-icon-post-review
kebbet
left a comment
There was a problem hiding this comment.
Some notes on the current state of the PR.
| .site-icon-preview-inline.settings .home-icon { | ||
| width: 58px; | ||
| height: 58px; | ||
| border-radius: 12.95px; |
There was a problem hiding this comment.
Can all pixel values be changed to be integers?
src/wp-admin/css/site-icon.css
Outdated
| width: 200%; | ||
| height: 200%; | ||
| transform: translateX(-25%) translateY(-25%); | ||
| /* background: linear-gradient(0deg, rgba(0, 0, 0, 0.2) 0%, rgba(0, 0, 0, 0.3) 100%), var( --site-icon-url ) 50%/cover no-repeat; */ |
src/wp-admin/css/site-icon.css
Outdated
| flex-shrink: 0; | ||
| z-index: 1; | ||
| border-radius: 9.824px; | ||
| box-shadow: 0 1.517px 3.034px 0 rgba(0, 0, 0, 0.1), 0 4.552px 4.552px 0 rgba(0, 0, 0, 0.09), 0 10.621px 6.828px 0 rgba(0, 0, 0, 0.05), 0 19.724px 7.586px 0 rgba(0, 0, 0, 0.01), 0 30.345px 8.345px 0 rgba(0, 0, 0, 0); |
There was a problem hiding this comment.
Can box-shadows be simplifed to use one shadow statement, this is really messy.
src/wp-admin/css/site-icon.css
Outdated
| border-top: 1px solid rgba(255, 255, 255, 0.2); | ||
| border-left: 1px solid rgba(255, 255, 255, 0.2); | ||
| background: linear-gradient(180deg, #dcdcde 0%, #bdbdbd 100%); | ||
| box-shadow: 0 10px 22px 0 rgba(0, 0, 0, 0.2), 0 40px 40px 0 rgba(0, 0, 0, 0.17), 0 89px 53px 0 rgba(0, 0, 0, 0.1), 0 158px 63px 0 rgba(0, 0, 0, 0.03), 0 247px 69px 0 rgba(0, 0, 0, 0); |
src/wp-admin/css/site-icon.css
Outdated
| flex: 1 0 0; | ||
| border-radius: 4px; | ||
| background: #f6f7f7; | ||
| box-shadow: 0 1px 3px 0 rgba(0, 0, 0, 0.04), 0 5px 5px 0 rgba(0, 0, 0, 0.03), 0 12px 7px 0 rgba(0, 0, 0, 0.02), 0 22px 9px 0 rgba(0, 0, 0, 0.01), 0 34px 9px 0 rgba(0, 0, 0, 0); |
| border-radius: 12.95px; | ||
| } | ||
|
|
||
| .site-icon-preview-inline.settings:after { |
There was a problem hiding this comment.
src/wp-admin/css/site-icon.css
Outdated
| height: 44px; | ||
| flex-shrink: 0; | ||
| z-index: 1; | ||
| border-radius: 9.824px; |
src/wp-admin/options-general.php
Outdated
| <?php | ||
| /* translators: %s: Site Icon size in pixels. */ | ||
| printf( __( 'Site Icons should be square and at least %s pixels.' ), '<strong>512 × 512</strong>' ); | ||
| printf( __( 'Site Icons are what you see in browser tabs, bookmark bars, and within the WordPress mobile apps. They should be square and at least %s pixels.' ), '<strong>512 × 512</strong>' ); |
This needs to be addressed. |
Thanks for clarifying and fixing cropping. |
|
First, have a look at the admin bar when the Site Title option is changed in options-general.php. Is it possible to use the same mechanism in the preview of the site icon? Basically update the tab name, while typing in the Site Title field above? |
…review in the cropper
…4370-site-icon-post-review
I kindly disagree. The design changes are outside of the scope of this PR. I'm not sure insisting broadening the scope of this PR is ideal. More importantly, given we're in Beta 2, I'm not sure it's any wise. At this point of the release cycle any change should be as small and self-contained as possible and only focused to fix bugs. While I agree that updating the design with a more modern browser interface is a nice to have, that's not required for this functionality to work. Also, if updating the design of the preview is desired, I'd like to remind everyone that it would need to be be updated also in other two places;
I'm not sure providing a different design only in the General Settings page would be ideal and help users as it would be clearly inconsistent and confusing. Extending the design changes to the media modal and customizer in this PR would be really out of scope and make this PR way larger than it was meant to be. Lastly, @kebbet reported valid concerns about the latest changes that, in my opinion, would need more time to be addressed. As I see it, Beta 2 is not the best timing for such changes. I'd like to make clear that I'm nog against a design update, but that should go in a separate PR so that such changes can be better evaluated to establish if they fit with the release cycle process. |
|
Hi all 👋 Just chiming in here since I see this ticket / PR has been open for a while now with a lot of activity, so I am just wondering if there's anything I can help with to ensure this is in a good shape to land in time for the next beta. Could someone perhaps summarize the goals and contents of this pull request for me, maybe with a before/after comparison? Even just updating the PR title & description would be helpful. Or maybe put another way: what are the issues with the current version in Thanks in advance 🙏 In the meantime, since I saw a comment about coding standards, missing whitespace, etc.: Please note that we have tools like Prettier, just use e.g. Also, if the changes in the PR are too big to review in one go, perhaps they could be split into multiple PRs? |
npx prettier@npm:wp-prettier@latest --write src/js/_enqueues/admin/site-icon.js npx prettier@npm:wp-prettier@latest --write src/wp-admin/css/site-icon.css
|
I've gone back and forth on this for the last few hours. On one hand, the new design more closely resembles the block editor and the current browser UI is outdated. On the other, the new design does not feel ready as it came in very late in the release cycle and as James notes, it hasn't considered edge cases. The improvements that are reflected in the screenshots seem to resolve the known issues, but I'm unsure. I also worry about integrating in this in three different places and then doing further interaction. As I've mentioned multiple times, I think what's going to provide the best experience for the users of WordPress is an experience that is consistent across the different UIs. Iterating on the UI in the three different places is cumbersome at best and bug-inducing at worst. Unless there is an objection, I think the path forward is:
RE: Prettier. That command doesn't format correctly. I used |
|
Thanks for the update & context @aaronjorbin! That sounds like a sensible path forward to me. I see you just opened #6165 in the meantime. Would you like the group to review that one now? Just noting it's still in draft. |
|
I opened that PR so that it's ready if this path forward is desired without further clouding this one. The only differences are 1: I fixed the jshint issues that prettier caused 🤦 |













https://core.trac.wordpress.org/ticket/54370
Work In Progess. Feel free to help out.