31–40 of 64 posts
I sincerely hope BS4 is the last nail in IE9's coffin.
Out of curiosity, is there anything significant other than flexbox that's not in IE9 but is in IE10/11?
CSS Transitions is probably the biggest one, but there's a lot, and a ton of javascript improvements too.
Why is there over 1000 !important's in bootstrap.css? I always thought 1 !important was a big no no.
(In a framework, different matter quite possibly. Don't they use only-their-own-class-names anyway? Nevermind..)
I sincerely hope BS4 is the last nail in IE9's coffin.
Out of curiosity, is there anything significant other than flexbox that's not in IE9 but is in IE10/11?
Why is there over 1000 !important's in bootstrap.css? I always thought 1 !important was a big no no.
Though, one thing I noticed going through the docs, the first thing I always look at is the "forms" section. For most apps, forms are probably the most important aspect (at least, for me they are).
I noticed that there are still two type of forms, normal ones and inline. However, when I work on larger apps that require more sophisticated input I often require a mix of both normal and inline forms. Maybe when you're working on SPA's it's easier to have multiple forms on a page and treat them as a single form but for old-school traditional page submit apps it's a little bit more difficult.
Anyhow, I wished they'd make the "form-inline" style more a form group thing rather than a form element thing. Currently the forms have a "form-group" which only contains a single control. To me (and correct me if I'm wrong), "form-group" should actually be named something like "control-group" so that "form-group" could be used to have both a normal and inline style form within the same form, maybe the ability to apply "form-inline" to a or something. If that makes sense..
Anyhow, I'm rambling. Love Bootstrap. Keep it up!
What is the best way to extend bootstrap without loosing an ability to update it in the future and also do not have a ton of duplicated code?
From that approach, one useful example I have seen is the infrastructure of the Bootswatch project. [1] Perhaps unsurprisingly for how many themes Bootswatch maintains, their GitHub repository is quite well laid out, easy to learn from, and even easy enough to fork as the basis of your own project.
what is the compatibility store for third party components/themes based on bootstrap. one of the things I love about bootstrap is being able to google "bootstrap " and get something that works and looks nice. will these third party components need to be re-written and support multiple bootstrap versions?
> what is the compatibility store for third party components/themes based on bootstrap. I can't speak to components, but for themes there's already a migration guide, and I'd expect to see tools that help with the conversion since they're conceptually similar. https://v4-alpha.getbootstrap.com/migration/ > will these third party components need to be re-written and support multiple bootstrap versions? They'll need to…
I recall that happened with the Bootstrap 2 and 3 transition with some components maintaining versions for both for a while.
Did they get smaller?
I'm using BlazeCSS right now because it's very small.