Closed
Bug 289981
Opened 20 years ago
Closed 20 years ago
nsBrowserContentHandler.js has wrong constant for NS_BINDING_ABORTED
Categories
(Firefox :: General, defect, P5)
Tracking
()
RESOLVED
FIXED
Firefox 2 alpha1
People
(Reporter: Biesinger, Assigned: Gavin)
References
()
Details
(Keywords: fixed1.8.1)
Attachments
(1 file)
|
783 bytes,
patch
|
benjamin
:
review+
|
Details | Diff | Splinter Review |
62 const NS_BINDING_ABORTED = 0x80020006;
but NS_BINDING_ABORTED is really 0x804b0002
Updated•20 years ago
|
Assignee: firefox → mconnor
| Assignee | ||
Updated•20 years ago
|
Assignee: mconnor → gavin.sharp
OS: Linux → All
Hardware: PC → All
Summary: browser.js has wrong constant for NS_BINDING_ABORTED → nsBrowserContentHandler.js has wrong constant for NS_BINDING_ABORTED
Target Milestone: --- → Firefox1.6-
| Assignee | ||
Comment 1•20 years ago
|
||
Attachment #200652 -
Flags: review?(bugs.mano)
| Assignee | ||
Updated•20 years ago
|
Status: NEW → ASSIGNED
Comment 2•20 years ago
|
||
How do you know that the code really wants NS_BINDING_ABORTED? Does 0x80020006 correspond to some other defined error code that has specific meaning that some other module may care about?
| Assignee | ||
Comment 3•20 years ago
|
||
(In reply to comment #2)
> How do you know that the code really wants NS_BINDING_ABORTED? Does 0x80020006
> correspond to some other defined error code that has specific meaning that some
> other module may care about?
It's only used for the call to nsIRequest.cancel in nsIContentHandler's handleContent, given it's name I assumed it was a typo. In-tree, this function is never used, I don't know why this object implements nsIContentHandler.
Comment 4•20 years ago
|
||
The function *is* used in some cases where people are calling nsIURILoader to open URIs. I probably just expanded the macro incorrectly or something like that when I copied this code from the original C++
Comment 5•20 years ago
|
||
OK, sounds good.
| Assignee | ||
Updated•20 years ago
|
Whiteboard: [patch-r?]
| Assignee | ||
Updated•20 years ago
|
Priority: -- → P5
Updated•20 years ago
|
Attachment #200652 -
Flags: review?(bugs.mano) → review?(benjamin)
Updated•20 years ago
|
Attachment #200652 -
Flags: review?(benjamin) → review+
| Assignee | ||
Updated•20 years ago
|
Whiteboard: [patch-r?]
| Assignee | ||
Comment 6•20 years ago
|
||
mozilla/browser/components/nsBrowserContentHandler.js; new revision: 1.18;
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Updated•20 years ago
|
Flags: blocking-aviary2?
Comment 7•20 years ago
|
||
Mano, why would this block anything? Does this code bug actually affect anything visible?
| Assignee | ||
Comment 9•19 years ago
|
||
mozilla/browser/components/nsBrowserContentHandler.js 1.12.2.8
Keywords: fixed1.8.1
Version: Trunk → 2.0 Branch
| Assignee | ||
Updated•19 years ago
|
Target Milestone: Firefox 2 → Firefox 2 alpha1
You need to log in
before you can comment on or make changes to this bug.
Description
•