The Notification Page allows to filter by reading status (all, read, unread). When users change from one status to another, the control becomes disabled (as captured below) for a moment conveying unnecessary the need to wait and making the selected status to disappear for few seconds.
| Project | Branch | Lines +/- | Subject | |
|---|---|---|---|---|
| mediawiki/extensions/Echo | master | +94 -6 | Add a PromisePrioritizer and use it for notifications fetching |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T119713 Update Help:Notifications | |||
| Open | None | T114351 Better organisation for the Notification System | |||
| Open | None | T115316 Better organisation of the Notification Page | |||
| Open | None | T136567 Design adjustments for the Notifications Page | |||
| Resolved | Mooeypoo | T136895 Status filter should not become disabled between status change in the Notification Page |
Change 295565 had a related patch set uploaded (by Mooeypoo):
Add a PromisePrioritizer and use it for notifications fetching
Change 295565 merged by jenkins-bot:
Add a PromisePrioritizer and use it for notifications fetching
Checked the fix in betalabs - the selected status is clearly communicated to user while the page is loading.
