Open Bug 307870 Opened 20 years ago Updated 3 years ago

Document when nsIChannel::contentType is available

Categories

(Core :: Networking, enhancement, P3)

enhancement

Tracking

()

People

(Reporter: Biesinger, Unassigned)

References

()

Details

(Keywords: good-first-bug, Whiteboard: [necko-backlog])

Currently, nsIChannel.idl avoids the question when the contentType is available. It also does not say what happens if the type is not known. It should document that the type is available in and after onStartRequest (or after open()). I'm not sure what we do for an unknown type, I think we may return "application/x-unknown-type" or somesuch...
Flags: blocking1.9a1?
Assignee: darin → nobody
QA Contact: benc → networking
Flags: blocking1.9a1? → blocking1.9-
Whiteboard: [wanted-1.9]
Flags: wanted1.9+
Whiteboard: [wanted-1.9]
Whiteboard: [necko-backlog][good first bug]
Priority: -- → P1
Priority: P1 → P3
Keywords: good-first-bug
Whiteboard: [necko-backlog][good first bug] → [necko-backlog]

(In reply to Christian :Biesinger (don't email me, ping me on IRC) from comment #0)

Currently, nsIChannel.idl avoids the question when the contentType is
available.
It also does not say what happens if the type is not known.

It should document that the type is available in and after onStartRequest (or
after open()). I'm not sure what we do for an unknown type, I think we may
return "application/x-unknown-type" or somesuch...

Hey!
Can I take this up! Would be great if you could guide me more on this!
Thanks :)

Thanks for the offer! I'll have to defer to Patrick on the current status here, I haven't been involved in years.

Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.