-
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
Stepper: Fix navigation UI in Stepper #97256
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: App Entrypoints (~102 bytes added 📈 [gzipped])
Common code that is always downloaded and parsed every time the app is loaded, no matter which route is used. Sections (~23733 bytes removed 📉 [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 (~992 bytes removed 📉 [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. |
Fixed in |
I cleaned up the CSS more and tested the user step, the domains step, and the plans step. On Mobile, Tablet, and Desktop. |
This reverts commit e27a58c.
…calypso into fix/navigation-on-stepper
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.
LGTM
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 |
I noticed that this changed the whole stepper design. I'm not sure if that was the right call. @fditrapani can you chime on this? I started reporting this here: |
Thanks for the ping @valterlorran. I have been following this work on the stepper. It does look like the spacing is different than before. I don't think it's a bad thing though. We'll just have to make some adjustments on the non-stepper screens before and after the stepper used in migrations to line everything up. |
Quoting my reply on Slack
|
This changed the navigation position on other steps under the stepper flow. Is it exptected 🤔 |
Removed in #97256. This PR removed an unused prop related to sticky nav buttons, however in tidying up the CSS it ended up removing styles that were still in use.
It removed some CSS which was needed to to have the goals step actions appear in the footer. My guess is it was assumed that the |
Does this fix both issues @alshakero? #97503 |
Removed in #97256. This PR removed an unused prop related to sticky nav buttons, however in tidying up the CSS it ended up removing styles that were still in use.
Fixes: #97067
Proposed Changes
shouldStickyNavButtons
property and the CSS that comes with it.Why are these changes being made?
To bring consistency.
Testing Instructions