Page MenuHomePhabricator

VisualEditor should handle connections dying more gracefully (and not cache errors)
Open, LowPublic

Description

In T173858: Unable to save changes, a user experienced very strange behaviour when their connection died during editing. Although we can't fix the user's connection, we can at least fail more gracefully and in a more obvious way to the user.

Event Timeline

Deskana created this task.Aug 22 2017, 7:32 PM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptAug 22 2017, 7:32 PM
Deskana triaged this task as Low priority.Aug 22 2017, 7:32 PM
Deskana moved this task from To Triage to Freezer on the VisualEditor board.
Deskana renamed this task from VisualEditor should handle connections dying more gracefully to VisualEditor should handle connections dying more gracefully (and not cache errors).Nov 7 2017, 1:02 PM
Deskana added a subscriber: jberkel.

Would just like to add that it's not just dying connections, but all sorts of backend errors (timeouts etc). Anyway, I've been hitting this bug more frequently recently.