You can't use Bootstrap CSS directly because many of the things in Moodle e.g. form elements use their own HTML, not Bootstrap HTML.
The two main ways to work around this are to use renderers (which let you rewrite the HTML in Moodle to what Bootstrap expects) and to use LESS to compile the .less files provided by Bootstrap and map them to the HTML that Moodle provides.
The upstream Bootstrap less files are in /less/bootstrap/, the files that convert it to Moodle are in /less/moodle/ and the renderers that rewrite the HTML are in /renderers/.
When you run "grunt less" it creates the moodle.css file, if you're heavily customising your theme, you'll probably need to learn about that so you can add your own changes to the CSS.
David Scotson
Aportación realizada por David Scotson
It doesn't seem to happen for me on the latest 2.7 master branch.
Maybe something they've done has fixed it (though note I've not got a 2.6 site handy to see if it's affecting me at all, IE8 bugs are weird enough that you can't make any assumptions). I know they were looking at z-index stuff recently because of a few issues like this.
Maybe something they've done has fixed it (though note I've not got a 2.6 site handy to see if it's affecting me at all, IE8 bugs are weird enough that you can't make any assumptions). I know they were looking at z-index stuff recently because of a few issues like this.
There seems to be a gap between "Moodle has dropped support for IE8" and "IE8 and Safari 5 are no longer fully supported. They should still work ... there might be some problems".
Given that people have been adding CSS specifically for ie6 within the last few months, and I found that out while having tracker issues to remove CSS for ie6 and 7 denied unless I could prove that removing a few hundred lines of CSS made things faster, I'm not sure the actual policy is communicated or understood as clearly as it might be. Certainly the recent discussion in this theme forum seems a lot more direct than any previous official announcement I've seen.
Personally I'd make some effort for IE8, while also strongly recommending that people get off XP as soon as possible, so the "no longer fully supported" seems the right compromise. I'd suggest that if someone provides a simple enough fix then that's worth using.
Given that people have been adding CSS specifically for ie6 within the last few months, and I found that out while having tracker issues to remove CSS for ie6 and 7 denied unless I could prove that removing a few hundred lines of CSS made things faster, I'm not sure the actual policy is communicated or understood as clearly as it might be. Certainly the recent discussion in this theme forum seems a lot more direct than any previous official announcement I've seen.
Personally I'd make some effort for IE8, while also strongly recommending that people get off XP as soon as possible, so the "no longer fully supported" seems the right compromise. I'd suggest that if someone provides a simple enough fix then that's worth using.
You can upload photos (and probably videos and maybe audio) through the web interface, at least on Android.
It's not perfect (mostly to do with javascript-based pop-up modal windows not being as responsive as they should have been) but overall I found the experience of uploading a photo much better than the desktop equivalent.
It might be interesting to compare it with the apps.
It's not perfect (mostly to do with javascript-based pop-up modal windows not being as responsive as they should have been) but overall I found the experience of uploading a photo much better than the desktop equivalent.
It might be interesting to compare it with the apps.
For the menu, I noticed last night that the burger icon wasn't doing anything on Firefox for Android. This also seems to be the case if I narrow the window on desktop Firefox (v26 on Ubuntu). Actually desktop Chrome (and Chromium) shows this for me as well.
And, while checking out the drop-down ("contact us") on the full width desktop menu, it just seemed weird on Firefox.
Let me see if I can pinpoint this better. If I put my mouse pointer to the right of the "contact us" (so outside the hover area) and then move it over the text "contact us", it works only about 50% of the time. Sometimes I'm a fair distance in before the hover triggers, sometimes it doesn't trigger at all (and sometimes it works as I'd expect).
Sometimes, if I aim for the top of the text, my cursor turn into the text selection I icon, and I can make it all the way across both "contact us" and "discussion forum" links before the hover triggers on "The Program".
Actually, scratch that. It only seems to happen when I have the Firefox Developer tools window open.
For duplicate CSS, if I examine the social icons in Firefox it tells me that e.g. the .fa-twitter:before CSS is defined on line 1286 and again (identically) on line 3404.
The hover on your green buttons seems to be getting overruled incorrectly. I think some of the stuff required to style Moodle's buttons is too strong (which reminds me I really need to revisit how hard it would be to fix these buttons at source via renderers).
edit: also, not a them issue but some of your content in mistyled here:
http://2014.imoot.org/mod/page/view.php?id=1
The list under "Registration includes:" is actually a nested list and has a style attribute on the outer li trying to make one of them unstyled, which might be better as class="list-unstyled" if that's the intention. At the moment the list is numbered but the numbers are half-hidden for me.
And, while checking out the drop-down ("contact us") on the full width desktop menu, it just seemed weird on Firefox.
Let me see if I can pinpoint this better. If I put my mouse pointer to the right of the "contact us" (so outside the hover area) and then move it over the text "contact us", it works only about 50% of the time. Sometimes I'm a fair distance in before the hover triggers, sometimes it doesn't trigger at all (and sometimes it works as I'd expect).
Sometimes, if I aim for the top of the text, my cursor turn into the text selection I icon, and I can make it all the way across both "contact us" and "discussion forum" links before the hover triggers on "The Program".
Actually, scratch that. It only seems to happen when I have the Firefox Developer tools window open.
For duplicate CSS, if I examine the social icons in Firefox it tells me that e.g. the .fa-twitter:before CSS is defined on line 1286 and again (identically) on line 3404.
The hover on your green buttons seems to be getting overruled incorrectly. I think some of the stuff required to style Moodle's buttons is too strong (which reminds me I really need to revisit how hard it would be to fix these buttons at source via renderers).
edit: also, not a them issue but some of your content in mistyled here:
http://2014.imoot.org/mod/page/view.php?id=1
The list under "Registration includes:" is actually a nested list and has a style attribute on the outer li trying to make one of them unstyled, which might be better as class="list-unstyled" if that's the intention. At the moment the list is numbered but the numbers are half-hidden for me.