Live data from Hacker News

Bootstrap 3.0 Upcoming changes

github.com

61–70 of 149 posts

Re: Bootstrap 3.0 Upcoming changes

#61

Really sad they are dropping support for IE7 unfortunately I will not be upgrading to this version then.

Adding support for IE7 will be easy:

- Add the box-sizing polyfill: https://github.com/Schepp/box-sizing-polyfill

- Use 'display: inline; zoom: 1;' (with the * hack) wherever 'display: inline-block;' is used

Re: Bootstrap 3.0 Upcoming changes

#62
post #31

Exciting! I really hope they do end up going with multiple modal widths in 3.1, as I've had to do this myself on more than a few occasions. On a side note, I'm curious as to why they decided to refactor their variable names to include dashes instead of just sticking with camel casing. Personally, I find camel casing to be much more readable.

Although not always, you'll end up mixing CSS with JavaScript. In this case when naming CSS with dashes it's easier to differentiate from my JavaScript names, i.e. $("#myDiv") vs $("#my-div").

Re: Bootstrap 3.0 Upcoming changes

#63
post #7

> Responsive CSS is no longer separate. Will we still be able to easily remove things like the "large desktop" size?

Yes, of course. The customizer will continue to have the ability to include or remove the media queries for these. You can also always make a local build on your own to do it.

Re: Bootstrap 3.0 Upcoming changes

#66
post #22

Earlier quoted context omitted.

You mean, "how about re-engineering the entire project for little benefit"? LESS vs SASS is one of the more infuriating "this vs that" argument circling the web right now, because everyone is so inexplicably vocal and passionate about it. Looks like there is already a SASS port: https://github.com/thomas-mcdonald/bootstrap-sass

The SASS ports tend to lag behind the original or don't leverage the full potential of SASS/Compass. I personally think SASS has won out over LESS since the introduction of SCSS and if Bootstrap dropped support LESS would gradually fade away.

Won out in what sense? Last I checked there are no formal figures about usage for either. Bootstrap's phenomenal popularity ought to make it a kingmaker for the preprocessor it uses, I suspect.

Re: Bootstrap 3.0 Upcoming changes

#67

Glad they are finally using icon fonts instead of PNG. Now we can make icons any color and add drop shadows if needed.

It can be easily done (with any svg/fonts you have) using this awesome tool if you're interested: http://icomoon.io

Hadn't heard of that one but it looks really cool - thanks!

Re: Bootstrap 3.0 Upcoming changes

#68

Earlier quoted context omitted.

When was the last time anybody used FF 3.6? Serious question.

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. :|

Re: Bootstrap 3.0 Upcoming changes

#69

Earlier quoted context omitted.

I was worried when I saw this, but the very next bullet point is: >Overhauled default grid system. Now uses percentage widths, padding, and box-sizing: border-box instead of pixel widths and margins. Nesting and offsets remain the same. Which sounds like they are actually making everything fluid, and removing fixed widths. Perhaps a good thing, although border-box means no IE7 support.

They also removed all IE7 specific CSS hacks. IE7 will no longer be supported at all.

That's bold but the right decision IMO.

Re: Bootstrap 3.0 Upcoming changes

#70
post #7

> Responsive CSS is no longer separate. Will we still be able to easily remove things like the "large desktop" size?

Yes, of course. The customizer will continue to have the ability to include or remove the media queries for these. You can also always make a local build on your own to do it.

Awesome, thanks! I typically just drop in Bootstrap with a Rails gem but this is good to know.
Post reply on HN