-
Notifications
You must be signed in to change notification settings - Fork 385
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
Improve font sizes in onboarding wizard and settings screen #5192
Conversation
Plugin builds for dd7e592 are ready 🛎️!
|
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.
Very nice in terms proportionality and consistency. Ship it!
…sizes * 'develop' of github.com:ampproject/amp-wp: (22 commits) Allow legacy theme name to be translated, update description, use constant, s/classic/legacy/g Reindex array keys to ensure they are sequential Remove unused import and unskip tests Fix equals sign alignment Make sure override doesn't block selection in wizard Remove unnecessary init call on wp_scripts instance Mark action as internal Settings screen: switch to legacy if selected reader theme is active site theme Include JS maps if it's a development build Ensure JS vendor directory is included in build Call amp_register_polyfills action in a few more places and document it Add action hook for registration of polyfills Use curly-brace substitution instead of sprintf/concatenation Comment spacing fix Polyfill assets during paired browsing Remove conditional and delayed interfaces from polyfills class Modify conditional check for class registration Polyfill assets during paired browsing Initiate scripts and styles in tests Remove lodash from bundles (shouldn't have been included in the first place) ...
Looks much better!
|
Yeah; much better. |
Added initial fix for cramped buttons on Moto G4:
For fuller fix, see #5193. |
All these changes look great! Significant improvements. One question: the |
Ah yes. This is just hidden because I selected Legacy. I should have selected a Reader theme so that supported templates would be shown. |
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.
Significant improvements indeed.
@westonruter I didn't see anything on desktop that stood out to me. On mobile I found a number of issues that we may want to address: MOBILE - ONBOARDING
MOBILE - SETTINGS
Granted, some of these are not related to fonts, but if we think they're worth doing I can open a new issue for them. cc @amedina |
Center align in what way? I think this looks ok to me.
And what should the resolution be? Hide the warning labels on mobile? |
…sizes * 'develop' of github.com:ampproject/amp-wp: (44 commits) Mock Reader themes provider Delete obsolete deletion of theme_roots site transient Use LoadsCoreThemes in remaining tests Reuse variable for condition Make ReaderThemes::normalize_theme_data() private Explicitly ignore legacy theme since not yet pushed to array Remove unused asset dependency Add test for ReaderThemes::using_fallback_theme Add tests for admin notice printers Remove outdated hook dependencies Remove screenshot from being required for DesktopScreenshot.propTypes Enable the "Customize Theme" button after installing the new Reader theme Replace astra with neve for testing since astra is suspended Remove user capability check from ReaderThemes::using_fallback_theme Ensure AMP legacy theme is being used as a fallback Only programmmatically select legacy theme when current Reader theme is unavailable Restrict showing legacy fallback notice to admins on themes screen and AMP settings screen Add link to reader themes drawer Ensure paired browsing template_include filter overrides other filters Make registration of core theme directory in tests DRY ...
Problem: Those are |
I think since these template modes are the only ones shown on the screen, it is OK to be expanded by default. It also ensures the notices are displayed. |
I'm ok with keeping it as is. Was thinking we would move the objects to the middle of the screen on mobile.
Agreed, that makes the most sense to me.
If they semantically need to be h3 and h4, then I agree it makes sense to keep them different sizes. |
Summary
font-size
of heading in theme cards to1rem
.font-size
ofh3
to consistently be1.2rem
regardless of viewport width.👇 See comments below for additional changes.
Checklist