Giter Club home page Giter Club logo

Comments (5)

leeoniya avatar leeoniya commented on August 29, 2024

@leejordan ping

from reflex.

leejordan avatar leejordan commented on August 29, 2024

I'm going investigate all open issues when I have a day clear to look at them. Bear with me!

from reflex.

leejordan avatar leejordan commented on August 29, 2024

I've given this some thought and I think that because it's easy to change the breakpoints (when compiling via LESS or SCSS) I won't be changing the defaults as it's my personal preference to use the breakpoints in this way.

How much of a problem is this for you? When you say it's counter-intuitive is that relative to your expectations or to your experience of using other layout grids?

from reflex.

leeoniya avatar leeoniya commented on August 29, 2024

@leejordan

From [1]:

We occasionally use media queries that go in the other direction (the given screen size or smaller):

This is basically what i expect, though it seems not to be the default in most grids. My reasoning is that when you serve a page, you serve all the content because you don't have another chance to get it (especially if js is disabled). The layout for all the content is desktop, so you design the desktop layout first (for all screens larger than some value). Then you progressivly work downwards the common tablet/mobile screen sizes using the logic "if screen is <= 768"...else if "screen <= 640"...else if "screen <= 480". This works out to max-width rules rather than min-width rules. It's more intuitive to me because you never "fetch additional" content for bigger screens, you instead "collapse" existing content for smaller breakpoints (presumably commons screen sizes) that can no longer fit it.

Also, I expect that grid__col-xs-6 would apply a 50% width to "xs" devices which is "<=480px". Currently xs actually excludes 480px, which is unexpected.

EDIT: with the inversion the breakpoint names don't hold their original meanings, and < 480 would need to become something like xxs.

I don't really understand the "mobile-first" terminology (if this is it), it seems backwards. Mobile-conscientious perhaps.

[1] http://v4-alpha.getbootstrap.com/layout/overview/

from reflex.

dmoojunk avatar dmoojunk commented on August 29, 2024

@leeoniya The mobile first approach is really just so you think about presenting information on small screens first, as they are the most difficult to design. If you can get a good layout on mobile the desktop should easily follow. The inverse is much harder.

from reflex.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.