If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

explicit error-handling semantics

RESOLVED INVALID

Status

()

Toolkit
Safe Browsing
--
enhancement
RESOLVED INVALID
12 years ago
3 years ago

People

(Reporter: Fritz Schneider, Unassigned)

Tracking

unspecified
Future
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

12 years ago
We need more consistent semantics for errors. What's the right way to flag them (return value or exceptions)? Who can throw what kind of errors? Who can catch exceptions and how (e.g., can we have naked exception handlers)?

Updated

12 years ago
QA Contact: nobody → safe.browsing

Updated

9 years ago
Target Milestone: --- → Future
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → INVALID
(Assignee)

Updated

3 years ago
Component: Phishing Protection → Phishing Protection
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.