Endless props, thanks, and respect to the Bootstrap team. They do an amazing job, sometimes with less-than-amazing levels of gratitude in return.
Bootstrap 3 preview
111–120 of 166 posts
Re: Bootstrap 3 preview
#112The issue Bootstrap still has is that the parts that make use of JavaScript completely rely on JavaScript. If you're on a flakey data connection, for example, and JavaScript doesn't load parts of the page simply break. The tab component is a good example of this - turn off JavaScript in your browser and you'll see that it still looks like tabs (thanks to CSS) but you just can't access anything part from the first tab…
I disagree. As a web designer/developer your job is to make sure your site looks proper. If someone chooses to disable javascript, they know that they are missing out. It's their personal choice to embrace an inferior web experience, and I don't think it's fair to have to compensate for them as well.
Re: Bootstrap 3 preview
#113A big heads up for anyone thinking of switching. Bootstrap 3 "Drops IE7/FF3x support entirely." ref: http://blog.getbootstrap.com/2012/12/10/bootstrap-3-plans/
A big heads up to those people who still support ie7, that is. Google and Facebook dropped support a while ago, and ie7's usage share is around 0.6-2.0% globally. http://clicky.com/marketshare/global/web-browsers/versions/ http://gs.statcounter.com/#browser_version_partially_combine...
IE7 doesn't cause nearly the same scale of problems that IE6 did; I don't think 1% is small enough to justify ignoring it entirely. (I suppose it depends on whether it degrades gracefully or becomes unusable.)
Re: Bootstrap 3 preview
#114The issue Bootstrap still has is that the parts that make use of JavaScript completely rely on JavaScript. If you're on a flakey data connection, for example, and JavaScript doesn't load parts of the page simply break. The tab component is a good example of this - turn off JavaScript in your browser and you'll see that it still looks like tabs (thanks to CSS) but you just can't access anything part from the first tab…
I disagree. As a web designer/developer your job is to make sure your site looks proper. If someone chooses to disable javascript, they know that they are missing out. It's their personal choice to embrace an inferior web experience, and I don't think it's fair to have to compensate for them as well.
...except that JS can also fail due to network lag or simple programming errors (like a trailing JSON comma in IE). Ideally, sites should remain as functional as possible if JS or CSS fail to load. (Admittedly, a great many large websites fail this test.)
Re: Bootstrap 3 preview
#115Earlier quoted context omitted.
A big heads up to those people who still support ie7, that is. Google and Facebook dropped support a while ago, and ie7's usage share is around 0.6-2.0% globally. http://clicky.com/marketshare/global/web-browsers/versions/ http://gs.statcounter.com/#browser_version_partially_combine...
IE7 doesn't cause nearly the same scale of problems that IE6 did; I don't think 1% is small enough to justify ignoring it entirely. (I suppose it depends on whether it degrades gracefully or becomes unusable.)
Indeed, I'm starting a responsive site design project that will have a large target audience in China... where some 20% of users are still on IE6. Looks like I'll be testing both Bootstrap and Foundation.
Re: Bootstrap 3 preview
#116A big heads up for anyone thinking of switching. Bootstrap 3 "Drops IE7/FF3x support entirely." ref: http://blog.getbootstrap.com/2012/12/10/bootstrap-3-plans/
A big heads up to those people who still support ie7, that is. Google and Facebook dropped support a while ago, and ie7's usage share is around 0.6-2.0% globally. http://clicky.com/marketshare/global/web-browsers/versions/ http://gs.statcounter.com/#browser_version_partially_combine...
I hope you understand that global usage is totally irrelevant, when as a web developer you need to target a specific audience.
If your audience is public businesses ie7 shares whill not be just 1% of your target.
If you care only about people using browsers at home,then you are not doing your job.
Re: Bootstrap 3 preview
#117Earlier quoted context omitted.
Use bootstrap, but customize the design to fit your brand. Bootstrap is a framework for building your own CSS on top of. The less opinionated it becomes, the better, since it'll make it easier to adapt the framework for your design.
This is the key to Bootstrap (or similar css frameworks). It's not intended to be a theme. If you want to just have the css/html ready for you to do some documentation or a project that has no need for any visual differentiation, then go ahead and use vanilla. When used to build something that should be visibly unique, the visual design and appeal is something that should be created aside from bootstrap, maybe with t…
Come on yes it is (was) intended to be a theme , that's why it is so successfull. Grid frameworks existed well before bootstrap , and most developers did not use them.
Re: Bootstrap 3 preview
#118Not sure if I like this at all. I think they need to call it Bootstrap 3: flat and fat! It just seems like a huge step back to me. It's not even an elegant "flat" design; it's like they scrapped everything and decided to make all classes (even buttons for God's sake) DIVs of different colors. The new navbar, for example, is literally a gray DIV with rounded edges. I use Bootstrap on my web app because I care about de…
> I use Bootstrap on my web app because I care about design, but I don't care so much about learning fancy CSS
A paradox.
Re: Bootstrap 3 preview
#119For god's sake, just learn some CSS already.
Re: Bootstrap 3 preview
#120Earlier quoted context omitted.
A big heads up to those people who still support ie7, that is. Google and Facebook dropped support a while ago, and ie7's usage share is around 0.6-2.0% globally. http://clicky.com/marketshare/global/web-browsers/versions/ http://gs.statcounter.com/#browser_version_partially_combine...
I hope you understand that global usage is totally irrelevant, when as a web developer you need to target a specific audience. If your audience is public businesses ie7 shares whill not be just 1% of your target. If you care only about people using browsers at home,then you are not doing your job.
I hope you understand that global usage is totally relevant, when as a web developer you don't have a specific audience to target.
Can you elaborate on usage stats of "public businesses" and where you got those from?
If you have usage stats on your audience, then use them. Otherwise, go with the global usage, or at least your country/continent.