The Mozilla WebAPI team is pushing the envelope of the web to include --- and in places exceed --- the capabilities of competing stacks.
WebAPI work is being tracked by Mozilla bug 673923. Find an dependent bug that interests you (and is unassigned), and assign it to yourself.
This wiki page's purpose is mostly to be able to track the advancement of the work on the different APIs covered by the WebAPI team and help working on those. If you are interested in documentation for these Web APIs, you should look at the following MDN documentation page: https://developer.mozilla.org/docs/WebAPI
Here's a list of the APIs that we're working on. Some of them are done, and some of them we haven't gotten further than acknowledge that we probably need them.
Planned for initial release of B2G (aka Basecamp)
Unless otherwise noted, APIs listed in the table below were available in Firefox OS v1.0.1 or will be available in v1.1.
|WebTelephony||Allow placing and answering phone calls as well as build in-call UI.||W3C ED (SysApps)||bug 674726, Security|
|Vibration API||Control device vibration for things like haptic feedback in games. Not intended to solve things like vibration for notification.||W3C CR (Device APIs)||bug 679966, Security|
|WebSMS||Send/receive SMS messages as well as manage messages stored on device.||W3C ED (SysApps)||bug 674725, Security|
|Idle API||Get notifications when user is idle.||Needs plan||bug 715041, Security|
|Screen Orientation||Get notification when screen orientation changes as well as control which screen orientation a page/app wants.||W3C WD (WebApps)||bug 720794 bug 740188 bug 673922, Security|
|Settings API||Set system-wide configurations that are saved permanently on the device.||Future?||bug 678695, Security|
|Power Management API||Turn on/off screen, cpu, device power, etc. Listen and inspect resource lock events.||Future?||bug 708964, Security|
|Mobile Connection API||Expose signal strength, operator, etc for GSM and other mobile connections. This does not cover WiFi.||Future?||bug 729173, Security|
|TCP Socket API||Low-level TCP socket API. Will also include SSL support.||W3C ED (SysApps)||bug 733573 bug 892833, Security|
|Geolocation API||Access to the end user's location.||W3C CR||Security|
|WiFi Information API||Privileged API to get a list of available WiFi networks. Also get signal strength and name of currently connected network, etc.||Future?||Security|
|Device Storage API||Add/Read/Modify files stored on a central location on the device. For example the "pictures" folder on modern desktop platforms or the photo storage in mobile devices.||Needs plan||bug 717103, Security|
|Contacts API||Add/Read/Modify the device contacts address book.||W3C ED (SysApps)||bug 674720, bug 857730 for Android, Security|
|Mouse Lock API||Lock access to mouse and get access to movement deltas rather than coordinates.||W3C ED||bug 633602|
|Open WebApps||Install web apps and manage installed webapps. Also allows an installed webapp to get payment information. Everything needed to build a Open WebApps app store.||W3C WD (SysApps)||bug 697006, Security|
|WebBluetooth||Low level access to Bluetooth hardware.||Future?||bug 674737, Security|
|Network Information API||Get basic information about current network connectivity. Example: "How fast of a connection do I have?".||W3C ED||bug 677166 bug 713199, Security|
|Battery Status API||Information about battery charge level and if device is plugged in.||W3C CR (DAP)||bug 678694, Security|
|Alarm API||Schedule a notification, or for an application to be started, at a specific time.||W3C WD (SysApps)||bug 749551, Security|
|Browser API||Enables implementing a browser completely in web technologies.||Future?||bug 693515, Security|
|Time/Clock API||Set current time. Timezone will go in the Settings API.||Future?||bug 714357, bug 714358, API proposed|
|Web Activities||Delegate an activity to another application.||Discussed in Device APIs||bug 715814 bug 776027 for Android|
|Push Notifications API||Allow the platform to send notification messages to specific applications.||W3C ED (Webapps)||bug 822712 for B2G, bug 834033 for Android|
|Permissions API||Allow Settings app to manage all app permissions in a centralized location||Future?||bug 707625, Security|
|WebFM API||For FM radio feature.||Future?||bug 749053, Security|
|FileHandle API||Writable files with locking.||Needs plan||bug 726593|
|Network Stats API||Monitor data usage and expose data to privileged apps||Future?||bug 746069|
|WebPayment||Allow web content to initiate payments and refunds for virtual goods. For the server implementation, see WebPaymentProvider.||Beginning||bug 767818 bug 813756bug 898499|
|IndexedDB||Client-side storage of structured data and high performance searches on this data||W3C WD||bug 553412, Security|
|Archive API||Blob support for Zip file contents||Future?||bug 772434|
|Ambient light sensor||Device light sensor support||W3C WD||bug 738465|
|Proximity sensor||Device proximity sensor support||W3C WD||bug 738131|
|SystemXHR||External (non-same origin) XMLHttpRequests||?||?|
Planned for the future
|Resource lock API||bug 697132||Prevent resources from being turned off, for example screen dimming, WiFi turning off, CPU going into sleep mode etc.|| Complete. |
Security Design Complete
|UDP Datagram Socket API||bug 745283||Low-level UDP API.||Planning. (Not P1 for basecamp)|
|USB file-reading API||bug 748350 bug 737153||When enabled, allows mounting of device storage as a USB filesystem on the tethered computer.|| Must be complete by June/July.|
Not really a webAPI, no security design.
|Camera API||This is part of the larger WebRTC effort. This is a big piece of work so see the link.|| API and implementation underway. |
Security Design Complete
|Peer to Peer API||This is part of the larger WebRTC effort. This is a big piece of work so see the link.||API and implementation underway.|
|WebNFC||bug 674741||Low level access to NFC hardware. So far focusing on NDEF support.|| API drafted, implementation underway for B2G (not Andorid/Desktop), must be complete by June/July. |
Security Design Complete
|WebUSB||bug 674718||Low level access to USB hardware.||Security Design Complete|
|HTTP-cache API||Query what's stored in the browsers http-cache. Add/remove entries. Update expiration time. Get data directly from cache.||None|
|Calendar API||Add/Read/Modify to the device calendar.||Implementation not planned ATM. If/when implemented, it should mimic WebAPI/ContactsAPI.|
|Spellcheck API||Enable webpages to check if a piece of text is correctly spelled as well as get suggestions for corrections.||None|
|Background services||Enable a web application to run in the background and perform tasks like syncing or respond to incoming messages.|| Initial proposal of API.|
Security Design Active
|LogAPI||Allows to register the user activity on the phone.||API proposal exists. Not planned for 1.0.|
|Keyboard/IME API||bug 737110 (WebAPI mailing list post, Extended API mailing list post)||Enables implementing virtual keyboards.||Only exposed to certified apps for V1. Controlled via a setting instead.]|
|DataStore API||bug 871445||Shared app/site data stores with a mechanism for multiple applications to concurrently synchronize shared data into local caches||Standardization: W3C ED (SysApps)|
|D = Desktop, A = Android, B = B2G|
|only available to certified apps on this platform|
|only available to privileged and certified apps on this platform|
|implemented and preference enabled by default on on this platform|
|implemented but requires explicitly turning on the preference on this platform|
|not implemented for this platform|
|not currently planned for this platform|
A draft specification and prototype implementation of new Web APIs will be discussed publicly on our mailing list and at our public meetings (see below). Once we have an API that we feel that we are satisfied with, we will submit the new API for standardization to the W3C.
The goal is to standardize all APIs.
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.
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.
Low Level vs. High Level
One question that often comes up, is should we do low level APIs, like USB access, or high level APIs, like camera access?
In many cases we are going to want to do both high level and low level APIs, with an initial priority on low level. High level APIs will let us create more friendly APIs, which are both easier to use for developers, and better for users since we can provide better security guarantees. However low level APIs will provide support for a wider range of hardware and use cases and will get the browser out of the critical path for innovation.
Plans for 2013
- Agenda for this week (create below if it doesn't exist yet)
- Tuesdays alternating 8:00 AM Pacific Time and 4:00 PM Pacific Time (watch mailing list for announcement)
- WebAPI Vidyo room
- Dial-in: conference# 98413
- US/California/Mountain View: +1 650 903 0800, x92 Conf# 98413
- US/California/San Francisco: +1 415 762 5700, x92 Conf# 98413
- US/Oregon/Portland: +1 971 544 8000, x92 Conf# 98413
- CA/Vancouver: +1 778 785 1540, x92 Conf# 98413
- CA/Toronto: +1 416 848 3114, x92 Conf# 98413
- UK/London: +44 (0)207 855 3000, x92 Conf# 98413
- FR/Paris: +33 1 44 79 34 80, x92 Conf# 98413
- US/Toll-free: +1 800 707 2533, (pin 369) Conf# 98413
- San Francisco: Amoeba conference room (7th floor)
- London: Allo Allo conference room
- Toronto: Spadina conference room
- Join irc.mozilla.org #webapi for back channel
Notes will be taken on etherpad: https://etherpad.mozilla.org/webapi-meetingnotes
Create a new weekly agenda from the template:
Remember: You'll still need to link it below!
Mailing-list / Newsgroup
You can subscribe to the mailing list here: https://lists.mozilla.org/listinfo/dev-webapi
And the web based API is here: http://groups.google.com/group/mozilla.dev.webapi/topics
The newsgroup lives on the news.mozilla.org server and has the name mozilla.dev.webapi
Find us on irc.mozilla.org in #webapi. Need help to use Mozilla IRC servers?
- Introducing WebAPI blog post by Robert Nyman
- More details about the WebAPI effort blog post by Jonas Sicking
- Mozilla joins the W3C DAP – WebAPI progress blog post by Robert Nyman and Jonas Sicking
- A look at the latest WebAPIs a demo/blog post by John Hammink
- Battery API by Robert Nyman
- Vibration API by Robert Nyman
- Demos by John Hammink
- Network API by Colin Frei
- W3C Device APIs (DAP). Mozilla developers are members of the DAP working group (announcement).
- Wholesale Applications Community (WAC)