Closed Bug 1587087 Opened 6 years ago Closed 5 years ago

Real bug with throw ?

Categories

(developer.mozilla.org Graveyard :: API, defect)

Product:
developer.mozilla.org Graveyard
Component:
API
Platform:
All
Other
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: montdm, Unassigned)

Details

(Whiteboard: [specification][type:bug])

What did you do?

1. I open the console
2. in javascript I use 'throw" to stop the execution with no catch.
3. 

What happened?

the console writes an error "uncaught exception"

What should have happened?

nothing (I mean, no error in the console)
in the documentation it is written :
"The throw statement throws a user-defined exception. Execution of the current function will stop (the statements after throw won't be executed), and control will be passed to the first catch block in the call stack. If no catch block exists among caller functions, the program will terminate."

  • if the documentation is good ("If no catch block exists among caller functions, the program will terminate") -> there is no error so the console should not say it is an error
  • if it is truly an error, the documentation should be changed : catch is necessary in all cases and the sentence in the documentation is an error

In both case, something is wrong

Is there anything else we should know?

MDN Web Docs' bug reporting has now moved to GitHub. From now on, please file content bugs at https://github.com/mdn/sprints/issues/ and platform bugs at https://github.com/mdn/kuma/issues/.
Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.