BrowserNotifications are not transactional (retries generate multiple notifications, oops still generate notifications)

Bug #48621 reported by Stuart Bishop
2
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
High
Unassigned

Bug Description

Notifications set using the BrowserNotifications API are being displayed on
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
Revision history for this message
Robert Collins (lifeless) wrote :

I'm marking this high but perhaps it should be wontfix.

summary: - BrowserNotifications are displayed on the oops page
+ BrowserNotifications are not transactional (retries generate multiple
+ notifications, oops still generate notifications)
Changed in launchpad:
importance: Medium → High
Revision history for this message
Robert Collins (lifeless) wrote :

Retries could zap the notifications they added - it should be fairly easy to address.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.