BrowserNotifications are not transactional (retries generate multiple notifications, oops still generate notifications)
Bug #48621 reported by
Stuart Bishop
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
High
|
Unassigned |
Bug Description
Notifications set using the BrowserNotifica
the OOPS pages if the notification happened to have been set before the
exception occurred. This leads to weird and confusing cases like an OOPS
page with an informational banner at the top saying something worked. This
could also cause false positives in page tests that check for the success
message but do no check for the HTTP status code.
Changed in launchpad: | |
status: | Unconfirmed → Confirmed |
description: | updated |
To post a comment you must log in.
I'm marking this high but perhaps it should be wontfix.