6
edits
WebAPI: Difference between revisions
adding link to MDN documentation in highlighted box
(Added links to about ten W3C standards) |
(adding link to MDN documentation in highlighted box) |
||
| (6 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
<div style="border: thick solid red; width: 50%; padding: 5px;"><em><center>Warning: Information on this page is mostly obsolete! Check the general [[Platform/Roadmap]] for up to date projects. Use [https://lists.mozilla.org/listinfo/dev-platform dev-platform] and [irc://irc.mozilla.org/developers #developers] or [irc://irc.mozilla.org/content #content] to get in touch. | |||
[https://developer.mozilla.org/en-US/docs/WebAPI See MDN documentation on WebAPI] | |||
</center></em></div> | |||
The Mozilla WebAPI team is pushing the envelope of the web to include --- and in places exceed --- the capabilities of competing stacks. | The Mozilla WebAPI team is pushing the envelope of the web to include --- and in places exceed --- the capabilities of competing stacks. | ||
| Line 512: | Line 517: | ||
| {{WebAPIPlatformAvailability|notImplemented|Android}} | | {{WebAPIPlatformAvailability|notImplemented|Android}} | ||
| {{WebAPIPlatformAvailability|certifiedOnly|B2G}} | | {{WebAPIPlatformAvailability|certifiedOnly|B2G}} | ||
|- | |||
| [[WebAPI/TVAPI|TV API]] | |||
| {{bug|998872}} | |||
| Allow apps to acquire the information from TV service providers as well as to manage the native TV hardwares (i.e. tuners). | |||
| Shipped in FxOS 2.2. But requires explicitly turning on the preference. <br> Standardization: [http://w3c.github.io/tvapi/spec/ W3C ED (TV Control API)] | |||
| {{WebAPIPlatformAvailability|notPlanned|Desktop}} | |||
| {{WebAPIPlatformAvailability|notPlanned|Android}} | |||
| {{WebAPIPlatformAvailability|certifiedOnly|B2G}} | |||
|- | |||
| [[WebAPI/PresentationAPI|Presentation API]] | |||
| {{bug|1184073}} {{bug|1184036}} | |||
| Enable web content to access external presentation-type displays and use them for presenting web content. | |||
| Shipped in FxOS 2.5 for receiver side. <br> Standardization: [http://www.w3.org/TR/presentation-api/ Presentation API] | |||
| {{WebAPIPlatformAvailability|notImplemented|Desktop}} | |||
| {{WebAPIPlatformAvailability|notImplemented|Android}} | |||
| {{WebAPIPlatformAvailability|privilegedAndCertified|B2G}} | |||
|} | |} | ||
| Line 544: | Line 565: | ||
Security will be a central aspect of all the APIs that we design. We wouldn't want any random webpage to be able to read the user's contact list, or able to issue arbitrary commands to any USB device which is hooked up to the user's computer. | Security will be a central aspect of all the APIs that we design. We wouldn't want any random webpage to be able to read the user's contact list, or able to issue arbitrary commands to any USB device which is hooked up to the user's computer. | ||
In some cases the solution will be to simply ask the user, like we do today for Geolocation for example. In other cases, where security implications are scarier or where describing the risk to the user is harder, we'll have to come up with better solutions. | In some cases the solution will be to simply ask the user, like we do today for Geolocation for example. In other cases, where security implications are scarier or where describing the risk to the user is harder, we'll have to come up with better solutions. For example, enumerating sensitive information or exposing device specific configuration to the web can be avoided by implementing dialogs (like the file picker for <input type=file>). Those can be implemented in the platform and ask the user which information to expose to the current website specifically. | ||
This is an area where we're still doing a lot of research. I really want to emphasize that we don't have all the answers yet, but that we plan on having them before we roll out these APIs to millions of users. | This is an area where we're still doing a lot of research. I really want to emphasize that we don't have all the answers yet, but that we plan on having them before we roll out these APIs to millions of users. | ||
| Line 555: | Line 576: | ||
== Plans == | == Plans == | ||
* [[WebAPI/PlannedWork| | * [[WebAPI/PlannedWork|Old planning document]] | ||
* | * Old (2013) [[WebAPI/Storage2013|storage discussion notes]] | ||
== Meetings == | == Meetings == | ||
We used to have weekly meetings but as of 1 October 2014 we no longer do. | We used to have weekly meetings but as of 1 October 2014 we no longer do. | ||
If there's something you'd like to discuss, ask on [https://lists.mozilla.org/listinfo/dev- | If there's something you'd like to discuss, ask on [https://lists.mozilla.org/listinfo/dev-platform dev-platform]. Since much of this effort is under Mozilla's DOM team, [irc://irc.mozilla.org/content #content] isn't a bad place for IRC conversation. | ||
=== Meeting Notes === | === Meeting Notes === | ||
| Line 755: | Line 776: | ||
* [[WebAPI/2011-08-23|August 23 2011]] | * [[WebAPI/2011-08-23|August 23 2011]] | ||
|} | |} | ||
=== See also === | === See also === | ||