necko progress "status" codes need not be errors

NEW
Unassigned

Status

()

Core
Networking
P5
normal
16 years ago
4 months ago

People

(Reporter: Darin Fisher, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [necko-would-take])

(Reporter)

Description

16 years ago
necko progress "status" codes need not be errors.

for example, NS_NET_STATUS_RESOLVING_HOST is defined as:

#define NS_NET_STATUS_RESOLVING_HOST \
    NS_ERROR_GENERATE_FAILURE(NS_ERROR_MODULE_NETWORK, 3)

but should really be defined as:

#define NS_NET_STATUS_RESOLVING_HOST \
    NS_ERROR_GENERATE_SUCCESS(NS_ERROR_MODULE_NETWORK, 3)

having these defined as errors causes problems for nsIWebProgressListener::
onStateChange impls, which need to distinguish progress status from actual errors.
(Reporter)

Updated

16 years ago
Target Milestone: --- → mozilla1.1beta
(Reporter)

Updated

16 years ago
Target Milestone: mozilla1.1beta → ---
(Reporter)

Comment 1

16 years ago
mass futuring of untargeted bugs
Target Milestone: --- → Future
(Reporter)

Comment 2

12 years ago
-> default owner
Assignee: darin → nobody
QA Contact: benc → networking
Target Milestone: Future → ---
Whiteboard: [necko-would-take]
You need to log in before you can comment on or make changes to this bug.