This issue isn't really related to LESS at all. If you split the Bootstrap CSS into multiple files, then Moodle would stitch them back together again.
It's the output of Moodle that the browsers get to see, not the way the files are organised within the theme. Moodle already had something that sent IE the parent theme CSS, mod style CSS and theme CSS as 3 seperate files for this reason (where normally they are turned into one big file). Moodle 2.5 has improved on this by actively splitting the files on roughly the 4096 limit (and not bothering to do it for IE10, as it doesn't need this).
So mostly, it's all under control and there's no real need to do anything further as Moodle is taking care of deliver the CSS in the fastest way possible to the various browsers. But it did just catch me out today when looking at something for a 2.4 related Bootstrap theme as I added a quick fix to the end of the CSS and wondered why IE9 wasn't seeing it.
David Scotson
Posts made by David Scotson
It's not a line limit, it's the number of "selectors" so
classname,
classname div a,
classname > table.th {
counts as 3 selectors towards the 4096 per stylesheet limit. Moodle sends parent stylesheets, the module stylesheets and the theme stylesheets seperately to IE browsers, so the only one you need to worry about is you theme's moodle.css which currently in Bootstrapbase sits just over the limit, so a few of the styles at the end get ignored in IE9. Low impact styles are intentionally placed near the end to limit this effect.
It worth noting that IE8 and IE9 count these selectors differently. IE8 simply ignores any inside media queries (as used for responsive layouts) since it doesn't understand them. IE9 supports them so they count towards the 4096 limit in that case.
Minification of CSS shouldn't have any impact on this.
classname,
classname div a,
classname > table.th {
counts as 3 selectors towards the 4096 per stylesheet limit. Moodle sends parent stylesheets, the module stylesheets and the theme stylesheets seperately to IE browsers, so the only one you need to worry about is you theme's moodle.css which currently in Bootstrapbase sits just over the limit, so a few of the styles at the end get ignored in IE9. Low impact styles are intentionally placed near the end to limit this effect.
It worth noting that IE8 and IE9 count these selectors differently. IE8 simply ignores any inside media queries (as used for responsive layouts) since it doesn't understand them. IE9 supports them so they count towards the 4096 limit in that case.
Minification of CSS shouldn't have any impact on this.
I think that might just be remembering a setting for your user account. I see the indenting on the desktop version (as long as that's the display option I've chosen).
I think that bug is present but there's an extra one too. It seems like the titletext hasn't been translated properly.
I filed a bug:
https://tracker.moodle.org/browse/MDL-40343
I hadn't realised they'd started using that theme. It doesn't show up for me on Android Firefox or on my Nexus 7 using Chrome.
It looks like there's something odd going on with the menus too. It seems like they've got a custom menu implementation for the standard theme that delivers it's data slightly differently than the standard custom menu? Anyone know where to file bugs for the Moodle site?
https://tracker.moodle.org/browse/MDL-40343
I hadn't realised they'd started using that theme. It doesn't show up for me on Android Firefox or on my Nexus 7 using Chrome.
It looks like there's something odd going on with the menus too. It seems like they've got a custom menu implementation for the standard theme that delivers it's data slightly differently than the standard custom menu? Anyone know where to file bugs for the Moodle site?