Moriel Schottlender a7aae23806 Remove read item from counter after it was actually marked as read ... We removed the item first from the 'unread' counter and then told the API to mark it as read. The API, however, wisely first checks if there is anything *to* mark as read, but by that point, the unread count is zero, so it gracefully refuses and returns an empty resolved promise. That is clearly not the way to go. Remove the read item from its smart unread counter only **after** it was sent to the API to be marked as read. Note: We shouldn't wait for the API promise to resolve to remove the item from the counter, but the API should run its preliminary tests before the item is removed. Bug: T122087 Change-Id: Ia5fc35c7435db8c4742238897da67681cee23c41		2015-12-21 15:13:29 -08:00
..
handlers	Add OOUI widgets for cross-wiki bundled notifications	2015-12-14 17:22:34 -08:00
mw.echo.dm.js	Split alerts and messages in Echo	2015-09-02 15:36:37 -07:00
mw.echo.dm.List.js	Implement SortedList in Echo notifications	2015-11-06 11:01:10 -08:00
mw.echo.dm.NotificationGroupItem.js	Add OOUI widgets for cross-wiki bundled notifications	2015-12-14 17:22:34 -08:00
mw.echo.dm.NotificationItem.js	Add OOUI widgets for cross-wiki bundled notifications	2015-12-14 17:22:34 -08:00
mw.echo.dm.NotificationList.js	Split alerts and messages in Echo	2015-09-02 15:36:37 -07:00
mw.echo.dm.NotificationsModel.js	Remove read item from counter after it was actually marked as read	2015-12-21 15:13:29 -08:00
mw.echo.dm.SortedList.js	Implement SortedList in Echo notifications	2015-11-06 11:01:10 -08:00