Still punting ARIA support?
Bootstrap 3.0 Upcoming changes
131–140 of 149 posts
Re: Bootstrap 3.0 Upcoming changes
#132Earlier quoted context omitted.
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.
Well, the CSS preprocessor ecosystem is a clusterfuck (pardon my french).
Since the differences are so marginal I wish projects would pick their preprocessor by the number of available implementations (in popular languages) rather than the latest fashion.
Less and stylus only have javascript impls and should be avoided for that reason alone. The same applies for most other niche processors.
Like it or not, SASS appears to be the only one with a C library that enables a wide range of language bindings.
Re: Bootstrap 3.0 Upcoming changes
#133Earlier quoted context omitted.
IE8 runs on XP, though. Just about every Windows computer still in operation should have IE8 installed, for security reasons if nothing else.
Should but from what I understand IE6/7 still account for fairly large portion of our revenue.
Really? Are you in enterprise software or something? We (WePay) see less than 1% of our traffic and revenue from IEWe still officially support 7 for our offsite/embeddable stuff, but from the chatter I hear of the devs that are working on that stuff, the maintenance cost sounds higher than the revenue. Then again, that cost to us is yet another reason that people like our API, since its one less tedious thing for other devs to worry about in their checkout process.
Re: Bootstrap 3.0 Upcoming changes
#134How about splitting inverted navbar into a separate less file?
Re: Bootstrap 3.0 Upcoming changes
#135Earlier quoted context omitted.
When was the last time anybody used FF 3.6? Serious question.
Not a lot, but they are there. I just pulled the Google Analytics numbers for one of my sites and over the past 30 days (3.3M visits) there were 3,003 visits with Firefox 3.6 (1.2% of all FF visits and .09% of all visits). 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.
I recently found my Windows 98 CD. I should pop that into VMware and try out the Internet.
Re: Bootstrap 3.0 Upcoming changes
#136When will input and button size classes (e.g. input-xxlarge) be normalized as hinted to in the current docs?
Re: Bootstrap 3.0 Upcoming changes
#137Earlier quoted context omitted.
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.
Well, the CSS preprocessor ecosystem is a clusterfuck (pardon my french). Since the differences are so marginal I wish projects would pick their preprocessor by the number of available implementations (in popular languages) rather than the latest fashion. Less and stylus only have javascript impls and should be avoided for that reason alone. The same applies for most other niche processors. Like it or not, SASS appea…
In the Microsoft corner of the world, DotLess[1] is pretty popular, and way more mature than any SASS libraries in .NET.
Re: Bootstrap 3.0 Upcoming changes
#138Earlier quoted context omitted.
There is however the problem that historically they have not keep a copy of the old docs online. So if you stick to 2.2.2 your probably going to be SOL when it comes to reference info. Sure there is an archive somewhere of the old docs but that is a long way from ideal.
Aren't the docs part of the repo?
Yes they are. Get them here:
https://github.com/twitter/bootstrap/tree/master/docs
Re: Bootstrap 3.0 Upcoming changes
#139> 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…
Could someone create a compatibility stylesheet that defines all the camelCased variables based on the new dashed values? Just as a stand-in until you can update all your variables. That or can someone write up a nice Sed script to grep through my less files and change all the variable names?
It may be limited, but seems to be a good start:
$ cat The following sed will replace camelCase only if it can find an arobase
> character in the current line, thus fooBar and bazThing won't be replaced
> but @fooBar and @awesomeFooBarBazzProperty will.
> True story.
> HN
The following sed will replace camelCase only if it can find an arobase
character in the current line, thus fooBar and bazThing won't be replaced
but @foo-bar and @awesome-foo-bar-bazz-property will.
True story.Re: Bootstrap 3.0 Upcoming changes
#140Earlier quoted context omitted.
Well, the CSS preprocessor ecosystem is a clusterfuck (pardon my french). Since the differences are so marginal I wish projects would pick their preprocessor by the number of available implementations (in popular languages) rather than the latest fashion. Less and stylus only have javascript impls and should be avoided for that reason alone. The same applies for most other niche processors. Like it or not, SASS appea…
In the Microsoft corner of the world, DotLess[1] is pretty popular, and way more mature than any SASS libraries in .NET. [1] http://www.dotlesscss.org/
Recently I was investigating using LESS on windows. I didn't want to do it at run-time a la DotLess, but at build-time. I wasn't able to install node.js so i had to scout around for other options...
I came across this: https://github.com/duncansmart/less.js-windows
It leverages the fact that windows has long supported running JavaScript (OK technically "JScript") outside of the browser, without node, to create a command line utility from the less.js implementation. Works perfectly :)