Closed emanuil-tolev closed 7 years ago
Note, this is on IE11.
Probably nothing we can do about that. The polling does work, and if they are seeing any poll count at all it must be working for them, but at any point a user could lose connection for a multitude of reasons. If it is a long running job, the polling could fail at some point and yes they would have to refresh. We could force a page refresh on poll fail, but then some browsers will consider a page refresh to be a bad behaviour that they will warn the user for.
On Tue, Aug 23, 2016 at 1:29 PM, Emanuil Tolev notifications@github.com wrote:
Note, this is on IE11.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/CottageLabs/LanternPM/issues/116#issuecomment-241714867, or mute the thread https://github.com/notifications/unsubscribe-auth/AAuXCA4fjkLWp-wCWyKaVc6g4c3Rrn4Lks5qiueogaJpZM4Jq3Z_ .
You know, gmail and Trello (to take 2) display a bit of text just saying the page you're looking at is out of date, and that you should refresh. This would solve the problem, since the actual problem is not so much one of robust progress polling, but user confusion where the user believes the page is up to date, but it actually isn't. Could we do that relatively simply in the AJAX fail handler?
Probably.
On Tue, Aug 23, 2016 at 8:54 PM, Emanuil Tolev notifications@github.com wrote:
You know, gmail and Trello (to take 2) display a bit of text just saying the page you're looking at is out of date, and that you should refresh. This would solve the problem, since the actual problem is not so much one of robust progress polling, but user confusion where the user believes the page is up to date, but it actually isn't. Could we do that relatively simply in the AJAX fail handler?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/CottageLabs/LanternPM/issues/116#issuecomment-241855838, or mute the thread https://github.com/notifications/unsubscribe-auth/AAuXCEO7g_W6d_N2laSpeddN9wAE_3fLks5qi0_agaJpZM4Jq3Z_ .
Take into account in new site design
after a bit of discussion, we think this is hard/impossible to solve, so closing off unless it becomes an issue again
Got a report (wellcome UI):