Closed
Bug 928153
Opened 11 years ago
Closed 10 years ago
Trying to close a notification that no longer displays should fire onerror on the notification object
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: jsmith, Unassigned)
References
Details
(Whiteboard: [systemsfe])
STR
1. Go to http://mozilla.github.io/qa-testcase-data/webapi/notifications/
2. Select show notification
3. Provide an index of 0 and hit close under close notification
4. Hit close again
5. Check the console log
Expected
When close is called on a notification that no longer exists, onerror should fire.
Actual
No developer visible error is fired.
Reporter | ||
Updated•11 years ago
|
Whiteboard: [systemsfe]
Reporter | ||
Updated•11 years ago
|
Blocks: b2g-notifications
Comment 1•10 years ago
|
||
AFAICT, the spec doesn't mention anything about closing a closed notification firing onerror. Anne?
Flags: needinfo?(annevk)
Comment 2•10 years ago
|
||
Correct. At most we could show something in developer tools.
Flags: needinfo?(annevk)
Comment 3•10 years ago
|
||
Closing as invalid as per comment 2.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
Assignee | ||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•