Closed Bug 875299 Opened 12 years ago Closed 11 years ago

Rename Promise.catch() to something else

Categories

(Core :: DOM: Core & HTML, defect)

Product:
Core
Component:
DOM: Core & HTML
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: mounir, Unassigned)

References

Details

Future.catch() has the problem of using an EcmaScript reserved name and old browsers will not enjoy that. This is the same probleme with .delete() in IDB. Developers have to do idb['delete']() to be able to have the code parsed (not even executed) in all browsers. Might be a pain if developers have to do that with catch.
'fail', like in the Q library?
Anne, can you give a feedback about this?
Flags: needinfo?(annevk)
This ground has been covered in the spec discussion. ES5 happened, we're gonna use the terms that make the most sense.
Status: NEW → RESOLVED
Closed: 12 years ago
Flags: needinfo?(annevk)
Resolution: --- → WONTFIX
Please, keep this bug open until the discussion happened in a public place.
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Summary: Rename Future.catch() to something else → Rename Promise.catch() to something else
I don't think this is what we want. Do we really want to rename catch() ?
Flags: needinfo?(annevk)
No. (And to address comment 4, this discussion did happen in a public place.)
Status: REOPENED → RESOLVED
Closed: 12 years ago → 11 years ago
Flags: needinfo?(annevk)
Resolution: --- → WONTFIX
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.