I wish they weren't dropping IE7 support. You can make fun of "who uses that!" all you want, but we build a site that is used by government people who can't control their own computers, and our current demographics are 50% IE7! Nothing to be done, we just can't upgrade to Bootstrap 3.0. So -- if you MUST do this, at least leave the website docs up for Bootstrap 2, cause we're not going anywhere...
Bootstrap 3.0 Upcoming changes
81–90 of 149 posts
Re: Bootstrap 3.0 Upcoming changes
#82I wish they weren't dropping IE7 support. You can make fun of "who uses that!" all you want, but we build a site that is used by government people who can't control their own computers, and our current demographics are 50% IE7! Nothing to be done, we just can't upgrade to Bootstrap 3.0. So -- if you MUST do this, at least leave the website docs up for Bootstrap 2, cause we're not going anywhere...
It's not like bootstrap adds 1000 features that can be created manually.
Re: Bootstrap 3.0 Upcoming changes
#83I wish they weren't dropping IE7 support. You can make fun of "who uses that!" all you want, but we build a site that is used by government people who can't control their own computers, and our current demographics are 50% IE7! Nothing to be done, we just can't upgrade to Bootstrap 3.0. So -- if you MUST do this, at least leave the website docs up for Bootstrap 2, cause we're not going anywhere...
Maybe you should be looking into a more custom solution instead of using Bootstrap if you have to support IE7. It's not like bootstrap adds 1000 features that can be created manually.
Re: Bootstrap 3.0 Upcoming changes
#84How about dropping support for LESS and using SASS instead?
does SASS work without installing the pre-processor? I know LESS does. I didn't think SASS did. LESS will work well enough with just the js file loaded (if a bit slower).
You shouldn't be running less.js in production.
Re: Bootstrap 3.0 Upcoming changes
#85Earlier quoted context omitted.
_this_. And why drop support for FF 3.6 too? Is there a technical reason to drop support for older browsers or is it idealism?
When was the last time anybody used FF 3.6? Serious question.
IE 7 is more common, there were 67,841 IE 7 visits. Worse still is the 12,188 IE 6 visits. Amazingly there were 78 IE 5.5 visits, the web must be a crazy place with IE 5.5.
Re: Bootstrap 3.0 Upcoming changes
#86> All variables now use dashes instead of camelCase. For example, it's now @body-background instead of @bodyBackground. Not sure how I feel about this. On one hand that's a pretty large sweeping change that is going to break all my customizations. On the other, dashes look much better in css and I prefer them for class names and so on. Not even sure why, is this some sort of community standard I picked up somewhere a…
I've always wondered why they initially chose camelCase and not dashes. I like keeping camelCase for JS only. CSS uses dashes (border-top). LESS uses dashes in its example documentation.
- do look neater but I wont switch because it frustrates me so much to not have that simple feature!
Re: Bootstrap 3.0 Upcoming changes
#87I wish they weren't dropping IE7 support. You can make fun of "who uses that!" all you want, but we build a site that is used by government people who can't control their own computers, and our current demographics are 50% IE7! Nothing to be done, we just can't upgrade to Bootstrap 3.0. So -- if you MUST do this, at least leave the website docs up for Bootstrap 2, cause we're not going anywhere...
Roughly 10% IE7, 30% IE8, 25% IE9, 17% Chrome, 12% Firefox, 6% Safari. No IE10 yet, not even one.
Re: Bootstrap 3.0 Upcoming changes
#88I wish they weren't dropping IE7 support. You can make fun of "who uses that!" all you want, but we build a site that is used by government people who can't control their own computers, and our current demographics are 50% IE7! Nothing to be done, we just can't upgrade to Bootstrap 3.0. So -- if you MUST do this, at least leave the website docs up for Bootstrap 2, cause we're not going anywhere...
Re: Bootstrap 3.0 Upcoming changes
#89Earlier quoted context omitted.
It's the 16th most popular user agent seen across the ~60,000 websites tracked by W3Counter. IE7 is the 7th. Dropping support for both will affect 1 in 20 visitors of the 'average' website (your particular audience may vary).
Maybe 5% of users need to get their shit together and upgrade. :|
Hospitals and big companies lock down the computers, you can't install anything. If it comes with IE7, that's all you got.
And it's not because of these companies.
E.g. they need to run a specific custom version of SAP (accounting), which on turn crashes if any other browser is present. Upgrading would cost over $30M, so forget it for a while.
Or the hospital needs to validate the hardware + OS + software. Until GE does not support feature X they are stuck with the old version which requires a specific list of software to be installed.
You don't want to hear "sorry about the bad news last week that you have cancer - actually it was just a rendering glitch on your MRI due to the new Chrome version".
So life is a bit more complex than "just upgrade"...
Re: Bootstrap 3.0 Upcoming changes
#90"Dropped all things fluid." Looks like I've got some updating to do in the near future.