[blog] Fix display on Safari #33102
Merged
[blog] Fix display on Safari #33102
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
oliviertassinari
force-pushed
the
fix-blog-safari-display
branch
from
4c2e681 to
25197e0
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I was checking https://twitter.com/constlomo/status/1535066785183301632 out quickly. Before I could start any exploration, I was immediately stopped by:
Otherwise, I couldn't reproduce this tweet on iOS v15.4 in the Simulator nor BrowserStack.
In the US, iOS is almost 60% of the market, on which, all browsers are using Safari under the hood, Chrome included proof: https://gs.statcounter.com/os-market-share/mobile/united-states-of-america, hence most people will notice since blog posts are read a lot on mobile (could be tested in GA).
https://deploy-preview-33102--material-ui.netlify.app/blog/