horizon.messages for table action allowed() calls does not display at the correct time
Bug #1463050 reported by
Eric Peterson
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Dashboard (Horizon) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Seeing that the table action allowed() call (for a table action, not a row action) has an exception / error - and then makes a call to the horizon messages.warning() api. The actual error is not showing until the subsequent page load call. This makes it look like the actual error is on the wrong page.
| tags: | added: ops |
| tags: | added: error-reporting |
Revision history for this message
| Eric Peterson (ericpeterson-l) wrote | #1 |
To post a comment you must log in.
I believe this is ocuring because the {{ table.render }} call occurs in the body of the html doc rendering, and the rendering for the messages occurs at the beginning of the document.
By the time the error and messaging occurs - the change to present this to end users is gone.
One possible solution is to move the messages to the bottom of the doc.