Actions
Bug #541
closed
AJAX calls don't fail when a connection to the server cannot be made
Status:
Rejected
Priority:
5 (lowest)
Assignee:
-
Category:
Web - UI & UX
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
I saw this on E03 "Server groups" page, but it may be more widely-spread.
Once the page is displayed, and I have clicked "Create a new group", changing search criteria and clicking on "Search" display a rotating wheel for a few seconds, then the wheel disappears, but no update has happened. The page can get into a bad state (for example, selecting criterion "RAM" and you can then choose "=Linux" as a value :) ).
Of course, an error message should be displayed if the server couldn't be contacted. Then, maybe grey out appropriate form elements, and add a "Retry" button?
Updated by Jonathan CLARKE about 14 years ago
- Priority changed from 2 to 5 (lowest)
Updated by Jonathan CLARKE almost 14 years ago
- Category changed from 13 to Web - UI & UX
Updated by Jonathan CLARKE almost 14 years ago
- Target version changed from 6 to 8
Updated by Jonathan CLARKE over 12 years ago
- Target version changed from 24 to 18
Updated by Jonathan CLARKE about 12 years ago
- Target version changed from 18 to Ideas (not version specific)
Updated by François ARMAND almost 10 years ago
- Status changed from New to Rejected
We now have a "server can not be contacted at this time" error when Ajax fails - actually, even when it's due to an error in the returned JS.
So closing that one.
Actions