Skip to content

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

Merged
merged 19 commits into from
Apr 1, 2025

Conversation

rafaelgallani
Copy link
Contributor

@rafaelgallani rafaelgallani commented Mar 28, 2025

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

Where Before After
TLD filter image image
Prompt tooltip image image
Focused search input image image

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

  • Has the general commit checklist been followed? (PCYsg-hS-p2) (not quite, but still)
  • Have you written new tests for your changes?
  • Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
  • Have you checked for TypeScript, React or other console errors?
  • Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
  • Have we added the "[Status] String Freeze" label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
    • For UI changes, have we tested the change in various languages (for example, ES, PT, FR, or DE)? The length of text and words vary significantly between languages.
  • For changes affecting Jetpack: Have we added the "[Status] Needs Privacy Updates" label if this pull request changes what data or activity we track or use (p4TIVU-aUh-p2)?

Copy link

github-actions bot commented Mar 28, 2025

@matticbot
Copy link
Contributor

matticbot commented Mar 28, 2025

Here is how your PR affects size of JS and CSS bundles shipped to the user's browser:

Sections (~106 bytes added 📈 [gzipped])

name                        parsed_size           gzip_size
async-step-unified-domains       +343 B  (+0.0%)     +106 B  (+0.0%)

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])

name                             parsed_size           gzip_size
async-load-signup-steps-domains       +343 B  (+0.1%)     +106 B  (+0.1%)

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.
Gzip Size: Compressed size of the JS and CSS files. This much data needs to be downloaded over network.

Generated by performance advisor bot at iscalypsofastyet.com.

Comment on lines +608 to +609
/* stylelint-disable-next-line declaration-property-unit-allowed-list */
line-height: 1.2em;
Copy link
Contributor Author

Choose a reason for hiding this comment

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

/* 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));
Copy link
Contributor Author

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;
Copy link
Contributor Author

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.

@rafaelgallani rafaelgallani marked this pull request as ready for review March 28, 2025 03:46
Copy link
Contributor

@gius80 gius80 left a comment

Choose a reason for hiding this comment

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

LGTM! Thanks for the fix!
I only noticed a minor discrepancy, see images below.

search-domain-only
search-onboarding

@rafaelgallani
Copy link
Contributor Author

LGTM! Thanks for the fix! I only noticed a minor discrepancy, see images below.

search-domain-only search-onboarding

@gius80 Wow. That's a very good catch + pair of eyes 😬

I've also added a few other minor adjustments to the description (here).

I'll deploy this one tomorrow. Thanks for the review!

@rafaelgallani rafaelgallani merged commit 65fc7ea into trunk Apr 1, 2025
15 of 16 checks passed
@rafaelgallani rafaelgallani deleted the fix/sync-styles-for-domain-flows branch April 1, 2025 19:47
JessBoctor pushed a commit to JessBoctor/wp-calypso that referenced this pull request Apr 15, 2025
…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... 🥶)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants