WebAPI/SettingsAPI: Difference between revisions

m
syntax fixes
m (syntax fixes)
Line 1: Line 1:
== Status ==
== Status ==


The proposed specification doesn't have a fully working implementation yet. Patches will appear in [bug|678695].
The proposed specification doesn't have a fully working implementation yet. Patches will appear in {{bug|678695}}.


== Proposed API ==
== Proposed API ==
Line 27: Line 27:
== Notes ==
== Notes ==


* SettingsRequest will be similar to SMSRequest described in [WebSMS specification|WebAPI/WebSMS].
* SettingsRequest will be similar to SMSRequest described in [[WebAPI/WebSMS|WebSMS specification]].
* As for BatteryAPI, SettingsManager object might be in window.navigator, window.navigator.devices or even could be created with ''new''.
* As for BatteryAPI, SettingsManager object might be in window.navigator, window.navigator.devices or even could be created with ''new''.
* The allowed types are restricted to the type we know we will be using in the first implementation. Those could be extended.
* The allowed types are restricted to the type we know we will be using in the first implementation. Those could be extended.
* If a setting is unknown, it should fail.
* If a setting is unknown, it should fail.
* But some platforms might not know some settings. Do we want to add a method that checks if the platform knows a specific setting?
* But some platforms might not know some settings. Do we want to add a method that checks if the platform knows a specific setting?
Confirmed users
368

edits