Open
Bug 1632270
Opened 4 years ago
Updated 4 years ago
unhandledrejection doesn't work correctly in content scripts
Categories
(Core :: DOM: Core & HTML, defect, P3)
Tracking
()
UNCONFIRMED
People
(Reporter: miika9764, Unassigned, NeedInfo)
Details
Attachments
(1 file)
|
1.83 KB,
application/zip
|
Details |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:75.0) Gecko/20100101 Firefox/75.0
Steps to reproduce:
- Installed the extension in the ext directory at https://github.com/siikamiika/firefox-unhandledrejection-addon-bug
- Opened index.html in the page directory
- Clicked the "Trigger unhandledrejection" and "Trigger unhandledrejection from extension" buttons
Actual results:
Got the alert
"Caught unhandledrejection in extension: ReferenceError: somethingStupid is not defined"
and the text
"Received unhandledrejection: ReferenceError: somethingStupid is not defined"
to the page when clicking "Trigger unhandledrejection", but nothing from the "Trigger unhandledrejection from extension" button.
Expected results:
I shouldn't have gotten an alert from the first button, and the second button should have alerted "Caught unhandledrejection in extension: unhandledrejection from extension". For example Chrome behaves this way.
|
||
Updated•4 years ago
|
Component: Untriaged → DOM: Core & HTML
Product: Firefox → Core
|
||
Updated•4 years ago
|
Flags: needinfo?(echen)
|
||
Updated•4 years ago
|
Severity: normal → S3
Priority: -- → P3
You need to log in
before you can comment on or make changes to this bug.
Description
•