Bug #3691

[Workbench] Suppress "ajax failed" error messages when ajax fails due to browser navigation event.

Added by Tom Clegg almost 5 years ago. Updated over 4 years ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
Workbench
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Story points:
1.0

Description

In fail callbacks, check jqxhr.readyState and status == 'abort' to determine whether the request was terminated by a user action (like navigating away from the current page) rather than an application/network error.

In this case, correct behavior is something like
  • Show a distinct message like "(cancelled)" that doesn't look like an error, or
  • Don't display anything, just clean up internal state and stop.

Related issues

Has duplicate Arvados - Bug #4776: [Workbench] Pipeline pane load error when opening pipeline from home page in new browser tabClosed12/10/2014

History

#1 Updated by Tom Clegg almost 5 years ago

  • Description updated (diff)
  • Category set to Workbench

#2 Updated by Tom Clegg almost 5 years ago

  • Description updated (diff)

#3 Updated by Brett Smith over 4 years ago

  • Target version set to Bug Triage

#4 Updated by Brett Smith over 4 years ago

#4776 illustrates a case where it would be preferable to just clean up, rather than displaying a more-specific error.

#5 Updated by Tom Clegg over 4 years ago

  • Story points changed from 0.5 to 1.0

#6 Updated by Tom Clegg over 4 years ago

  • Target version changed from Bug Triage to 2015-02-18 sprint

#7 Updated by Tom Clegg over 4 years ago

  • Target version changed from 2015-02-18 sprint to Arvados Future Sprints

Also available in: Atom PDF