When calling AskPermission, on desktop we call into nsBrowserGlue.js, where nsContentPermissionPrompt's prompt function is implemented. However, we don't actually check for exceptions after prompt is called, meaning that things like i18n/l10n failures just throw to stderr and are hard to discern. It'd be nice to be able to actually propagate errors so we can possibly catch prompt problems in mochitests.
Attachment #8637420 - Flags: review?(fabrice) → review+
Component: DOM → DOM: Core & HTML
Product: Core → Core
You need to log in before you can comment on or make changes to this bug.