List of all cross-browser gotchas from the Bootstrap site: - Striped tables are styled via the :nth-child CSS selector, which is not available in IE8. - IE and Safari don't actually support the attribute on a - Avoid using elements here as they cannot be fully styled in WebKit browsers. - If you add the disabled attribute to a , Internet Explorer 9 and below will render text gray with a nasty text-shadow that we cann…
Bootstrap 3 RC1
91–100 of 143 posts
Re: Bootstrap 3 RC1
#92The Bootstrap grid system now appears crazy complex to me. I really wish all browsers would now support modern CSS3 Flexbox.
Re: Bootstrap 3 RC1
#93Seems like navigation might be broken on the Nexus 7.
Re: Bootstrap 3 RC1
#94So what exactly is the point of bootstrap? It includes an entirely pointless (and poorly made) grid system; an excessive (and unnecessary) css reset; complex & slow selectors, and lots of default styling you're probably going to replace anyhow. If it were a bunch of separate modules you could individually include and use as a template for your own style, you could actually use the parts you need: as it is, I really d…
If it were a bunch of separate modules you could individually include and use as a template for your own style, you could actually use the parts you need Version 3 is very modular. You can compile the LESS files yourself and include only what you need.
You could already do that with 2.x too. I did this with a site that I built using bootstrap 2.3. No one knows that site is bootstrap until I tell them we used it. We made our own bootstrap.less file that only pulled in the .less for the modules we needed, so we could minimize the bloat.
Also, bootstrap uses normalize now, not reset. This poster should make a little more effort to understand before criticizing. It's obviously a useful framework as many find it very useful. Coding and html css for a complex is not something a developer wants to do unless they have very, very good expertise in front end development. I think bootstrap is great for developers who aren't front end experts, but aren't necessarily bad developers. Maybe specializing in back end work, database, web server side stuff. Using bootstrap frees you up to focus on things that matter more for your app, and you don't have to worry about typography, typeahead, grid systems, etc. It's one of many options that satisfy this need, such as Zurb's Foundation.
Re: Bootstrap 3 RC1
#95Cue a dozen comments about flat buttons. This looks like a nice set of changes for Bootstrap. I'm not sure how I feel about the grid class name changes, but then again, I went all-in on Foundation a few months back, so it doesn't affect me one way or another. I'm sure mdo and fat have excellent reasons for using Less instead of Sass, but I'm a Rails user and I like Sass better to boot. Anyway, no matter, I'm glad to…
Ugh, those aren't buttons. Those are text inside a rectangle. :(
http://monosnap.com/image/Vc05ZRQmGTmRrYvTEbLaYAI6w.png -- those do not look interactive at all.
Re: Bootstrap 3 RC1
#96List of all cross-browser gotchas from the Bootstrap site: - Striped tables are styled via the :nth-child CSS selector, which is not available in IE8. - IE and Safari don't actually support the attribute on a - Avoid using elements here as they cannot be fully styled in WebKit browsers. - If you add the disabled attribute to a , Internet Explorer 9 and below will render text gray with a nasty text-shadow that we cann…
These are pretty minimal for most of the work I do, but what would be nice is if they had a separate section in the docs that tracked all the cross-browser gotchas in one place (let me know if that already exists and I missed it). We are fine with abandoning IE 8. 4% of our user base uses IE8, and I think by 8-12 months from now that will have dropped to below 1-2%. Any major features that don't work, we can workaround (like using respond.js to support media queries on ie, or hacks to support placeholder attribute in IE, etc).
Re: Bootstrap 3 RC1
#97just tried replacing the css files with the new ones , navigation and many things broke ..but any how I like it, I will integrate it after checking out docs ..
Re: Bootstrap 3 RC1
#98Earlier quoted context omitted.
As I'm sure you well know, a mixing includes vendor specific prefixes. And the whole point of mixins is to make it easier to maintain. Once they're written, you don't need to worry.
Unless you're supporting Firefox 3.5 for some weird reason, you haven't needed vendor prefixes for almost two years.
That's great news if it's true. Happen to have a link or citation backing that up??
Re: Bootstrap 3 RC1
#99Earlier quoted context omitted.
Unless you're supporting Firefox 3.5 for some weird reason, you haven't needed vendor prefixes for almost two years.
That's great news if it's true. Happen to have a link or citation backing that up??
Re: Bootstrap 3 RC1
#100Earlier quoted context omitted.
If you are writing a web application of sorts that needs to have a basic theme (buttons, forms, menus, etc) then Bootstrap serves a good purpose and gives you a responsive layout along with it. It also brings some sense of uniformity across apps for more complex controls. For anything beyond that you are better off with yui/pure or csswizardry/inuit which offer much better responsive grid systems. Pure has one shortc…
You forgot the option of "no framework, I'll build it myself and have ultimate control". It's not rocket science, it's HTML and CSS, and you don't need a framework to have uniformity or responsiveness. Your site could be made up of a bunch of jquery plugins too, and stock library graphics, and is your content rehashed too? div class=span4 is nothing more than a table-based layout in disguise. Spans and rows are not i…
You're forgetting the key benefit of frameworks built on preprocessors like Sass or LESS: you can use their mixins to define semantic CSS rules, without using presentation classes.