Closed Bug 1525845 Opened 6 years ago Closed 6 years ago

Firefox is not handling failures in promises properly

Categories

(Core :: JavaScript Engine, defect)

65 Branch
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1498775

People

(Reporter: dalius.dobravolskas, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:65.0) Gecko/20100101 Firefox/65.0

Steps to reproduce:

I do some React development. I have written simple application to illustrate the problem that disturbs my workflow from time to time and urges me to move to Chromium/Chrome because Chrome does not have this problem.

Here is application that has intended problem:
https://rlq6mxr28q.codesandbox.io/

Press F12: no error is reported in console. Here is source code https://codesandbox.io/s/rlq6mxr28q, error is in actions/actions.js line 10. Error was made to illustrate the problem.

Actual results:

Nothing has happened. I made development error and I don't know about it anything. In this case as developer I'm lucky as I don't get result and this way I know that my code has problem. However sometimes I get error and I don't even get to know why that happens.

Expected results:

Error should be reported at least in console. E.g. if you opened my example code in Chromium you would get following error in console:

Uncaught (in promise) TypeError: Cannot read property 'toString' of undefined
at eval (actions.js? [sm]:10)

fixed in 66

Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Component: Untriaged → JavaScript Engine
Product: Firefox → Core
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.