-
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 step: Improve domain title spacing on smaller screens #94852
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 (~22 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 (~22 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. |
This PR modifies the release build for the following Calypso Apps: For info about this notification, see here: PCYsg-OT6-p2
To test WordPress.com changes, run |
Related to #94426
Fixes #94426
Proposed Changes
This is the second attempt, previously we had to revert due to some tests failing. No code has changed, only a null check to fix the tests
This PR addresses the issue by repositioning the 'deal' badges above the title and ensuring that overly long titles are automatically broken into multiple lines for better readability and layout.
Issue
Fix
Why are these changes being made?
Testing Instructions
Navigate to any flow (e.g., /setup/onboarding/domains) and proceed to the domains step.
Select an excessively long domain name and verify that the layout remains intact (compare it with the production version).
Ensure the domain grid matches the provided screenshots.
Compare it with the /start/onboarding flow and confirm that the horizontal scroll issue has been resolved, especially on mobile or smaller screens.