webstaff: remove statusbar, move Hatch connection indicator to hamburger menu
Bug #1564508 reported by
Galen Charlton
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
The browser client has a status bar that is currently hidden. It supports the following features:
- notification system
- websockets connection status indicator
- Hatch status indicator
The notification system has been supplanted by toasts from ngToast. However, since having an indication of whether Hatch is connected or not would be handy, I suggest:
- removing the status bar
- adding a Hatch connection status indicator to the hamburger menu
- optionally adding a websockets connection status indicator to the hamburger menu
Changed in evergreen: | |
milestone: | 3.next → 3.0-alpha |
Changed in evergreen: | |
assignee: | nobody → Bill Erickson (berick) |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
http:// git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ berick/ lp1564508- hatch-status- hamburger
From the commit:
* Move the Hatch connectivity status indicator into the upper-right hamburger menu.
* Removes the long-hidden hatch/websockets statusbar.
* Since the Hamburger forces a re-digest of the interface when opened, the code no longer attempts to force the page to re-$apply() when the Hatch connection opens or closes. It's no longer necessary (and was buggy).
* The WebSockets connectivity status is not added to the hamburger. The websockets connection will go up and down regularly as connections expire and reset. Having the indicator flash could lead to unnecessary panic (IMO). Plus, if websockets are down, staff can't log in anyway.