- From: Max Froumentin via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 24 Nov 2009 10:35:48 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/system-info In directory hutz:/tmp/cvs-serv12242 Modified Files: Overview.html Log Message: make valid XML and correct a few markup bugs in the process Index: Overview.html =================================================================== RCS file: /sources/public/2009/dap/system-info/Overview.html,v retrieving revision 1.6 retrieving revision 1.7 diff -u -d -r1.6 -r1.7 --- Overview.html 29 Oct 2009 21:40:52 -0000 1.6 +++ Overview.html 24 Nov 2009 10:35:46 -0000 1.7 @@ -102,10 +102,10 @@ as an argument. If the attempt fails, and the method was invoked with a non-null <code>errorCallback</code> argument, the implementation MUST invoke the <code>errorCallback</code> with a <code>PowerError</code> object - as an argument. + as an argument.</li> <li>Invoke the appropriate callback with a new <code>PowerLevel</code> object every time the implementation determines that the power level of the - hosting device has changed. + hosting device has changed.</li> </ol> </dd> <dt>void clearWatch(in int watchId)</dt> @@ -686,7 +686,7 @@ Returns a DisplayOrientation object that indicates the orientation of the current display. </dd> - <dt>readonly attribute sequence<DisplayOrientation> supportedOrientations </dt> + <dt>readonly attribute sequence<DisplayOrientation> supportedOrientations </dt> <dd> The orientations that this device supports. </dd> @@ -971,11 +971,11 @@ <dd> The preferrred network bearer. </dd> - <dt>readonly attribute sequence<NetworkBearer> availableNetworkBearers</dt> + <dt>readonly attribute sequence<NetworkBearer> availableNetworkBearers</dt> <dd> The list network bearers that are currently available. </dd> - <dt>readonly attribute sequence<NetworkBearer> supportedNetworkBearers</dt> + <dt>readonly attribute sequence<NetworkBearer> supportedNetworkBearers</dt> <dd> The list of network bearers that the device supports. </dd> @@ -1072,7 +1072,7 @@ the following set of steps: <ol> <li>Monitor the network resources specified in the <code>NetworkChangeOptions</code> - object. + object.</li> <li>When the specififed network resources change, invoke the <code>NetworkChangeCallback</code> with the appropriate flag set in the <code>NetworkChange</code> parameter to indicate what change occured.</li> @@ -1801,7 +1801,7 @@ </section> </section> <dl title='[NoInterfaceObject] interface Thermal' class='idl'> - <dt>readonly attribute sequence <Thermometer> thermometers</dt> + <dt>readonly attribute sequence <Thermometer> thermometers</dt> <dd> The list of thermometers attached to the system. </dd> @@ -1827,15 +1827,15 @@ When called, <code>watchTemperature()</code> MUST immediately return and then asynchronously start a watch process defined as the following set of steps: <ol> - <li>Monitor the ambient temperature. + <li>Monitor the ambient temperature. </li> <li>When the temperature changes in a manner specified by the <code>options</code> parameter, invoke the <code>TemperatureChangeCallback</code> with the appropriate attribute set in the <code>TemperatureChange</code> parameter to - indicate what change occured. + indicate what change occured.</li> <li>If the monitoring fails at any point, and the method was invoked with a non-null <code>errorCallback</code> argument, invoke the <code>errorCallback</code> with a <code> - TemperatureChangeError</code> object as an argument. + TemperatureChangeError</code> object as an argument. </li> </ol> </dd> <dt>void clearWatch(in long watchId)</dt>
Received on Tuesday, 24 November 2009 10:35:50 UTC