The default bug view has changed. See this FAQ.

Use Components.results.NS_BINDING_ABORTED instead of hardcoding the value

RESOLVED FIXED in mozilla17

Status

()

Core
General
--
minor
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: philor, Assigned: philor)

Tracking

Trunk
mozilla17
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

5 years ago
Created attachment 653019 [details] [diff] [review]
fix

+++ This bug was initially created as a clone of Bug #454360 +++

Since bug 418406 was nice enough to expose network error constants in Components.results back in 2008, we made use of them rather than hardcoding 0x804b0002 all over the place in JS...

but that's the sort of thing that creeps back in, from people remembering all the years before 2008 instead of the years after it.

https://tbpl.mozilla.org/?tree=Try&rev=ee0aa78db209
Attachment #653019 - Flags: review?(gavin.sharp)
Comment on attachment 653019 [details] [diff] [review]
fix

Cr is defined in all of the test files, you could use it
Attachment #653019 - Flags: review?(gavin.sharp) → review+
(Assignee)

Comment 2

5 years ago
I did consider using Cr, but it's freshly defined from a tree-wide change, nothing else in the files uses any of the C*s, so using just one down in the middle is a bit risky, and changing them all seemed both intrusive and likely to bring down the wrath of someone with a superstition about not using them.

https://hg.mozilla.org/integration/mozilla-inbound/rev/d11657f18f85
https://hg.mozilla.org/mozilla-central/rev/d11657f18f85
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla17
You need to log in before you can comment on or make changes to this bug.