3 ms·
Does anyone else feel like every time they release a new version of Bootstrap it is never backwards compatible? I feel like lots of divs on my site need differe
by bretthardin 14y ago
Does anyone else feel like every time they release a new version of Bootstrap it is never backwards compatible? I feel like lots of divs on my site need different classes than were used before.
- markdotto 14y agoThere should be no problems upgrading from 2.1.2 to 2.2.0—no features were removed and none had their classes changed.
- bretthardin 14y agoThanks Mark.
- latchkey 14y agoTwo changes that I found affected me: .label's are now display: inline-block. In my particular usage, I needed block in one area. tooltips used to default to html: true and now they default to html: false - The issue with this is that popovers are now html: false as well. I think popovers should default to html: true given their nature.
- damoncali 14y agoThere is something very wrong with having to "upgrade" your CSS.
- phillmv 14y agoMy only problem is that they don't version the docs. I couldn't care less if it were easy to find the docs. I had to revisit a bootstrap 1 site I put together for a client and it was very annoying to track down the documentation. I considered opening an issue on github but…
- sbarre 14y agoYou can just grab the tag of the version you need from Github and the docs are included in there. i.e. https://github.com/twitter/bootstrap/tree/v1.0.0 https://github.com/twitter/bootstrap/tree/v1.0.0 If that's too complicated for you, I believe there is even someone who hosts an archive of all the version of the docs? He posted elsewhere in this thread.. http://bootstrapdocs.com/ http://bootstrapdocs.com/