Updated proposal. Please reply-to dev-weba...@lists.mozilla.org
Name of API: Web SMS API
References: https://bugzilla.mozilla.org/show_bug.cgi?id=674725
Brief purpose of API: Send and recieve SMS messages
General Use Cases: None
Inherent threats:
* Sending an SMS costs user money, premium SMS
On Apr 21, 2012, at 10:35 PM, Thinker K.F. Li wrote:
> Hi,
>
> Although we donwload pages automatically if the cache manifest changes,
> but the new cache will only be used for next time of launching.
>
> I concern more about faults of networks. Internet is not always stable
> and secured. For
Updated proposal. Please reply-to dev-weba...@lists.mozilla.org
Name of API: Open Web App API
Reference: https://developer.mozilla.org/en/OpenWebApps/The_JavaScript_API
Brief purpose of API: The Open Web Apps JavaScript API is a programmatic
interface for installing Web apps and for managing a
Hmm, so I'm not sure exactly where we came out on this discussion. As Mounir
pointed out, discussion of Wifi, Bluetooth and other network-y APIs should be
held in those respective APIs (and yes, those have not yet been posted). Is it
likely that this API is really focused on certified apps tha
"Final" proposal. Please reply-to dev-weba...@lists.mozilla.org with any major
issues.
Name of API: Resource Lock API
Reference: https://bugzilla.mozilla.org/show_bug.cgi?id=697132
Brief purpose of API: Prevent the screen from being dimmed or switched off
General Use Cases: Request a lock to st
Updated proposal:
Name of API: Web Telephony
References:
https://wiki.mozilla.org/WebAPI/WebTelephony
*B2G Meta telephony bug https://bugzilla.mozilla.org/show_bug.cgi?id=699235
*Web Telephony meta bug: https://bugzilla.mozilla.org/show_bug.cgi?id=674726
Brief purpose of API: Make and receive p
