@@ -91,7 +91,7 @@ Examples {#examples}
91
91
92
92
<div class="example">
93
93
In this simple example, ambient light sensor is created with
94
- default configuration. Whenever new [=sensor readings|reading=] is available,
94
+ default configuration. Whenever a new [=sensor readings|reading=] is available,
95
95
it is printed to the console.
96
96
97
97
<pre highlight="js">
@@ -103,10 +103,10 @@ Examples {#examples}
103
103
</div>
104
104
105
105
<div class="example">
106
- In this example, exposure value (EV) at ISO 100 is calculated from
106
+ In this example, the exposure value (EV) at ISO 100 is calculated from
107
107
the ambient light [=sensor readings=] . Initially, we check that the user
108
108
agent has permissions to access ambient light [=sensor readings=] . Then,
109
- {{AmbientLightSensor/illuminance!!attribute}} value is converted to the
109
+ the {{AmbientLightSensor/illuminance!!attribute}} value is converted to the
110
110
closest exposure value.
111
111
112
112
<pre highlight="js">
@@ -187,9 +187,9 @@ the device environment. Potential privacy risks include:
187
187
- Cross-origin leaks. Light emitted from the screen can be reflected back to
188
188
the sensor from nearby reflective surfaces. Malicious sites can embed
189
189
resources from different origins and scale the content to display
190
- particular pixels to allow distinguish the contents, pixel by pixel.
191
- - Hijacking browsing history. Styling visited links to allow distinguish the
192
- light levels associated with visited and unvisited links i.e. visited
190
+ particular pixels to allow distinguishing the contents, pixel by pixel.
191
+ - Hijacking browsing history. Styling visited links to allow distinguishing
192
+ the light levels associated with visited and unvisited links i.e. visited
193
193
links styled as a block of black screen; white for unvisited.
194
194
195
195
To mitigate these Ambient Light Sensor specific threats, user agents should
@@ -274,7 +274,7 @@ Use Cases and Requirements {#usecases-requirements}
274
274
interprets them to control a game character.
275
275
276
276
While some of the use cases may benefit from obtaining precise ambient light measurements, the use
277
- cases that convert ambient light level fluctuations to user input events, would benefit from
277
+ cases that convert ambient light level fluctuations to user input events would benefit from
278
278
higher [=sampling frequency|sampling frequencies=] .
279
279
280
280
Acknowledgements {#acknowledgements}
0 commit comments