Closed
Bug 624562
Opened 14 years ago
Closed 14 years ago
The notifications API should warn and use the default icon when an invalid iconURL is given
Categories
(Add-on SDK Graveyard :: General, defect)
Add-on SDK Graveyard
General
Tracking
(Not tracked)
RESOLVED
FIXED
1.0b2
People
(Reporter: adw, Assigned: adw)
Details
Attachments
(1 file)
1.39 KB,
patch
|
myk
:
review+
|
Details | Diff | Splinter Review |
bsterne had a problem where the URL returned from self.data.url was wrong, and passing that URL as the iconURL to the notifications API gave him this unhelpful error rather than showing the notification: [Exception... "Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIAlertsService.showAlertNotification]" nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame :: resource://jid0-qjdoz32n3dcx6vs5qztj6sfouq8-jetpack-core-lib/securable-module.js -> resource://jid0-qjdoz32n3dcx6vs5qztj6sfouq8-jetpack-core-lib/notifications.js :: notifications_notify :: line 58" data: no] He could have just as easily made a simple typo in the filename. If the iconURL is invalid, the user should get a helpful warning, the notification should happen, and the default icon should be used.
Attachment #502637 -
Flags: review?(myk)
Updated•14 years ago
|
Attachment #502637 -
Flags: review?(myk) → review+
Assignee | ||
Comment 1•14 years ago
|
||
Thanks for the quick review. https://github.com/mozilla/addon-sdk/commit/6dbaafa464741974326af4cd6ce36a97e6f11ffa
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Target Milestone: --- → 1.0b2
You need to log in
before you can comment on or make changes to this bug.
Description
•