You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 8, 2022. It is now read-only.
Bootstrap currently interferes with the styling of other elements of LabKey, particularly the header/navigation bar.
The LabKing module should be completely self-contained and not affect any surrounding modules. We can achieve that by ensuring that we only use namespaced CSS classes. Rather than prefixing all classes with labking, we can nest our classes inside a 'module' class, in the SMACSS style.
Bootstrap currently interferes with the styling of other elements of LabKey, particularly the header/navigation bar.
The LabKing module should be completely self-contained and not affect any surrounding modules. We can achieve that by ensuring that we only use namespaced CSS classes. Rather than prefixing all classes with
labking, we can nest our classes inside a 'module' class, in the SMACSS style.Bootstrap can't just be dropped into a namespace by using a nested import in Less (http://stackoverflow.com/questions/19793508/compiling-issue-in-bootstrap-3-with-namespace).
We need to add a Gulp step to precompile Bootstrap (using our variables), and then drop it into the import within the
.labkingclass.