50218128
Bootstrap 4 alpha
181–190 of 216 posts
Re: Bootstrap 4 alpha
#18250218128
50218125
Re: Bootstrap 4 alpha
#183Does anyone know why they don't want to support right-to-left? I've seen tons of questions and posts about it over the years so I'm surprised that even with the next major release they aren't addressing it. Maybe I'm missing a perspective here though -- don't other people think that rtl should be a core capability of a framework like this? I'm also curious whether accessibility will be improved in 4.x.
Just to be clear, you're talking about the text direction, for languages like Hebrew and Arabic? (We Americans are typically blissfully unaware that other languages are actually used on the internet - this is a great opportunity to talk about the importance of i18n)
Yup. Though it's not like it's hard to find samples and compare them. Source: I write typesetting software.
Re: Bootstrap 4 alpha
#184well glyphicons have been removed, didn't even notice it in the docs.
Re: Bootstrap 4 alpha
#185No backward compatibility with Bootstrap 3?
I prefer it that way. Last thing a front-end framework needs is a bunch of legacy cruft, and they're going to continue supporting v3.
The migration doesn't seem like a tall order: http://v4-alpha.getbootstrap.com/migration/ though my v3 projects are going to stay on v3 until it's time for a complete UI redesign.
Re: Bootstrap 4 alpha
#186Line 22: view-source: http://themes.getbootstrap.com/products/application
Kudos to whomever wrote it. The customized meta tags crap for each service has gone too far.
Re: Bootstrap 4 alpha
#187Does anyone know why they don't want to support right-to-left? I've seen tons of questions and posts about it over the years so I'm surprised that even with the next major release they aren't addressing it. Maybe I'm missing a perspective here though -- don't other people think that rtl should be a core capability of a framework like this? I'm also curious whether accessibility will be improved in 4.x.
I'm curios to know what doesn't work in rtl? Does bootstrap uses `margin-left` and stuff like that? It should be simple to fix it .some-class { margin-left: 1em; &[dir="rtl"] { margin-right: 1em; } }
It is a little more complicated because you have to omit the previous rule as well (and overriding it may interfere with other CSS rules), so it should be:
.some-class {
&[dir="rtl"] { margin-right: 1em; }
&:not([dir="rtl"]) {
margin-left: 1em;
}
}Re: Bootstrap 4 alpha
#188Is there any reason checkboxes and radio buttons aren't styled, e.g. like in wtfforms? Are there plans to merge that project into bootstrap?
We've got them! See http://v4-alpha.getbootstrap.com/components/forms/#custom-fo... :).
Re: Bootstrap 4 alpha
#189Do you know what plugins they used to transform Markdown into HTML?
Our docs are built on Jekyll, which takes either HTML or Markdown for page content. Markdown is so much faster to write in for docs, especially since we no longer have to escape inline HTML by hand haha.
Re: Bootstrap 4 alpha
#190Earlier quoted context omitted.
> The same issue exists with v3 needing a LESS compiler. Only there are TONS of LESS compilers, even a straight PHP one, a pure JS etc, whereas Sass has either Ruby or a C/C++ dependency.
The last time I looked at the PHP one, it compiled fine, but wasn't handling variables scopes in the same way of the JS one. This was a big deal for me.
Yeah, which is one of the reasons why I'm not a fan of Assetic in Symfony. The PHP versions of front-end build components are always lacking, unfortunately. But that's not a big deal in my opinion, you basically always need Node for a front-end application at this point for other needed tooling (Browserify/WebPack, Babel, etc.) so better to use the best-of-breed tooling and ignore Assetic as much as possible.