Type: New Feature
Status: Closed (View Workflow)
Resolution: Cannot Reproduce
Affects Version/s: None
Fix Version/s: None
I finally have an, I think, coherent overall idea of how we might make the in-pane grid system work on various screen sizes, and behave consistently usable with customizable pane widths and fly-out pane logic:
Rather than our components—and app developers' own components—using css media queries to turn e.g. a multi-col table into a cards list, or to change layout different, here is what I propose:
This way, the code would not need to be read in runtime, the layout of items and components would not depend on the overall screen width when components are confined actually to part-width-panes, and it is a quite similar technique to styling for media queries (syntax wise).
The only challenge I can see with this is that it does not follow along well with the notion of completely splitting up CSS code into components. We do have some global styles, but I don't know if this is problematic for one reason or another.