Closed mayank99 closed 1 year ago
Breakpoints were chosen based on this article: https://polypane.app/blog/css-breakpoints-used-by-popular-css-frameworks/ (not random)
Also, breakpoints were chosen based on the same article that you gave here, that says not to take some specific resolution.
Breakpoints were chosen based on this article: polypane.app/blog/css-breakpoints-used-by-popular-css-frameworks (not random)
Those are random though. We don't know how those frameworks came up with those values, and they might have copied even other frameworks.
Also, breakpoints were chosen based on the same article that you gave here, that says not to take some specific resolution.
Then how did we arrive at values like 769 and 991? Those are currently the bounds of tablet
breakpoint and they will not match 768x1024
and 1024x1366
, both of which are tablets. I think there are also some smaller tablets with resolutions like 601x962
.
Even if you insist on keeping the same breakpoint values, the other three points I mentioned still apply.
Currently, the breakpoints are handled like this:
This approach has a few problems:
min-width
or onlymax-width
. There are very limited uses for specifying both constraints.486.5px
will match neither mobile nor landscape-mobile) which are sometimes possible, especially with iframes.500px
,1100px
and1500px
work great as breakpoint values. This will still not account for the many permutations within these sizes, e.g. changed font size, resized window, multi-window on android/ipad. And that's fine, it is still a much more methodic approach based on real data rather than picking random values from other projects (which might in turn be based on random values picked by yet other projects).Further reading: https://www.freecodecamp.org/news/the-100-correct-way-to-do-css-breakpoints-88d6a5ba1862/