4 ms·
This has great potential to interfere with other css modules like nprogress or noUIslider to throw a few. The same reason why the <table> element requires a 'ta
by hamhamed 12y ago
This has great potential to interfere with other css modules like nprogress or noUIslider to throw a few. The same reason why the <table> element requires a 'table' class for bootstrap as explained here: http://getbootstrap.com/css/#tables http://getbootstrap.com/css/#tables
For basic styling—light padding and only horizontal dividers—add the base class .table to any <table>. It may seem super redundant, but given the widespread use of tables for other plugins like calendars and date pickers, we've opted to isolate our custom table styles.
- foreigner 12y agoMaybe you could work around this by adding a single class: "explicit". If that class is present it resets all the tacit css back to default.
- callum85 12y agoThird party components (date pickers etc.) wouldn't know about the 'explicit' class so it would be up to the user to add this class to all non-semantic tables to 'undo' the Tacit CSS, but they won't know which components output such tables... This is supposed to be a drop-in 'make the page look nice' thing.
- Demiurge 12y agoIf you're adding widgets to your page, you're probably not a dummy or the intended user of this css :)
- normloman 12y agoWithout classes, it certainly will break other styles. But I reckon the intended user won't use other styles. This is perfect for someone who wants to make a static page, and doesn't want to bother with CSS.