The 100% correct way to do #CSS #breakpoints
600px, 900px, 1200px, and 1800px if you plan on giving the giant-monitor people something special.
▻https://medium.freecodecamp.com/the-100-correct-way-to-do-css-breakpoints-88d6a5ba1862
The 100% correct way to do #CSS #breakpoints
600px, 900px, 1200px, and 1800px if you plan on giving the giant-monitor people something special.
▻https://medium.freecodecamp.com/the-100-correct-way-to-do-css-breakpoints-88d6a5ba1862
Mouais.
100% correct c’est un peu péremptoire.
Je n’utilise jamais de breakpoints standards, je les définis toujours par rapport aux contenus d’un site.
▻http://bradfrost.com/blog/post/7-habits-of-highly-effective-media-queries
So where should you insert breakpoints? Follow Stephen Hay’s advice:
“Start with the small screen first, then expand until it looks like shit. Time for a breakpoint! –Stephen Hay”
C’est ce que je pratique, sauf que je ne travaille pas mobile first, donc je pars d’une résolution large, que je réduis.
Quand ça pète -> breakpoint.
Oui, c’est ce que pointe le premier commentaire :
This makes more sense than the counter example but it definitely not the 100% correct way. Ideally you want to choose your break points around your content and design, not around devices. This year’s devices are different than last year’s and different than next year’s. Resize your window — when the layout breaks or stops makings sense you have a break point. Devices should have no voice in this decision.
Le plus intéressant dans l’article est certainement cette partie :
that’s basically what you’d be doing if you set your breakpoints at positions matching the exact width of popular devices (320px, 768px, 1024px).
...
I think we mix up “boundaries” and “ranges” in our discussions and implementations of breakpoints.