WebAPI: Difference between revisions

WebAPI (view source)

Revision as of 20:03, 31 August 2011

1,420 bytes removed , 31 August 2011

no edit summary

Khuey

Confirmed users

201

edits

@@ Line 38: / Line 38: @@
 |-
 | Games
-| <font color="green">Accelerometer API</font>, [https://bugzilla.mozilla.org/show_bug.cgi?id=633602 Mouse Lock API]
+| <font color="green">Accelerometer API</font>
 |-
 | Maps
@@ Line 44: / Line 44: @@
 |}
-Mozilla will most likely '''not''' implement the FileSystem API.  For local file access, we have implemented <font color="purple">FileReader</font> and plan to implement [https://bugzilla.mozilla.org/show_bug.cgi?id=557540 FileWriter].  A file system abstraction can additionally be built on top of <font color="green">IndexedDB</font>.
+Mozilla will most likely '''not''' implement the FileSystem API.  For local file access, we have implemented <font color="purple">FileReader</font> and plan to implement parts of the [https://bugzilla.mozilla.org/show_bug.cgi?id=557540 FileWriter] specification.  A file system abstraction can additionally be built on top of <font color="green">IndexedDB</font>.
 '''Legend'''<br/>
@@ Line 54: / Line 54: @@
 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 Principles ==
-=== Security ===
-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 users contact list, or able to issue arbitrary commands to any USB device which is hooked up to the users 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.
 == Meetings ==
 * Tuesday @ 10:00am PDT
-{{conf|9254}}
+{{conf|254}}
-* (you can also join room 254 on vidyo if you have a mozilla account)
 * *1 to unmute yourself
 * join irc.mozilla.org #webapi for back channel
+* Mountain View conference room "All Your Base"
 == Communication ==