Closed Bug 381498 Opened 17 years ago Closed 17 years ago

Resolve mechanism for how setting default mime type handlers works

Categories

(Developer Documentation Graveyard :: General, defect)

Product:
Developer Documentation Graveyard
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 372441

People

(Reporter: baz, Assigned: sheppy)

References

Details

We should help clarify to extension and website developers how setting default MIME type handlers works in Firefox 3. Do we recommend a user prompt? (like resetting the home page via JS?) or should some other technique be used.
Flags: blocking-firefox3?
Depends on: 340333
Not sure what you're asking for here, Baz. Are you talking about adding a JS method for registering MIME type handlers? Or adding documentation to MDC? (clearing blocking flag, re-nom if you feel it needs to block release)
Flags: blocking-firefox3?
It's meant as a documentation bug - so moving it to Product: Documentation, Component: Extension and cc'ing Sheppy
Assignee: nobody → endico
Component: File Handling → Mozilla Developer
Product: Firefox → Documentation
QA Contact: file.handling → imajes
Target Milestone: Firefox 3 → ---
Version: Trunk → unspecified
Any advice where to look for the appropriate information on what should be said about this?
Assignee: endico → eshepherd
Once the feature is designed dmose should be able to help provide more details.
Is there a bug for the feature itself? If so, this should be dependent on that. Or, ideally, this should be closed and that bug tagged dev-doc-needed instead.
Component: Mozilla Developer → Documentation Requests
Product: Documentation → Mozilla Developer Center
QA Contact: imajes → doc-request
That's bug 372441; I've tagged that appropriately and marking this as a DUP of it.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
Component: Documentation Requests → Documentation
Component: Documentation → General
Product: Mozilla Developer Network → Developer Documentation
You need to log in before you can comment on or make changes to this bug.