Open williballenthin opened 3 months ago
I'm on the fence if we want to support mobile (at least for now). Do we expect many users to explore capa results on their smartphone?
It sorta works right now but the width is the main issue. I hope that this change wouldn't require too much code, which is why I proposed it. Otherwise, I understand deprioritizing it.
When the browser window is narrow, such as on mobile, we should render the rule results table in a different way so that all information can easily be seen. Today, we put rule name, namespace, ATT&CK, etc. in their own column, which works well on a large display.
When the display is narrow, I think we could render the data like so:
Using bold/light and primary/muted colors to emphasize the rule name and de-emphasize the namespace/ATT&CK/MBC information. While this may make each list entry taller, it should still be easy to visually scan.
Ideally this is implemented via responsive CSS and media queries; however, if there's a dependency on the JS library, perhaps changes to the page width can be subscribed and responded to.