Closed Bug 71053 Opened 24 years ago Closed 24 years ago

nsIProtocolHandler needs cleanup.

Categories

(Core :: Networking, defect, P2)

All
Linux
defect

Tracking

()

VERIFIED FIXED
mozilla0.9

People

(Reporter: jud, Assigned: dougt)

References

()

Details

(Keywords: embed)

1. nsILoadGroup and nsIInterfaceRequestor pre-defs need to be removed. 2. if not a socket using handler, the return code of defaultPort needs to be defined as -1, and documented in comments. 3. baseURI in newURI() method needs to be documented that it can take null.
Blocks: 70229
Accepting per API review
Severity: normal → major
Status: NEW → ASSIGNED
Component: Embedding APIs → Networking
Keywords: embed
Priority: -- → P2
Hardware: PC → All
Target Milestone: --- → mozilla0.9
Checked into the tree.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
re-opening. doug, if you'll recall our email exchange involved leaving this open. Please review the api notes for more info.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
I thought that we were talking about leaving 71054 open. Please confirm.
my bad. you're right.
Status: REOPENED → RESOLVED
Closed: 24 years ago24 years ago
Resolution: --- → FIXED
reassign qa contact to depstein.
QA Contact: mdunn → depstein
in nsIProtocolHandler.idl: 1. No nsILoadGroup or nsIInterfaceRequestor pre-defs 2. there's a comment about -1 being the default for abnormal port. (Q: In what file is -1 default actually defined?) 3. in newURI(), there's a comment about aBaseURI possibly being nsnull.
verified
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.