Devices and Sensors Working Group - Activity
No matches.
Lifecycle
-
1 charter started.
-
Chartered until 30 September 2028.
-
Participants
-
1 participant joined.
-
Alexander Kyereboah (Microsoft Corporation) joined.
-
GitHub
w3c/geolocation
-
1 issue received 1 new comment.
-
2 pull requests received 2 new comments.
-
While emulating, only set emulated position data wakes a watch w3c/geolocation#236 (1 comment by @marcoscaceres)
-
Add support for approximate location (without separate permission) w3c/geolocation#233 (1 comment by @marcoscaceres)
-
w3c/das-wg
-
1 issue received 2 new comments.
-
1 pull request opened.
-
Charter & roadmap update w3c/das-wg#84, by @anssiko.
-
-
1 pull request merged.
-
Charter & roadmap update w3c/das-wg#84.
-
w3c/compute-pressure
-
1 issue closed.
-
Metabug: Raising Specification to CR maturity level. w3c/compute-pressure#295.
-
-
1 issue received 1 new comment.
-
Metabug: Raising Specification to CR maturity level. w3c/compute-pressure#295 (1 comment by @anssiko)
-
TR publications
-
1 document published.
-
Screen Wake Lock API published as a Working Draft. History of Screen Wake Lock API
-
GitHub
w3c/geolocation
-
2 issues opened.
-
How coarse must an approximate position be? w3c/geolocation#235, by @marcoscaceres.
-
TPAC 2026 Status Report w3c/geolocation#234, by @marcoscaceres.
-
-
4 issues received 6 new comments.
-
How coarse must an approximate position be? w3c/geolocation#235 (2 comments by @antosart, @marcoscaceres)
-
How to specify desired accuracy / resolution of data? w3c/geolocation#49 (1 comment by @marcoscaceres)
-
-
1 pull request opened.
-
While emulating, only set emulated position data wakes a watch w3c/geolocation#236, by @marcoscaceres.
-
-
1 pull request closed.
-
Add support for approximate geolocation w3c/geolocation#195.
-
-
2 pull requests received 14 new comments.
-
Add support for approximate location (without separate permission) w3c/geolocation#233 (11 comments by @antosart, @marcoscaceres, @martinthomson)
-
Add support for approximate geolocation w3c/geolocation#195 (3 comments by @alvinjiooo, @marcoscaceres)
-
w3c/deviceorientation
-
1 issue opened.
-
TPAC 2026 Status Report w3c/deviceorientation#194, by @marcoscaceres.
-
-
1 issue received 1 new comment.
w3c/screen-wake-lock
-
1 issue closed.
-
TPAC 2025 status report w3c/screen-wake-lock#376.
-
-
1 issue received 2 new comments.
-
1 pull request opened.
-
editorial: split security and privacy considerations into two sections w3c/screen-wake-lock#380, by @marcoscaceres.
-
-
1 pull request merged.
-
editorial: split security and privacy considerations into two sections w3c/screen-wake-lock#380.
-
w3c/das-wg
-
1 issue opened.
-
Video integration with sensor data at TPAC? w3c/das-wg#83, by @rjksmith.
-
-
1 issue closed.
-
Video integration with sensor data at TPAC? w3c/das-wg#83.
-
-
1 issue received 3 new comments.
-
Video integration with sensor data at TPAC? w3c/das-wg#83 (3 comments by @anssiko, @reillyeon, @rjksmith)
-
w3c/vibration
-
1 issue received 1 new comment.
GitHub
w3c/geolocation
-
2 pull requests received 20 new comments.
-
Add support for approximate location (without separate permission) w3c/geolocation#233 (19 comments by @antosart, @marcoscaceres, @martinthomson, @saschanaz, @sideshowbarker)
-
w3c/screen-wake-lock
-
1 issue opened.
-
TPAC 2026 Status Report w3c/screen-wake-lock#379, by @LJWatson.
-
w3c/contact-picker
-
1 issue opened.
-
TPAC 2026 Status Report w3c/contact-picker#82, by @LJWatson.
-