Last modified: 2014-04-16 18:22:10 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T34284, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 32284 - Update Echo Notifications in real time without page reloads
Update Echo Notifications in real time without page reloads
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
Echo (Other open bugs)
unspecified
All All
: High enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
: 59879 (view as bug list)
Depends on: 32283
Blocks: 32281
  Show dependency treegraph
 
Reported: 2011-11-08 21:09 UTC by Brion Vibber
Modified: 2014-04-16 18:22 UTC (History)
6 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Brion Vibber 2011-11-08 21:09:34 UTC
Classic 'new message' notifications about your talk page or LQT only show up when refreshing a page.

Polling the web API every couple minutes could be nice, especially if things like RecentChanges turn into more interactive pages that will be long-running.
Comment 1 Andre Klapper 2014-02-15 14:02:32 UTC
Brion: Is this ticket Echo territory nowadays? Should this be moved, or can this be considered closed?
Comment 2 Brion Vibber 2014-02-16 17:38:19 UTC
Sounds like Echo territory for implementation -- has this been implemented in Echo, or is it still something that needs doing?
Comment 3 Andre Klapper 2014-02-25 16:34:29 UTC
Not sure if that's implemented already, but if it was it would be Echo territory. Hence moving there. Might require fixing bug 32283 first...
Comment 4 Quiddity 2014-02-25 18:49:43 UTC
See also bug 59879 (probably a duplicate?), particularly comment1 by legoktm
Comment 5 Jared Zimmerman (WMF) 2014-04-14 23:09:17 UTC
This is inconsistent with other sites where notification are shown in real-time, or at least while the user is on the page rather than leaving or explicitly reloading the page.
Comment 6 Jared Zimmerman (WMF) 2014-04-14 23:09:51 UTC
*** Bug 59879 has been marked as a duplicate of this bug. ***
Comment 7 Kunal Mehta (Legoktm) 2014-04-16 06:19:58 UTC
I put together a POC at I8f7bc77d05762fd12927437f6450ae3f97eb84af.

It simply polls the API every 60 seconds to check for new notifications (it kinda but not really works).

That said, I don't think polling is a good idea. We should instead have some kind of websockets service pushing notifications to the user/browser. This might line up well with [[mw:Requests for comment/Publishing the RecentChanges feed]].
Comment 8 Jared Zimmerman (WMF) 2014-04-16 18:22:10 UTC
Kunal, sounds like a reasonable stopgap measure fix, as you said there are better ways to do it, How would you feel about increasing the polling frequency but tying it to an activity timer, associated with page scrolling or mouse movement, e.g. we poll at a higher frequency while we know the user is interacting with the page, and stop polling or poll much more infrequently when no activity is detected. Quora uses a similar approach.

Another metric of, is the user looking at the page could be a mixture of Page Visibility API https://developer.mozilla.org/en-US/docs/Web/Guide/User_experience/Using_the_Page_Visibility_API#Use_cases and window focus and blur for older browsers compatibility. http://stackoverflow.com/questions/14309596/detecting-when-browser-window-tab-is-not-in-the-foreground

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links