Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Mobile-first is the biggest hype after responsive-design, but it is not intended for the type of projects we are doing and for our customers, and probably for most of the drupal projects out there.
We should keep the responsiveness, of course, only implement a desktop-first approach, this will solve oldIEs issues, will allow us to remove respond.js and will allow us to have the responsiveness as an optional feature - this is important for projects that don't take care of different layout for mobile devices - today we force them to be responsive.
Comments
Comment #1
tsi CreditAttribution: tsi commentedDone
Comment #3
tsi CreditAttribution: tsi commentedActualy, we thought about a way we can have both desktop-first and mobile-first responsive layouts, optional and configurable in theme settings so setting this to needs work (and moving to Sasson).
Comment #4
tsi CreditAttribution: tsi commentedThe dev branch now has optional mobile-first responsive layout, Thank you all !
Lame...
Comment #6
mxmilkiib CreditAttribution: mxmilkiib commentedI'm interested in avoiding lower bandwidth mobile devices having to download more style content than required, and in exploring the advantages of Sass and using a variation on 320andup that would compile to multiple .css files, kind of like the examples given on “Mobile first” CSS and getting Sass to help with legacy IE (see also the comments) and IE-friendly mobile-first CSS with Sass 3.2. Might that kind of responsive method fit with the goals of Sasson?
Comment #7
tsi CreditAttribution: tsi commentedWhat exactly are you suggesting ? and how does that differ from the current implementation ?