WebAPI/NetworkAPI: Difference between revisions

no edit summary
(→‎Proposed API: add onchange)
No edit summary
 
(2 intermediate revisions by one other user not shown)
Line 3: Line 3:
The DAP WG (W3C) has a specification sharing this proposal goal [1]. Our proposal might or might not look like it for the moment. Suggestions and comments will be submitted to the Device Status Task Force [2].
The DAP WG (W3C) has a specification sharing this proposal goal [1]. Our proposal might or might not look like it for the moment. Suggestions and comments will be submitted to the Device Status Task Force [2].


[1] http://dev.w3.org/2009/dap/netinfo/
[1] http://dev.w3.org/2009/dap/netinfo/<br>
[2] http://lists.w3.org/Archives/Public/public-device-status/
[2] http://lists.w3.org/Archives/Public/public-device-status/


Line 24: Line 24:
     // Estimated bandwidth (in MB/s) of the current connection.
     // Estimated bandwidth (in MB/s) of the current connection.
     readonly attribute double  bandwidth;
     readonly attribute double  bandwidth;
 
 
     // Return whether the current connection is metered (like quota limitation, pay per use, etc.).
     // Return whether the current connection is metered (like quota limitation, pay per use, etc.).
     readonly attribute boolean metered;
     readonly attribute boolean metered;
 
 
     // A 'change' event is fired when one of the previous attributes is changed.
     // A 'change' event is fired when one of the previous attributes is changed.
             attribute Function onchange;
             attribute Function onchange;
Line 39: Line 39:


== Considered changes ==
== Considered changes ==
[[Category:Web APIs]]
Confirmed users
1,340

edits