| 2006-06-06 06:06:05 |
Stuart Bishop |
bug |
|
|
added bug |
| 2007-04-17 15:34:10 |
Diogo Matsubara |
launchpad: status |
Unconfirmed |
Confirmed |
|
| 2007-04-17 15:34:10 |
Diogo Matsubara |
launchpad: statusexplanation |
|
|
|
| 2007-04-17 15:37:09 |
Diogo Matsubara |
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.
affects /products/launchpad
--
Stuart Bishop <stuart.bishop@canonical.com> http://www.canonical.com/
Canonical Ltd. http://www.ubuntu.com/
|
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.
|
|
| 2011-05-12 23:15:04 |
Robert Collins |
summary |
BrowserNotifications are displayed on the oops page |
BrowserNotifications are not transactional (retries generate multiple notifications, oops still generate notifications) |
|
| 2011-05-12 23:15:07 |
Robert Collins |
launchpad: importance |
Medium |
High |
|
| 2011-05-30 08:05:43 |
William Grant |
removed subscriber Canonical Launchpad Engineering |
|
|
|
