-
Notifications
You must be signed in to change notification settings - Fork 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
Domains: Fix DNS pages header design issues #58692
Conversation
Link to Calypso live: https://calypso.live?image=registry.a8c.com/calypso/app:build-21622 |
Here is how your PR affects size of JS and CSS bundles shipped to the user's browser: Sections (~59 bytes added 📈 [gzipped])
Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to. Legend What is parsed and gzip size?Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory. Generated by performance advisor bot at iscalypsofastyet.com. |
.popover__menu-item[disabled] { | ||
svg.gridicon { | ||
fill: var( --color-neutral-20 ); | ||
} | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Having to define this feels like a regression 🤔 the icon was invisible because it was being colored color: var( --color-neutral-0 )
. Or maybe we're defining something wrong and the icon ends up being colored wrongly?
Thanks @leonardost! This is kind of my mistake, but I think the "3 dots" button should still be there in mobile, Like this:
This point doesn't seem to be addressed and this should be true for all borderless buttons (in any page, including the "Domains" page). This helps create consistent spacing as well as providing a large enough hit area on mobile. While I think we should go for a similar approach to how it is in P2 for example. Their button size is 36x36. In our case it would be 40x40. |
Thanks for the review @poligilad-auto!
I had thought about asking you about that but I didn't, so I'm at fault too 😆 The width of the ellipsis button is now 40px: And it's in the mobile view too: I reduced the left margin of the button to 8px in the mobile view as it seemed that way in the design - is this correct? |
Perfect.
Yes, exactly correct 👌 The only thing now is doing the same for the "Domains" page :) Now we also have miss-alignment that needs to be fixed in the table, that's what this comment was about: |
7fa198b
to
f2ed3c0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice job! LGTM. Tested that all the described changes were reflected.
There's only one single issue I found with the TXT record alignment - although I'm not sure if that's related to this PR:
I think it's easier to fix it in this PR, but if that's not the case, then feel free to ignore this comment 😅
I also left a single code suggestion, but that's only a nitpick - it should be good to go with or without it.
@@ -171,6 +171,10 @@ | |||
.breadcrumbs__buttons-mobile { | |||
display: flex; | |||
|
|||
> * + * { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice one!
There's a relatively new flex/grid display CSS property called gap
that does the same thing - and you can also define row-gap
and column-gap
separately on it.
I saw a few references to it in our codebase, although I'm not so sure how that would be interpreted by our webpack loaders. It might be worth giving a try 😸
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it was Del who wrote that selector, it's neat 😄
I was going to say that selector isn't inside a grid context, but I just learned that gap
can be used in flexbox too, that's nice!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah...I think you should be able to use gap
here. Probably more readable than the "owl-face" selector I used. :-D
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🦉 Owl face, that's a nice one * + *
😄
Thanks for the review @rafaelgalani and nice catch! I'll take a look at that case 👀 |
This PR modifies the release build for wpcom-block-editor To test your changes on WordPress.com, run To deploy your changes after merging, see the documentation: PCYsg-l4k-p2 |
This PR modifies the release build for editing-toolkit To test your changes on WordPress.com, run To deploy your changes after merging, see the documentation: PCYsg-mMA-p2 |
This PR modifies the release build for notifications To test your changes on WordPress.com, run To deploy your changes after merging, see the documentation: PCYsg-elI-p2 |
Cool! I've aligned the 3 dots icons with the header's 3 dots, I'll do the same for the "Domains" page in a follow-up PR 👍 |
This Pull Request is now available for translation here: https://translate.wordpress.com/deliverables/7027759 Thank you @leonardost for including a screenshot in the description! This is really helpful for our translators. |
* Fix DNS page header design issues * Fix width of ellipsis breadcrumb button * Reduce left-margin of breadcrumb buttons in mobile view * Align DNS item rows' 3 dots with DNS header's 3 dots * Fix positioning of ellipsis menu of DNS items in mobile view * Make DNS items ellipsis popover appear below the icon instead of above
Translation for this Pull Request has now been finished. |
Changes proposed in this Pull Request
This PR fixes design issues in the DNS pages header pointed out by the design review in pcYYhz-q9-p2#comment-358.
The following screenshots highlight what was updated:
redo
icon is now visible in menuYou can compare them with the previous designs:
Note: Breadcrumbs issues are being addressed in #58601 and #58519.
Testing instructions
?flags=domains/dns-records-redesign
to your URL to enable the appropriate feature flag