Replies: 1 comment
-
You can change or add breakpoints in the tailwind.config so i don't think this should be changed for everyone |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
First, I noticed that the breakpoint units have been changed from px to rem in v4. That's a positive change.
However, I wonder if it’s time to reconsider the current breakpoint values:
I guess these values were established a long time ago when there were fewer device types. The screen size of the original iPad was for example 768x1024px.
From my own experience, I think these breakpoints are a little bit off. I always struggle to choose a good breakpoint range when building a responsive layout. Either the breakpoint triggers too early or too late.
I while ago, I came across an article talking about this. They explained the issue, and presented a simple yet effective solution. The article is several years old, but I think it is still valid today.
In short, instead of basing the breakpoints on some specific device widths, they create breakpoint intervals around groups of the most popular device widths. Following the advice an updated list of breakpoints should be:
Alternatively, for more granular control over smaller sizes:
I realize this change would be a breaking change for v4, and I’m unsure if it’s worth implementing. Since users can easily customize breakpoints in their configuration, it may not be necessary. However, I wanted to share the idea, as it might be worth considering.
Beta Was this translation helpful? Give feedback.
All reactions