Page MenuHomePhabricator

Visiting Special:Notifications should not mark notifications as read
Closed, ResolvedPublic

Description

At mediawiki.org, I clicked the Notifications growler before the page had finished loading, and was taken to Special:Notifications (expected).
However, that marked all 15 of my new Notifications as read (unexpected).

Event Timeline

Quiddity raised the priority of this task from to Needs Triage.
Quiddity updated the task description. (Show Details)
Quiddity subscribed.
Quiddity set Security to None.

Solution is probably to implement T96061: Add a "Mark all as read" button at Special:Notifications for no-JS users and this task together. We probably don't need to implement a way to mark individual messages read one-by-one (at least we don't have to implement this immediately); people can still mark individual messages as read automatically by going to the topic.

Quiddity renamed this task from Visiting Special:Notifications marks all Flow messages as read to Visiting Special:Notifications should not mark all Flow messages as read.May 12 2015, 9:32 PM

This is also relevant to the LQT->Flow conversion, since LQT has more of an inbox metaphor and it seems people tend to keep a lot of new messages (partly because LQT is not good about marking them as read automatically).

This is addressed in https://gerrit.wikimedia.org/r/#/c/276256/ which added 'mark as read' button to notifications in the no-JS version of the special page, and also removes the auto-mark-as-read feature.

Mattflaschen-WMF renamed this task from Visiting Special:Notifications should not mark all Flow messages as read to Visiting Special:Notifications should not mark notifications as read.Apr 27 2016, 8:51 PM

This is addressed in https://gerrit.wikimedia.org/r/#/c/276256/ which added 'mark as read' button to notifications in the no-JS version of the special page, and also removes the auto-mark-as-read feature.

Solved then?