348
edits
WebAPI: Difference between revisions
m
→Design Principals
| Line 55: | Line 55: | ||
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 an initial implementation is available on trunk, we will submit the new API for standardization to the W3C. | 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 an initial implementation is available on trunk, we will submit the new API for standardization to the W3C. | ||
== Design | == Design Principles == | ||
=== Security === | === Security === | ||
| Line 69: | Line 69: | ||
One question that often comes up, is should we do low level APIs, like USB access, or high level APIs, like camera access? | 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. | 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. | ||
== Meetings == | == Meetings == | ||