Add kiosk mode - #1970
Conversation
Test results 8 files 1 800 suites 3m 28s ⏱️ Results for commit 1b2d585. ♻️ This comment has been updated with latest results. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1970 +/- ##
==========================================
+ Coverage 88.62% 89.50% +0.87%
==========================================
Files 149 152 +3
Lines 7185 7296 +111
==========================================
+ Hits 6368 6530 +162
+ Misses 817 766 -51 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
e2b2244 to
28a973e
Compare
Co-authored-by: Hanne Moa <hanne.moa@sikt.no>
There was a problem hiding this comment.
Kiosk mode sure doesn't look much different than just collapsing the filters, which was already possible - only detectable difference for me is that the footer line is removed and its filter summary moved to the filter row instead (and that isn't very space-saving - at worst, the footer would have just been pushed outside of the viewport in a long incident list)
I think I would prefer an even more minimal kiosk mode, perhaps pushing the "details" to the blue argus navbar instead. Likely the only thing needed in kiosk mode is to print the name of the selected filter, and the timestamp of the last update. But these are just opinions - I think this kiosk mode should be demoed to our NOC to get some actual user feedback.
One potential show-stopper in the details, thoug...
There was a problem hiding this comment.
Works, but I can only know that the kiosk-mode does something by hovering.
I have suggested adding "link", but we could also decide on never using btn-ghost.
There was a discussion at the accessibility group's latest meeting about invisible buttons. Common, but inaccessible. Ditto hiding the link underline. We have the much slopped #1985 which is about the same problem but in other parts of the dashboard.
Another possibility is having a two-pixel border around such buttons (also including the "special filters"-one, but that would have to be fixed in a different PR).
Agreed. |
Co-authored-by: Hanne Moa <hanne.moa@sikt.no>
de848a8 to
30d8d9b
Compare
|
Look/feel is approved. |
|
Follow-up: how to highlight links in general, what to do with buttons of little importance (like "special filters" in filter box), with updated style guide. |
|
@hmpf @lunkwill42 Current version has been reworked to be even more minimal, I ran a live demo with the NOC and they preferred this version to their previous suggestion. Happy to get feedback on the code now, since the changes have been quite extensive to facilitate the rework. |
Co-authored-by: Johanna England <johanna.england@sikt.no>
|
| {% include "htmx/incident/_filter_controls.html" %} | ||
| <div id="filterbox" class="flex flex-wrap items-center basis-full"> | ||
| {% include "htmx/incident/_incident_filterbox.html" %} | ||
| {% if not kiosk_mode %} |
There was a problem hiding this comment.
Follow-up: All of these "if/if not kiosk_mode" in the templates when the opposite is nothing, it is tempting to break the contents out as either an independent fragment or as a partial in the same file.
The latter is available from Django 6.0+ so let's not do anything until we upgrade our minimum supported version.
hmpf
left a comment
There was a problem hiding this comment.
The header in the kiosk mode looks the same if:
- No filters have been set
- No named filter has been chosen
- A filter has been set but not saved
It always says "Filter: None".
I would prefer that in case 1 it says "Unset" (or just remove the entirety of "Filter: None"), in case 2 it says "None" and in case 3 it says "Unsaved". If the total number of incidents is always shown in addition to "After filtering: " I would at least know if any filters are in place but altering what's after "Filter:" is more explicit.



Scope and purpose
Fixes #1938 .
Before:

After:

Adds some extra tests to pad the coverage.
Contributor Checklist
Every pull request should have this checklist filled out, no matter how small it is.
More information about contributing to Argus can be found in the
Development docs.