Confirm
2,615
edits
Changes
no edit summary
= Status =
;Feature tracking bug
* {{bug|372949}}
* ''any other high-level tracking bugs can be listed here''
''Any relevant status comments for the feature can be placed here.''
= Overview =
Streamline and extend the handling of MIME content on the web.
== Motivation ==
Our current MIME-type handling has some rough edges that needs to be cleaned up. Additionally, more and more people are using web-applications as their primary way to handle specific types of content (e.g. calendar, mail). It should be possible for web sites to register content-handlers for types other than just RSS.
== Use Cases ==
* dynamic handoff
** subscribe to an ICS calendar in a web calendar application
** properly hand off streaming content (music, video) to a local or embedded player
* static handoff
** take an event in an ICS file generated by evite and insert it into a web calendar
** allow a website to render an Excel spreadsheet into HTML in an iframe
** hand off a mailto: URL to a web mail app for composition
== Requirements ==
* CON-001a P1 FR Support web services as MIME type handlers
* CON-001b P2 FR Minimize/remove local MIME type database for local applications
* CON-001c P3 FR Properly handle streaming content types - embedded or handed off to a helper app
== Schedule ==
''Describe the rough schedule here, linking back to relevant product release milestones, as well as linking to any build/release notes.''
= Design & Implementation =
;Documentation
* [[/User Interface|User Interface]]
* [[/Architecture|Architecture]]
* [[/Test Plan|Test Plan]]
;Repository
:''Indicate where the code for the feature lives (in branch or as extension).''
== API Changes ==
''list any API changes made by this feature.''
== Extensibility ==
''list work done to make feature extensible by add-ons & any impact to extensibility of Firefox''
== Customization ==
''list changes to preferences and customization controls for the feature''
== Performance ==
''list effects on performance, tests used, metrics targeted''
== Reliability/Stability ==
''list effects on reliability/stability, tests used, metrics targeted''
== Security ==
''list security impact and link to results of security reviews''
== Privacy ==
''list privacy impacts and any tie-ins to user privacy features''
== Global Audience ==
''list l10n requirements and a11y efforts''
== Web Compatibility ==
''list any known effects on compatibility with websites''
== Other ==
''any other implementation or design related documentation''
= Discussion & Implications =
== Caveats / What We've Tried Before ==
''links to previous design documents, discussions, etc.''
== References ==
''links to external documents that could inform the design of the feature''
;Feature tracking bug
* {{bug|372949}}
* ''any other high-level tracking bugs can be listed here''
''Any relevant status comments for the feature can be placed here.''
= Overview =
Streamline and extend the handling of MIME content on the web.
== Motivation ==
Our current MIME-type handling has some rough edges that needs to be cleaned up. Additionally, more and more people are using web-applications as their primary way to handle specific types of content (e.g. calendar, mail). It should be possible for web sites to register content-handlers for types other than just RSS.
== Use Cases ==
* dynamic handoff
** subscribe to an ICS calendar in a web calendar application
** properly hand off streaming content (music, video) to a local or embedded player
* static handoff
** take an event in an ICS file generated by evite and insert it into a web calendar
** allow a website to render an Excel spreadsheet into HTML in an iframe
** hand off a mailto: URL to a web mail app for composition
== Requirements ==
* CON-001a P1 FR Support web services as MIME type handlers
* CON-001b P2 FR Minimize/remove local MIME type database for local applications
* CON-001c P3 FR Properly handle streaming content types - embedded or handed off to a helper app
== Schedule ==
''Describe the rough schedule here, linking back to relevant product release milestones, as well as linking to any build/release notes.''
= Design & Implementation =
;Documentation
* [[/User Interface|User Interface]]
* [[/Architecture|Architecture]]
* [[/Test Plan|Test Plan]]
;Repository
:''Indicate where the code for the feature lives (in branch or as extension).''
== API Changes ==
''list any API changes made by this feature.''
== Extensibility ==
''list work done to make feature extensible by add-ons & any impact to extensibility of Firefox''
== Customization ==
''list changes to preferences and customization controls for the feature''
== Performance ==
''list effects on performance, tests used, metrics targeted''
== Reliability/Stability ==
''list effects on reliability/stability, tests used, metrics targeted''
== Security ==
''list security impact and link to results of security reviews''
== Privacy ==
''list privacy impacts and any tie-ins to user privacy features''
== Global Audience ==
''list l10n requirements and a11y efforts''
== Web Compatibility ==
''list any known effects on compatibility with websites''
== Other ==
''any other implementation or design related documentation''
= Discussion & Implications =
== Caveats / What We've Tried Before ==
''links to previous design documents, discussions, etc.''
== References ==
''links to external documents that could inform the design of the feature''
