-
Notifications
You must be signed in to change notification settings - Fork 2k
Domains: Fix discrepancy between onboarding and domain-only search #102021
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
Conversation
Jetpack Cloud live (direct link)
Automattic for Agencies live (direct link)
|
Here is how your PR affects size of JS and CSS bundles shipped to the user's browser: Sections (~106 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. Async-loaded Components (~106 bytes added 📈 [gzipped])
React components that are loaded lazily, when a certain part of UI is displayed for the first time. 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. |
/* stylelint-disable-next-line declaration-property-unit-allowed-list */ | ||
line-height: 1.2em; |
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.
wp-calypso/client/components/formatted-header/style.scss
Lines 110 to 111 in 7800534
/* stylelint-disable-next-line declaration-property-unit-allowed-list */ | |
line-height: 1.2em; |
Since we're replicating this referenced style in here, we need to disable the rule as well too.
flex-direction: column; | ||
|
||
@media (min-width: 960px) { | ||
margin-top: calc(48px + 48px - var(--step-container-v2-top-bar-height)); |
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.
This is calculated based on the domain-only component - its margins/paddings are used to determine which should be the top here, along with the variable from the height of the different bar used in this flow.
} | ||
|
||
.onboarding:not(.is-onboarding-2023-pricing-grid) .step-container-v2__heading { | ||
margin: calc(48px + 24px - var(--step-container-v2-top-bar-height)) 20px 24px 20px; |
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.
Same as here - but a different viewport/media query, thus a different calculated value.
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.
…utomattic#102021) * Fix smaller viewport * Add more alignment fixes * Many more fixes * More fixes * Manage large viewport from parent component * Restrict search bar fix to onboarding * Fix wrong gap prop * Fix smaller viewports * Fix different price order * Fix wrong margin for desktop breakpoint * Fix small bug to load initial viewport * Organize styles + general cleanup * AI take on cleanup/simplifying the style * Fix bottom style for explanation image in smaller viewports * Add balance to text-wrap to avoid orphan words in last line * Move anti-aliasing to a more suitable location * Sync example prompt styles * Fix search element weird border radius * Remove outdated style... (2019... 🥶)
Related to https://linear.app/a8c/issue/NOMADO-28/fix-discrepancy-between-onboarding-and-domain-only-search.
Proposed Changes
Fix the visual discrepancies between the domain-only flow and the onboarding domain flows.
Also, there are some minor tweaks to the domain-only flow style (mainly anti-aliasing for the font family in the entire flow).
Preview
Before
Screen.Recording.2025-03-28.at.00.44.10.mov
After
Screen.Recording.2025-03-28.at.00.42.26.mov
Minor tweaks
Why are these changes being made?
So we can continue our work in the domain of UX with a synchronized state between both flows.
Testing Instructions
The easiest way I could find to test this is to keep both onboarding and domain-only flow tabs open and switch between them while changing the browser's window width, ensuring both look identical.
Pre-merge Checklist