>> The basic difference is that a browser will first try to render the mobile - small resolution, and more simple - layout, and will then try to apply the "enhancements" provided by the responsive design.
Could you explain this with Code? On Saturday, May 18, 2013 5:56:47 AM UTC+8, Sherbrow wrote: > > Hi, > > As I understand it - aside from any *new things* that the third version > will introduce - the mobile first aspect will not change the code. > > The basic difference is that a browser will first try to render the mobile > - small resolution, and more simple - layout, and will then try to apply > the "enhancements" provided by the responsive design. Version 2 does it the > other way, retro-fitting a fully featured layout into a smaller screen. > > The thought process should change (if it wasn't already that) because you > have to make your website mobile-ready at the least, and then think about > the desktop screens. > > TWBS3 is still a work in progress, but it will also introduce features to > improve mobile support (I have the col-small-spanX in mind, which is a grid > for mobiles). > > Nevertheless the new version will change quite a few things : some class > name refactoring, default appearance, fluid only, font icons, ..., you can > check everything as it's changing on > github<https://github.com/twitter/bootstrap/tree/3.0.0-wip> > > On Friday, May 17, 2013 1:04:48 PM UTC+2, Shark Huang wrote: >> >> Hi Gurus, >> Could you please explain why bootstrap3 was labeled as "mobile first"? >> Please help give some example against the code? >> >> Br >> Shark >> > -- You received this message because you are subscribed to the Google Groups "twitter-bootstrap" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
