-
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
Signup: Use preventWidows
on mockup title and tagline.
#32670
Conversation
Here is how your PR affects size of JS and CSS bundles shipped to the user's browser: Sections (~69 bytes added 📈)
Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to. 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. |
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.
d62d604
to
43e189f
Compare
I just rebased this on top of the site information deletion changes
Looks like Maybe we should leave it off for the mobile view, and allow the words to wrap? The mobile view is restricted to a width of Or – 😱– leave it out altogether, since it's introducing a text effect that won't exist in the theme a user chooses regardless. Making the preview look nice is a worthy goal however, so I don't want to 💩on the motivations behind this PR. But I can if that's your thing. ^ sounds like an invulnerability drug for married people |
Using preventWidows() on the title seems to be more trouble than its worth. I do think it makes sense for the tagline, though. |
Thanks for pointing this out. We don't |
Some of the larger-font site styles (Calm and Sophisticated) have title and tagline wrapping issues. On the end site, these values will be filtered through
widont
, so we can usepreventWidows
for the mockups.To Test: