Can you point to where you see it in Bootstrapbase? In fact, are you sure it's set for all tables in Moodle? I can't see it in the table listing the topics in this forum for example, even if I add the generaltable class. But I can see it set for specific named tables/cells. Oh, there it is, on .flexible .th I can see it (which is in core.css/core.less).
There's quite a bit of CSS in Moodle to micro-manage the display of tables (and worse, as Mary points out, inline styles to do similar). I personally would take it all out.
Between different languages for UI strings, different data in each Moodle, different screen sizes, different font-sizes, tablets phones etc. it would be a lot easier if we took a more zen approach to tables and just let the browsers display them however they fit on that particular device.
As an example, setting a table width to 80% might nicely center it with some whitespace on a developers display, but leave useless padding around a cramped display on a small tablet or netbook. The fact that every developer does this in a different way (e.g. margin or width on the table, padding on the container, subtly different % values till it looks perfect on their particular display) just bloats and complicates the CSS more.
This is fairly easy for "simple" tables (i.e. row of headers along the top) and I think I might have already done it for most of them that I had access to the styles for in Bootstrapbase. But it would be good to make it a standard across Moodle.
There are of course other, much more complex tables in Moodle that rely on pixel perfect positioning in order to work. That's a completely different issue, but it does mean you can't quickly fix these issues just from looking at the CSS, you need to visually check what each table is trying to do.
But yes, in the modern web world forcing all table headers to remain on one line and take up maximum horizontal space, doesn't help with adaptation to mobile. Maybe you could file it as a sub-task of the Epic mobile issues task in the bug tracker.
You mention th, but isn't your bug about td cells?
David Scotson
Posts made by David Scotson
I've thought about doing this to let people take advantage of some of the more advanced bits of Bootstrap (particularly the javascript: http://twitter.github.io/bootstrap/javascript.html).
It should work pretty much as you say.
I think you could (sometimes) skip a step though and just get TinyMCE to insert the correct HTML in the first place. This would then have the correct visual look even while editing.
See here
http://www.tinymce.com/wiki.php/Configuration:style_formats
and here for a demo:
http://www.tinymce.com/tryit/custom_formats.php
It looks like TinyMCE just had a major update. Does anyone know if/when that going into Moodle?
It should work pretty much as you say.
I think you could (sometimes) skip a step though and just get TinyMCE to insert the correct HTML in the first place. This would then have the correct visual look even while editing.
See here
http://www.tinymce.com/wiki.php/Configuration:style_formats
and here for a demo:
http://www.tinymce.com/tryit/custom_formats.php
It looks like TinyMCE just had a major update. Does anyone know if/when that going into Moodle?
There's a bug in the tracker with a patch that makes similar changes to the course listings but it seems to have got stuck in the pipeline:
https://tracker.moodle.org/browse/MDL-39242
https://tracker.moodle.org/browse/MDL-39242
I seem to recall there was a bug in Bootstrapbase that mean the layouts were not set up to have 3 columns on the frontpage. This would be within the config.php file of the Bootstrapbase theme. You might want to compare the two with a diff tool and see if there's a change there.