Devices and Sensors Working Group - Activity in 2018
No matches.
TR publications
-
1 document published.
-
Geolocation Sensor published as a Working Draft. History of Geolocation Sensor
-
GitHub
w3c/system-wake-lock
-
2 issues opened.
-
Privacy consideration about tracking location w3c/system-wake-lock#3, by @jyasskin.
-
Does "system" wakelock really prevent "device's CPU from entering a standby mode"? w3c/system-wake-lock#11, by @jyasskin.
-
-
1 issue received 2 new comments.
-
Privacy consideration about tracking location w3c/system-wake-lock#3 (2 comments by @jyasskin, @thecodingdude)
-
w3c/screen-wake-lock
-
9 issues opened.
-
Duplicate (?) normative requirements w3c/screen-wake-lock#143, by @domenic.
-
Consider using the platform's standard cancelation primitive, AbortSignal w3c/screen-wake-lock#142, by @domenic.
-
Subtleties of using Document are not specced w3c/screen-wake-lock#141, by @domenic.
-
Give advice on how UAs should infer consent to take a wakelock w3c/screen-wake-lock#140, by @jyasskin.
-
WakeLock and only require activation once w3c/screen-wake-lock#139, by @petele.
-
What do the wakelocks actually do? w3c/screen-wake-lock#138, by @jyasskin.
-
Make WakeLock require user gesture before activation w3c/screen-wake-lock#135, by @petele.
-
Remove cancel() w3c/screen-wake-lock#134, by @beaufortfrancois.
-
API to get list of active wake locks w3c/screen-wake-lock#133, by @petele.
-
-
1 issue closed.
-
Remove cancel() w3c/screen-wake-lock#134.
-
-
10 issues received 24 new comments.
-
Make WakeLock require user gesture before activation w3c/screen-wake-lock#135 (5 comments by @andrey-logvinov, @marcoscaceres, @tomayac)
-
Give advice on how UAs should infer consent to take a wakelock w3c/screen-wake-lock#140 (4 comments by @Ajedi32, @feross, @jyasskin, @tomayac)
-
WakeLock and only require activation once w3c/screen-wake-lock#139 (3 comments by @jyasskin, @tomayac)
-
Need maximum screen brightness mode w3c/screen-wake-lock#129 (3 comments by @jyasskin, @marcoscaceres, @mounirlamouri)
-
Low battery while wake lock is on should cancel the lock w3c/screen-wake-lock#132 (2 comments by @marcoscaceres, @tomayac)
-
API to get list of active wake locks w3c/screen-wake-lock#133 (2 comments by @marcoscaceres, @tomayac)
-
Turn on screen and screen lock from system lock or the like w3c/screen-wake-lock#130 (1 comment by @tomayac)
-
w3c/deviceorientation
-
1 issue opened.
-
Add API for requesting permission to receive device motion / orientation events w3c/deviceorientation#57, by @cdumez.
-
-
1 issue reopened.
-
Add API for requesting permission to receive device motion / orientation events w3c/deviceorientation#57, by @cdumez.
-
-
1 issue received 20 new comments.
-
Add API for requesting permission to receive device motion / orientation events w3c/deviceorientation#57 (20 comments by @19h, @annevk, @anssiko, @cdumez, @geoffreygaren, @jyasskin, @reillyeon, @richtr)
-
w3c/contact-picker
-
1 issue received 4 new comments.
-
Is there evidence that emerging market users have useful on-device contact databases? w3c/contact-picker#6 (4 comments by @adityapunjani, @domenic)
-
w3c/sensors
-
1 pull request opened.
-
Update echidna.sh flags w3c/sensors#376, by @anssiko.
-
-
1 pull request merged.
-
Update echidna.sh flags w3c/sensors#376.
-
-
1 pull request received 1 new comment.
w3c/ambient-light
-
1 issue received 1 new comment.
-
1 pull request opened.
-
editorial: Minor proof-reading. w3c/ambient-light#53, by @rakuco.
-
-
1 pull request merged.
-
editorial: Minor proof-reading. w3c/ambient-light#53.
-
-
1 pull request received 1 new comment.
w3c/geolocation
-
1 issue received 1 new comment.
GitHub
w3c/screen-wake-lock
-
1 issue received 17 new comments.
-
Need maximum screen brightness mode w3c/screen-wake-lock#129 (17 comments by @HenrikJoreteg, @jyasskin, @marcoscaceres, @mounirlamouri, @tomayac)
-
w3c/sensors
-
1 issue closed.
-
Define WebDriver extension API for test automation w3c/sensors#363.
-
-
2 pull requests opened.
-
Add Explainer to spec metadata header w3c/sensors#375, by @anssiko.
-
Fix typo in webdriver-extension/explainer.md w3c/sensors#374, by @Honry.
-
-
3 pull requests merged.
-
Add Explainer to spec metadata header w3c/sensors#375.
-
Fix typo in webdriver-extension/explainer.md w3c/sensors#374.
-
Introduce WebDriver extension API w3c/sensors#369.
-
-
2 pull requests received 33 new comments.
-
Introduce WebDriver extension API w3c/sensors#369 (32 comments by @anssiko, @foolip, @Honry, @JohnChen0, @rakuco)
-
w3c/contact-picker
-
9 issues opened.
-
Restrict to top-level navigables w3c/contact-picker#9, by @PaulKinlan.
-
ContactInfo can be a dictionary w3c/contact-picker#8, by @annevk.
-
Consider contact API that does not reveal contact info to the website w3c/contact-picker#7, by @Gozala.
-
Is there evidence that emerging market users have useful on-device contact databases? w3c/contact-picker#6, by @domenic.
-
Consider dictionaries and sequences instead of non-constructible interfaces and frozen arrays w3c/contact-picker#5, by @domenic.
-
interface ContactInfo: metadata distinguishing email/tel instances? w3c/contact-picker#4, by @inexorabletash.
-
interface ContactInfo: Should name be a sequence? w3c/contact-picker#3, by @inexorabletash.
-
interface ContactInfo: Can't use sequence<> as type of attribute w3c/contact-picker#2, by @inexorabletash.
-
API shape: how about navigator.contacts.XXX ? w3c/contact-picker#1, by @inexorabletash.
-
-
3 issues closed.
-
API shape: how about navigator.contacts.XXX ? w3c/contact-picker#1.
-
interface ContactInfo: Should name be a sequence? w3c/contact-picker#3.
-
interface ContactInfo: Can't use sequence<> as type of attribute w3c/contact-picker#2.
-
-
6 issues received 10 new comments.
-
interface ContactInfo: metadata distinguishing email/tel instances? w3c/contact-picker#4 (3 comments by @annevk, @beverloo)
-
Is there evidence that emerging market users have useful on-device contact databases? w3c/contact-picker#6 (2 comments by @domenic, @PaulKinlan)
-
Consider dictionaries and sequences instead of non-constructible interfaces and frozen arrays w3c/contact-picker#5 (2 comments by @beverloo, @domenic)
-
w3c/geolocation
-
2 issues received 6 new comments.
-
Support geolocation (especially geofencing) in the "background" w3c/geolocation#214 (5 comments by @anssiko, @romulocintra)
-
w3c/deviceorientation
-
1 pull request received 1 new comment.
-
Add the ondeviceorientationabsolute event handler attribute w3c/deviceorientation#34 (1 comment by @reillyeon)
-
Participants
-
2 organizations joined.
-
HTML5 Converged Technology Forum joined.
-
Inswave Co., Ltd. joined.
-
GitHub
w3c/deviceorientation
-
1 issue closed.
-
Invalid IDL in DeviceMotionEventInit w3c/deviceorientation#54.
-
-
1 pull request opened.
-
Reference the "use cases" section by the right number w3c/deviceorientation#56, by @rakuco.
-
-
2 pull requests merged.
-
Remove '?' from dictionary members of DeviceMotionEventInit w3c/deviceorientation#55.
-
Reference the "use cases" section by the right number w3c/deviceorientation#56.
-
-
2 pull requests closed.
-
Add deviceorientation and devicemotion feature detection conformance requirement w3c/deviceorientation#12.
-
Add screen-adjusted device orientation attributes to DeviceOrientationEvent interface w3c/deviceorientation#10.
-
-
7 pull requests received 11 new comments.
-
Add the ondeviceorientationabsolute event handler attribute w3c/deviceorientation#34 (3 comments by @foolip, @reillyeon)
-
Reference the "use cases" section by the right number w3c/deviceorientation#56 (3 comments by @anssiko, @rakuco)
-
Remove '?' from dictionary members of DeviceMotionEventInit w3c/deviceorientation#55 (1 comment by @reillyeon)
-
update rotationRate alpha, beta, gamma description to be the same as implementation w3c/deviceorientation#43 (1 comment by @reillyeon)
-
Add deviceorientation and devicemotion feature detection conformance requirement w3c/deviceorientation#12 (1 comment by @reillyeon)
-
Add screen-adjusted device orientation attributes to DeviceOrientationEvent interface w3c/deviceorientation#10 (1 comment by @reillyeon)
-
w3c/screen-wake-lock
-
4 issues opened.
-
Low battery while wake lock is on should cancel the lock w3c/screen-wake-lock#132, by @larsgk.
-
Add WebIDL overview at the end of the spec w3c/screen-wake-lock#131, by @kenchris.
-
Turn on screen and screen lock from system lock or the like w3c/screen-wake-lock#130, by @tomayac.
-
Need maximum screen brightness mode w3c/screen-wake-lock#129, by @tomayac.
-
-
1 issue closed.
-
Add WebIDL overview at the end of the spec w3c/screen-wake-lock#131.
-
-
1 issue received 8 new comments.
-
Need maximum screen brightness mode w3c/screen-wake-lock#129 (8 comments by @marcoscaceres, @mounirlamouri, @tomayac)
-
w3c/das-wg
-
1 issue received 5 new comments.
-
1 pull request opened.
-
Fix home navigation link. w3c/das-wg#23, by @markafoltz.
-
-
1 pull request closed.
-
Fix home navigation link. w3c/das-wg#23.
-
-
1 pull request received 2 new comments.
w3c/geolocation
-
2 issues received 3 new comments.
-
Support geolocation (especially geofencing) in the "background" w3c/geolocation#214 (2 comments by @jakearchibald, @tomayac)
-
w3c/ambient-light
-
1 issue received 2 new comments.
w3c/battery
-
1 pull request received 6 new comments.
-
Allow use in same-origin children, add Feature Policy integration w3c/battery#13 (6 comments by @anssiko, @clelland)
-
Participants
-
1 participant joined.
-
Lars Knudsen (W3C Invited Experts) joined.
-
GitHub
w3c/deviceorientation
-
1 issue opened.
-
Invalid IDL in DeviceMotionEventInit w3c/deviceorientation#54, by @bzbarsky.
-
-
1 issue received 16 new comments.
-
Invalid IDL in DeviceMotionEventInit w3c/deviceorientation#54 (16 comments by @annevk, @bzbarsky, @mkruisselbrink, @reillyeon)
-
-
1 pull request opened.
-
Remove '?' from dictionary members of DeviceMotionEventInit w3c/deviceorientation#55, by @reillyeon.
-
-
1 pull request closed.
-
Add 'Handling Screen Orientation Changes' annex to specification w3c/deviceorientation#7.
-
-
3 pull requests received 7 new comments.
-
Add screen-adjusted device orientation attributes to DeviceOrientationEvent interface w3c/deviceorientation#10 (4 comments by @anssiko, @Honry, @TolMera)
-
Remove '?' from dictionary members of DeviceMotionEventInit w3c/deviceorientation#55 (2 comments by @anssiko, @bzbarsky)
-
Add 'Handling Screen Orientation Changes' annex to specification w3c/deviceorientation#7 (1 comment by @anssiko)
-
w3c/sensors
-
1 issue opened.
-
Garbage collection behavior unclear in Generic Sensor spec w3c/sensors#372, by @phoddie.
-
-
1 issue closed.
-
Garbage collection behavior unclear in Generic Sensor spec w3c/sensors#372.
-
-
1 issue received 13 new comments.
-
Garbage collection behavior unclear in Generic Sensor spec w3c/sensors#372 (13 comments by @anssiko, @Honry, @phoddie, @rakuco, @reillyeon, @smaug----)
-
-
1 pull request opened.
-
Improve wording in the "Sensor garbage collection" session w3c/sensors#373, by @rakuco.
-
-
1 pull request merged.
-
Improve wording in the "Sensor garbage collection" session w3c/sensors#373.
-
-
2 pull requests received 19 new comments.
-
Improve wording in the "Sensor garbage collection" session w3c/sensors#373 (7 comments by @anssiko, @phoddie, @rakuco, @reillyeon)
w3c/das-wg
-
1 issue opened.
-
DAS WG TPAC F2F agenda proposals w3c/das-wg#22, by @anssiko.
-
-
1 issue received 13 new comments.
-
DAS WG TPAC F2F agenda proposals w3c/das-wg#22 (13 comments by @anssiko, @kenchris, @reillyeon, @ThomasTheDane, @tomayac)
-
w3c/geolocation
-
1 issue received 1 new comment.
-
Support geolocation (especially geofencing) in the "background" w3c/geolocation#214 (1 comment by @tomayac)
-
w3c/battery
-
1 pull request received 3 new comments.
-
Allow use in same-origin children, add Feature Policy integration w3c/battery#13 (3 comments by @anssiko, @clelland)
-
w3c/html-media-capture
-
1 issue opened.
-
Limit to filesystem access w3c/html-media-capture#32, by @Novan123.
-
-
1 issue received 1 new comment.
TR publications
-
1 document published.
-
Geolocation Sensor published as a First Public Working Draft. History of Geolocation Sensor
-
Participants
-
8 organizations joined.
-
Privakey, Inc. joined.
-
Google LLC joined.
-
Ecole Mohammadia d'Ingenieurs Rabat (EMI) joined.
-
Intel Corporation joined.
-
Orange joined.
-
Qualcomm Innovation Center, Inc joined.
-
Bocoup joined.
-
Mitsubishi Electric Corporation joined.
-
GitHub
w3c/sensors
-
2 issues opened.
-
Support scripting complex sets of mock sensor readings w3c/sensors#371, by @Honry.
-
Pressure sensor support? w3c/sensors#370, by @maks.
-
-
2 issues received 5 new comments.
-
Support scripting complex sets of mock sensor readings w3c/sensors#371 (4 comments by @foolip, @jugglinmike)
-
-
2 pull requests opened.
-
Introduce WebDriver extension API w3c/sensors#369, by @Honry.
-
Correct typos w3c/sensors#368, by @jugglinmike.
-
-
1 pull request merged.
-
Correct typos w3c/sensors#368.
-
-
2 pull requests received 78 new comments.
-
Introduce WebDriver extension API w3c/sensors#369 (77 comments by @anssiko, @foolip, @Honry, @jugglinmike, @tobie)
-
w3c/deviceorientation
-
1 issue opened.
-
[editorial] Convert the spec source to Bikeshed/ReSpec w3c/deviceorientation#53, by @anssiko.
-
-
1 issue closed.
-
Spec URL is ugly w3c/deviceorientation#16.
-
-
1 issue received 1 new comment.
-
[editorial] Convert the spec source to Bikeshed/ReSpec w3c/deviceorientation#53 (1 comment by @anssiko)
-
-
3 pull requests opened.
-
Update spec metadata w3c/deviceorientation#52, by @xfq.
-
Use pretty URL for the Editor's Draft w3c/deviceorientation#51, by @anssiko.
-
Update README.md w3c/deviceorientation#50, by @xfq.
-
-
3 pull requests merged.
-
Update spec metadata w3c/deviceorientation#52.
-
Use pretty URL for the Editor's Draft w3c/deviceorientation#51.
-
Update README.md w3c/deviceorientation#50.
-
-
6 pull requests received 12 new comments.
-
update rotationRate alpha, beta, gamma description to be the same as implementation w3c/deviceorientation#43 (4 comments by @andybloch, @anssiko, @juncaidf, @reillyeon)
-
Add the ondeviceorientationabsolute event handler attribute w3c/deviceorientation#34 (4 comments by @anssiko, @foolip, @reillyeon)
-
Add deviceorientation and devicemotion feature detection conformance requirement w3c/deviceorientation#12 (1 comment by @anssiko)
-
Add screen-adjusted device orientation attributes to DeviceOrientationEvent interface w3c/deviceorientation#10 (1 comment by @anssiko)
-
w3c/battery
-
1 pull request received 8 new comments.
-
Allow use in same-origin children, add Feature Policy integration w3c/battery#13 (8 comments by @anssiko, @mounirlamouri, @TimothyGu)
-
w3c/das-wg
-
3 pull requests opened.
-
Stop teleconferences w3c/das-wg#21, by @anssiko.
-
Update roadmap ED milestone styles w3c/das-wg#20, by @anssiko.
-
Add Device Orientation Event and Geolocation Sensor to DAS WG w3c/das-wg#19, by @anssiko.
-
-
3 pull requests merged.
-
Stop teleconferences w3c/das-wg#21.
-
Update roadmap ED milestone styles w3c/das-wg#20.
-
-
2 pull requests received 3 new comments.
w3c/accelerometer
-
1 issue opened.
-
Image fallback code fails very badly if *both* images error w3c/accelerometer#48, by @tabatkins.
-
w3c/geolocation
-
1 pull request opened.
-
Clarify Geolocation Sensor group ownership w3c/geolocation#18, by @anssiko.
-
-
2 pull requests merged.
-
Clarify Geolocation Sensor group ownership w3c/geolocation#18.
-
Update web-platform-tests URLs w3c/geolocation#17.
-
-
1 pull request closed.
-
Add Feature Policy integration for the Geolocation API w3c/geolocation#14.
-
-
2 pull requests received 3 new comments.
-
Add Feature Policy integration for the Geolocation API w3c/geolocation#14 (2 comments by @anssiko, @plehegar)
-
w3c/screen-wake-lock
-
1 issue received 5 new comments.
-
What if WakeLockRequest is garbage collected? w3c/screen-wake-lock#128 (5 comments by @anssiko, @mounirlamouri)
-
Participants
-
2 participants joined.
-
Lukasz Olejnik (W3C Invited Experts) joined.
-
Andrey Logvinov (W3C Invited Experts) joined.
-
-
2 organizations joined.
-
CoSMo Software Consulting Pte Ltd joined.
-
Fraunhofer Gesellschaft joined.
-
GitHub
w3c/screen-wake-lock
-
2 issues opened.
-
What if WakeLockRequest is garbage collected? w3c/screen-wake-lock#128, by @mounirlamouri.
-
`WakeLockTypeNotSupported` should be `NotSupportedError` w3c/screen-wake-lock#126, by @mounirlamouri.
-
-
1 issue closed.
-
`WakeLockTypeNotSupported` should be `NotSupportedError` w3c/screen-wake-lock#126.
-
-
2 issues received 4 new comments.
-
What if WakeLockRequest is garbage collected? w3c/screen-wake-lock#128 (2 comments by @andrey-logvinov, @marcoscaceres)
-
`WakeLockTypeNotSupported` should be `NotSupportedError` w3c/screen-wake-lock#126 (2 comments by @marcoscaceres)
-
-
1 pull request opened.
-
BREAKING CHANGE: WakeLockTypeNotSupported -> NotSupportedError w3c/screen-wake-lock#127, by @marcoscaceres.
-
-
1 pull request merged.
-
BREAKING CHANGE: WakeLockTypeNotSupported -> NotSupportedError w3c/screen-wake-lock#127.
-
-
2 pull requests received 16 new comments.
-
Restrict status reporting for wake lock w3c/screen-wake-lock#125 (14 comments by @andrey-logvinov, @dontcallmedom, @marcoscaceres)
-
BREAKING CHANGE: WakeLockTypeNotSupported -> NotSupportedError w3c/screen-wake-lock#127 (2 comments by @marcoscaceres)
-
w3c/battery
-
1 issue opened.
-
Checks on allowed usage are specced incorrectly w3c/battery#19, by @domenic.
-
-
1 issue received 1 new comment.
w3c/geolocation
-
1 pull request received 1 new comment.
w3c/sensors
-
1 issue opened.
-
Sensor requested sampling Frequency and actual frequency differ at 100Hz w3c/sensors#367, by @janschmutz.
-
-
1 issue received 1 new comment.
-
Sensor requested sampling Frequency and actual frequency differ at 100Hz w3c/sensors#367 (1 comment by @reillyeon)
-
Lifecycle
-
1 charter started.
-
Chartered until 30 June 2020. Participants had to rejoin under this charter.
-
Participants
-
1 participant joined.
-
Fuqiao Xue (W3C) joined.
-
-
6 participants left.
-
Fuqiao Xue (W3C) left.
-
Raphael Spreitzer (W3C Invited Experts) left.
-
Lukasz Olejnik (W3C Invited Experts) left.
-
Frederick Hirsch (W3C Invited Experts) left.
-
Dominique Hazaël-Massieux (W3C) left.
-
Dave Raggett (W3C) left.
-
-
21 organizations left.
-
Lawrence Berkeley National Laboratory left.
-
Bocoup left.
-
Trust1Team left.
-
CoSMo Software Consulting Pte Ltd left.
-
Mitsubishi Electric Corporation left.
-
Ecole Mohammadia d'Ingenieurs Rabat (EMI) left.
-
Sony Group Corporation left.
-
Orange left.
-
Qualcomm Innovation Center, Inc left.
-
OpenJS Foundation left.
-
Deutsche Telekom AG left.
-
Alibaba Group left.
-
Mozilla Foundation left.
-
Yandex left.
-
Fraunhofer Gesellschaft left.
-
Electronics and Telecommunications Research Institute (ETRI) left.
-
MITRE Corporation left.
-
LG Electronics left.
-
Tencent left.
-
Google LLC left.
-
Intel Corporation left.
-
GitHub
w3c/das-wg
-
1 pull request merged.
-
recharter w3c/das-wg#18.
-
w3c/sensors
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Update web-platform-tests URLs w3c/sensors#366, by @foolip.
-
-
1 pull request merged.
-
Update web-platform-tests URLs w3c/sensors#366.
-
-
1 pull request received 2 new comments.
w3c/das-charter
-
2 issues closed.
-
Mention a11y? w3c/das-charter#70.
-
Add the remaining deliverables to the timeline? w3c/das-charter#69.
-
-
2 issues received 2 new comments.
-
5 pull requests opened.
-
Changes from ac review 2018 w3c/das-charter#75, by @xfq.
-
adding disposition of comments from charter review w3c/das-charter#74, by @samuelweiler.
-
refine consent requirements w3c/das-charter#73, by @samuelweiler.
-
update change log w3c/das-charter#72, by @samuelweiler.
-
accessiblity/privacy requirements w3c/das-charter#71, by @samuelweiler.
-
-
5 pull requests merged.
-
Changes from ac review 2018 w3c/das-charter#75.
-
adding disposition of comments from charter review w3c/das-charter#74.
-
refine consent requirements w3c/das-charter#73.
-
update change log w3c/das-charter#72.
-
accessiblity/privacy requirements w3c/das-charter#71.
-
w3c/html-media-capture
-
1 issue opened.
-
Privacy concerns w3c/html-media-capture#31, by @LJWatson.
-
-
1 pull request opened.
-
Update web-platform-tests URLs w3c/html-media-capture#30, by @foolip.
-
-
1 pull request merged.
-
Update web-platform-tests URLs w3c/html-media-capture#30.
-
w3c/geolocation
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Update web-platform-tests URLs w3c/geolocation#17, by @foolip.
-
w3c/magnetometer
-
1 pull request opened.
-
Update web-platform-tests URLs w3c/magnetometer#48, by @foolip.
-
-
1 pull request merged.
-
Update web-platform-tests URLs w3c/magnetometer#48.
-
w3c/proximity
-
1 pull request opened.
-
Update web-platform-tests URLs w3c/proximity#35, by @foolip.
-
-
1 pull request merged.
-
Update web-platform-tests URLs w3c/proximity#35.
-
w3c/vibration
-
1 pull request opened.
-
Update web-platform-tests URLs w3c/vibration#22, by @foolip.
-
-
1 pull request merged.
-
Update web-platform-tests URLs w3c/vibration#22.
-
w3c/battery
-
1 pull request opened.
-
Update web-platform-tests URLs w3c/battery#18, by @foolip.
-
-
1 pull request merged.
-
Update web-platform-tests URLs w3c/battery#18.
-
w3c/ambient-light
-
1 pull request opened.
-
Update web-platform-tests URLs w3c/ambient-light#52, by @foolip.
-
-
1 pull request merged.
-
Update web-platform-tests URLs w3c/ambient-light#52.
-
w3c/accelerometer
-
1 pull request opened.
-
Update web-platform-tests URLs w3c/accelerometer#47, by @foolip.
-
-
1 pull request merged.
-
Update web-platform-tests URLs w3c/accelerometer#47.
-
w3c/gyroscope
-
1 pull request opened.
-
Update web-platform-tests URLs w3c/gyroscope#39, by @foolip.
-
-
1 pull request merged.
-
Update web-platform-tests URLs w3c/gyroscope#39.
-
w3c/orientation-sensor
-
1 pull request opened.
-
Update web-platform-tests URLs w3c/orientation-sensor#59, by @foolip.
-
-
1 pull request merged.
-
Update web-platform-tests URLs w3c/orientation-sensor#59.
-
w3c/deviceorientation
-
1 issue received 6 new comments.
-
devicemotion: rotationRate is not implemented according to specification w3c/deviceorientation#44 (6 comments by @andybloch, @anssiko, @reillyeon)
-
-
1 pull request received 1 new comment.
-
update rotationRate alpha, beta, gamma description to be the same as implementation w3c/deviceorientation#43 (1 comment by @andybloch)
-
Participants
-
1 organization joined.
-
Lawrence Berkeley National Laboratory joined.
-
-
1 organization left.
-
Samsung Electronics Co., Ltd. left.
-
GitHub
w3c/geolocation
-
1 issue opened.
-
Support geolocation (especially geofencing) in the "background" w3c/geolocation#214, by @kenchris.
-
-
1 issue received 1 new comment.
-
Support geolocation (especially geofencing) in the "background" w3c/geolocation#214 (1 comment by @jakearchibald)
-
w3c/sensors
-
1 issue opened.
-
Support sensors (think step counter) running in the "background" w3c/sensors#365, by @kenchris.
-
-
1 pull request opened.
-
Fix typo: s/ineracts/interacts w3c/sensors#364, by @Honry.
-
-
1 pull request merged.
-
Fix typo: s/ineracts/interacts w3c/sensors#364.
-
-
1 pull request received 1 new comment.
w3c/battery
-
1 issue closed.
-
getBattery() spec doesn't make sense w3c/battery#16.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Always return promise in getBattery() w3c/battery#17, by @anssiko.
-
-
1 pull request merged.
-
Always return promise in getBattery() w3c/battery#17.
-
-
1 pull request received 4 new comments.
w3c/das-charter
-
2 issues opened.
-
Mention a11y? w3c/das-charter#70, by @xfq.
-
Add the remaining deliverables to the timeline? w3c/das-charter#69, by @xfq.
-
-
1 issue received 2 new comments.
w3c/contact-picker
-
1 issue received 2 new comments.
-
ContactAddress 'region' inconsistencies w3c/contact-picker#65 (2 comments by @marcoscaceres, @mnoorenberghe)
-
w3c/das-wg
-
2 issues opened.
-
Edge renders roadmap maturity stages in wrong orientation w3c/das-wg#17, by @anssiko.
-
Accessibility issues w3c/das-wg#15, by @anssiko.
-
-
1 issue closed.
-
Accessibility issues w3c/das-wg#15.
-
-
1 issue received 2 new comments.
-
1 pull request opened.
-
Center the link inside a "table cell" w3c/das-wg#16, by @xfq.
-
-
1 pull request merged.
-
Center the link inside a "table cell" w3c/das-wg#16.
-
-
1 pull request received 2 new comments.
GitHub
w3c/contact-picker
-
1 issue received 1 new comment.
w3c/sensors
-
2 issues opened.
-
Define WebDriver extension API for test automation w3c/sensors#363, by @Honry.
-
Usage of "concrete" w3c/sensors#362, by @dontcallmedom.
-
-
2 issues received 12 new comments.
-
Define WebDriver extension API for test automation w3c/sensors#363 (11 comments by @alexshalamov, @foolip, @Honry, @kereliuk, @reillyeon)
-
w3c/screen-wake-lock
-
1 issue opened.
-
Introduce rate limiting to prevent wake lock abuse w3c/screen-wake-lock#124, by @arturjanc.
-
-
1 issue received 2 new comments.
-
Introduce rate limiting to prevent wake lock abuse w3c/screen-wake-lock#124 (2 comments by @andrey-logvinov)
-
-
1 pull request opened.
-
Restrict status reporting for wake lock w3c/screen-wake-lock#125, by @andrey-logvinov.
-
-
1 pull request received 1 new comment.
w3c/battery
-
1 issue opened.
-
getBattery() spec doesn't make sense w3c/battery#16, by @bzbarsky.
-
-
1 issue received 3 new comments.
w3c/das-wg
-
1 pull request opened.
-
Add PR/Rec milestone guesstimates w3c/das-wg#14, by @anssiko.
-
-
1 pull request merged.
-
Add PR/Rec milestone guesstimates w3c/das-wg#14.
-
-
1 pull request received 2 new comments.
w3c/das-charter
-
4 pull requests opened.
-
Dom stepped down as team contact w3c/das-charter#68, by @xfq.
-
Minor editorial fixes w3c/das-charter#67, by @xfq.
-
Update links to the Process w3c/das-charter#66, by @xfq.
-
Update the dates after the charter extension w3c/das-charter#65, by @xfq.
-
-
5 pull requests merged.
-
Dom stepped down as team contact w3c/das-charter#68.
-
Add Reilly Grant as co-chair in the draft charter w3c/das-charter#63.
-
Update the dates after the charter extension w3c/das-charter#65.
-
Update links to the Process w3c/das-charter#66.
-
Minor editorial fixes w3c/das-charter#67.
-
w3c/html-media-capture
-
1 issue opened.
-
Upstream HTML Media Capture to HTML? w3c/html-media-capture#28, by @xfq.
-
-
1 issue closed.
-
[meta] Translations tracker w3c/html-media-capture#27.
-
-
2 issues received 4 new comments.
-
1 pull request opened.
-
Link to translations w3c/html-media-capture#29, by @xfq.
-
-
1 pull request merged.
-
Link to translations w3c/html-media-capture#29.
-
TR publications
-
6 documents published.
-
Accelerometer published as a Candidate Recommendation Snapshot. History of Accelerometer
-
Ambient Light Sensor published as a Candidate Recommendation Snapshot. History of Ambient Light Sensor
-
Generic Sensor API published as a Candidate Recommendation Snapshot. History of Generic Sensor API
-
Gyroscope published as a Candidate Recommendation Snapshot. History of Gyroscope
-
Magnetometer published as a Candidate Recommendation Snapshot. History of Magnetometer
-
Orientation Sensor published as a Candidate Recommendation Snapshot. History of Orientation Sensor
-
GitHub
w3c/das-charter
-
3 pull requests opened.
-
Fix validation warnings w3c/das-charter#64, by @xfq.
-
Add Reilly Grant as co-chair in the draft charter w3c/das-charter#63, by @xfq.
-
Update Sensor APIs state to CR w3c/das-charter#62, by @anssiko.
-
-
2 pull requests merged.
-
Fix validation warnings w3c/das-charter#64.
-
Update Sensor APIs state to CR w3c/das-charter#62.
-
-
2 pull requests received 3 new comments.
w3c/das-wg
-
2 pull requests opened.
-
Add test results w3c/das-wg#13, by @anssiko.
-
Update the roadmap w3c/das-wg#12, by @anssiko.
-
-
2 pull requests merged.
-
Add test results w3c/das-wg#13.
-
Update the roadmap w3c/das-wg#12.
-
w3c/sensors
-
4 issues opened.
-
Define mechanism for forward compatibility checks w3c/sensors#361, by @alexshalamov.
-
[meta] Sensor APIs Candidate Recommendation readiness tracker w3c/sensors#355, by @anssiko.
-
Make [SECURITY-PRIVACY-QUESTIONNAIRE] informative reference w3c/sensors#354, by @anssiko.
-
Improve guidance on UI for user consenting w3c/sensors#352, by @anssiko.
-
-
3 issues closed.
-
[meta] Sensor APIs Candidate Recommendation readiness tracker w3c/sensors#355.
-
Make [SECURITY-PRIVACY-QUESTIONNAIRE] informative reference w3c/sensors#354.
-
Improve guidance on UI for user consenting w3c/sensors#352.
-
-
3 issues received 13 new comments.
-
Improve guidance on UI for user consenting w3c/sensors#352 (8 comments by @alexshalamov, @annevk, @anssiko)
-
[meta] Sensor APIs Candidate Recommendation readiness tracker w3c/sensors#355 (4 comments by @anssiko, @xfq)
-
-
10 pull requests opened.
-
Add a note for unsupported sensor options w3c/sensors#360, by @pozdnyakov.
-
Avoid one more redundant redirect w3c/sensors#359, by @anssiko.
-
Fix broken links and fragments, avoid redundant redirects w3c/sensors#358, by @anssiko.
-
Update [SECURITY-PRIVACY-QUESTIONNAIRE] reference to match its status w3c/sensors#357, by @anssiko.
-
Throw 'NotSupportedError' for an unsupported sensor option w3c/sensors#356, by @pozdnyakov.
-
Improve guidance on UI for user consenting w3c/sensors#353, by @anssiko.
-
Fix links for "permission names" w3c/sensors#351, by @alexshalamov.
-
Fix the 'permission name' link w3c/sensors#350, by @pozdnyakov.
-
Update the "Losing Focus" mitigation strategy w3c/sensors#349, by @pozdnyakov.
-
Clarify concepts section w3c/sensors#348, by @anssiko.
-
-
10 pull requests merged.
-
Add a note for unsupported sensor options w3c/sensors#360.
-
Avoid one more redundant redirect w3c/sensors#359.
-
Fix broken links and fragments, avoid redundant redirects w3c/sensors#358.
-
Throw 'NotSupportedError' for an unsupported sensor option w3c/sensors#356.
-
Improve guidance on UI for user consenting w3c/sensors#353.
-
Update the "Losing Focus" mitigation strategy w3c/sensors#349.
-
Fix the 'permission name' link w3c/sensors#350.
-
Clarify concepts section w3c/sensors#348.
-
Clarify the conditions to expose sensor readings w3c/sensors#347.
-
-
1 pull request closed.
-
Fix links for "permission names" w3c/sensors#351.
-
-
8 pull requests received 53 new comments.
-
Throw 'NotSupportedError' for an unsupported sensor option w3c/sensors#356 (10 comments by @anssiko, @Honry, @pozdnyakov)
-
Update the "Losing Focus" mitigation strategy w3c/sensors#349 (5 comments by @kenchris, @pozdnyakov)
w3c/battery
-
1 pull request received 3 new comments.
-
Allow use in same-origin children, add Feature Policy integration w3c/battery#13 (3 comments by @anssiko, @RByers)
-
w3c/contact-picker
-
1 issue received 2 new comments.
-
ContactAddress 'region' inconsistencies w3c/contact-picker#65 (2 comments by @mnoorenberghe, @stpeter)
-
w3c/ambient-light
-
2 pull requests opened.
-
Fix broken fragments, avoid redundant redirects w3c/ambient-light#51, by @anssiko.
-
Use "sensor permission name" w3c/ambient-light#50, by @anssiko.
-
-
3 pull requests merged.
-
Fix broken fragments, avoid redundant redirects w3c/ambient-light#51.
-
Use "sensor permission name" w3c/ambient-light#50.
-
Reword security and privacy section w3c/ambient-light#49.
-
-
2 pull requests received 2 new comments.
w3c/accelerometer
-
1 issue opened.
-
Duplicate definition of LocalCoordinateSystem w3c/accelerometer#41, by @dontcallmedom.
-
-
2 issues closed.
-
Should we throw exception when screen coordinate system is not supported? w3c/accelerometer#35.
-
Duplicate definition of LocalCoordinateSystem w3c/accelerometer#41.
-
-
3 issues received 6 new comments.
-
Should we throw exception when screen coordinate system is not supported? w3c/accelerometer#35 (3 comments by @anssiko, @pozdnyakov)
-
Duplicate definition of LocalCoordinateSystem w3c/accelerometer#41 (2 comments by @anssiko, @rakuco)
-
Include Known Accelerometer Privacy Exposures in Accelerometer Document w3c/accelerometer#30 (1 comment by @anssiko)
-
-
7 pull requests opened.
-
Fix broken links and fragments, avoid redundant redirects w3c/accelerometer#46, by @anssiko.
-
Specify supported sensor options for Accelerometer interfaces w3c/accelerometer#45, by @alexshalamov.
-
Remove some extra whitespace in IDL w3c/accelerometer#44, by @anssiko.
-
Remove some extra whitespace in IDL w3c/accelerometer#43, by @foolip.
-
Prefix coordinate system enum w3c/accelerometer#42, by @alexshalamov.
-
Use "sensor permission name" w3c/accelerometer#40, by @anssiko.
-
Fix typo ligitimate => legitimate w3c/accelerometer#39, by @alexshalamov.
-
-
6 pull requests merged.
-
Fix broken links and fragments, avoid redundant redirects w3c/accelerometer#46.
-
Specify supported sensor options for Accelerometer interfaces w3c/accelerometer#45.
-
Remove some extra whitespace in IDL w3c/accelerometer#44.
-
Prefix coordinate system enum w3c/accelerometer#42.
-
Use "sensor permission name" w3c/accelerometer#40.
-
Fix typo ligitimate => legitimate w3c/accelerometer#39.
-
-
1 pull request closed.
-
Remove some extra whitespace in IDL w3c/accelerometer#43.
-
-
2 pull requests received 9 new comments.
-
Use "sensor permission name" w3c/accelerometer#40 (7 comments by @alexshalamov, @anssiko, @pozdnyakov, @riju)
-
w3c/magnetometer
-
6 pull requests opened.
-
Editorial pass, update informative references, fix broken links w3c/magnetometer#47, by @anssiko.
-
Define supported sensor options w3c/magnetometer#46, by @anssiko.
-
Prefix coordinate system enum w3c/magnetometer#45, by @anssiko.
-
Fix stray whitespace in IDL. w3c/magnetometer#44, by @riju.
-
Remove stray whitespace in IDL w3c/magnetometer#43, by @foolip.
-
Use "sensor permission name" w3c/magnetometer#42, by @anssiko.
-
-
6 pull requests merged.
-
Editorial pass, update informative references, fix broken links w3c/magnetometer#47.
-
Define supported sensor options w3c/magnetometer#46.
-
Prefix coordinate system enum w3c/magnetometer#45.
-
Fix stray whitespace in IDL. w3c/magnetometer#44.
-
Remove stray whitespace in IDL w3c/magnetometer#43.
-
Use "sensor permission name" w3c/magnetometer#42.
-
-
3 pull requests received 6 new comments.
-
Editorial pass, update informative references, fix broken links w3c/magnetometer#47 (4 comments by @anssiko, @riju)
-
w3c/gyroscope
-
1 issue closed.
-
Construct a gyroscope object w3c/gyroscope#30.
-
-
2 issues received 2 new comments.
-
Include Known Gyroscope Privacy Exposures in Gyroscope Document w3c/gyroscope#27 (1 comment by @anssiko)
-
-
7 pull requests opened.
-
Fix broken fragments, avoid redundant redirects w3c/gyroscope#38, by @anssiko.
-
Define supported sensor options w3c/gyroscope#37, by @pozdnyakov.
-
Remove extra whitespace in IDL w3c/gyroscope#36, by @anssiko.
-
Remove extra whitespace in IDL w3c/gyroscope#35, by @foolip.
-
Prefix coordinate system enum w3c/gyroscope#34, by @pozdnyakov.
-
Reword security and privacy section w3c/gyroscope#33, by @pozdnyakov.
-
Use "sensor permission name" w3c/gyroscope#32, by @anssiko.
-
-
6 pull requests merged.
-
Fix broken fragments, avoid redundant redirects w3c/gyroscope#38.
-
Define supported sensor options w3c/gyroscope#37.
-
Remove extra whitespace in IDL w3c/gyroscope#36.
-
Prefix coordinate system enum w3c/gyroscope#34.
-
Reword security and privacy section w3c/gyroscope#33.
-
Use "sensor permission name" w3c/gyroscope#32.
-
-
1 pull request closed.
-
Remove extra whitespace in IDL w3c/gyroscope#35.
-
-
4 pull requests received 5 new comments.
w3c/orientation-sensor
-
2 issues received 2 new comments.
-
Should OrientationSensor interface provide Euler angles? w3c/orientation-sensor#43 (1 comment by @anssiko)
-
4 pull requests opened.
-
Fix broken fragments, avoid redundant redirects w3c/orientation-sensor#58, by @anssiko.
-
Define supported sensor options w3c/orientation-sensor#57, by @pozdnyakov.
-
Prefix coordinate system enum w3c/orientation-sensor#56, by @anssiko.
-
Fix stray whitespace in IDL w3c/orientation-sensor#55, by @Honry.
-
-
4 pull requests merged.
-
Fix broken fragments, avoid redundant redirects w3c/orientation-sensor#58.
-
Define supported sensor options w3c/orientation-sensor#57.
-
Prefix coordinate system enum w3c/orientation-sensor#56.
-
Fix stray whitespace in IDL w3c/orientation-sensor#55.
-
-
2 pull requests received 5 new comments.
w3c/proximity
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Reword security and privacy section and propose mitigation strategies w3c/proximity#34, by @alexshalamov.
-
-
1 pull request merged.
-
Reword security and privacy section and propose mitigation strategies w3c/proximity#34.
-
TR publications
-
1 document published.
-
HTML Media Capture published as a Recommendation. History of HTML Media Capture
-
GitHub
w3c/accelerometer
-
1 issue opened.
-
Should we throw exception when screen coordinate system is not supported? w3c/accelerometer#35, by @alexshalamov.
-
-
1 issue closed.
-
Include Known Accelerometer Privacy Exposures in Accelerometer Document w3c/accelerometer#30.
-
-
2 issues received 7 new comments.
-
Should we throw exception when screen coordinate system is not supported? w3c/accelerometer#35 (5 comments by @alexshalamov, @anssiko, @pozdnyakov)
-
Include Known Accelerometer Privacy Exposures in Accelerometer Document w3c/accelerometer#30 (2 comments by @alexshalamov, @anssiko)
-
-
6 pull requests opened.
-
Reword security and privacy section w3c/accelerometer#38, by @alexshalamov.
-
Use newly introduced "initialize a sensor object" operation w3c/accelerometer#37, by @alexshalamov.
-
Add AccelerometerSensorOptions dictionary and align definitions w3c/accelerometer#36, by @alexshalamov.
-
Align reference frame definition w3c/accelerometer#34, by @alexshalamov.
-
Add illustrations and examples w3c/accelerometer#33, by @alexshalamov.
-
Fix link to 'local coordinate system' w3c/accelerometer#32, by @pozdnyakov.
-
-
7 pull requests merged.
-
Reword security and privacy section w3c/accelerometer#38.
-
Use newly introduced "initialize a sensor object" operation w3c/accelerometer#37.
-
Add AccelerometerSensorOptions dictionary and align definitions w3c/accelerometer#36.
-
Align reference frame definition w3c/accelerometer#34.
-
Add illustrations and examples w3c/accelerometer#33.
-
Fix link to 'local coordinate system' w3c/accelerometer#32.
-
Screen and Device local coordinates w3c/accelerometer#31.
-
-
5 pull requests received 32 new comments.
-
Align reference frame definition w3c/accelerometer#34 (4 comments by @alexshalamov, @anssiko, @pozdnyakov)
-
Add AccelerometerSensorOptions dictionary and align definitions w3c/accelerometer#36 (1 comment by @alexshalamov)
w3c/ambient-light
-
2 pull requests opened.
-
Reword security and privacy section w3c/ambient-light#49, by @alexshalamov.
-
Use newly introduced "initialize a sensor object" operation w3c/ambient-light#48, by @anssiko.
-
-
1 pull request merged.
-
Use newly introduced "initialize a sensor object" operation w3c/ambient-light#48.
-
w3c/sensors
-
1 issue opened.
-
Clarify construction of subclasses w3c/sensors#342, by @anssiko.
-
-
3 issues closed.
-
Clarify construction of subclasses w3c/sensors#342.
-
Add more complete examples to the Feature Detection section w3c/sensors#339.
-
Investigate possibility of synchronizing coordinate systems w3c/sensors#257.
-
-
4 issues received 10 new comments.
-
Investigate possibility of synchronizing coordinate systems w3c/sensors#257 (5 comments by @anssiko, @Honry, @pozdnyakov, @rakuco)
-
Sensor.frequency needs to be setable to allow frequency adaptation w3c/sensors#63 (2 comments by @anssiko)
-
Javascript 120Hz devicemotion events for high end inertial applications w3c/sensors#98 (2 comments by @adonikian, @saabi)
-
-
6 pull requests opened.
-
Clarify the conditions to expose sensor readings w3c/sensors#347, by @pozdnyakov.
-
Add reference to device fingerprinting research paper w3c/sensors#346, by @alexshalamov.
-
Clarify construction of subclasses w3c/sensors#345, by @pozdnyakov.
-
Clarify construction of subclasses w3c/sensors#344, by @pozdnyakov.
-
Fix generation error for document metadata w3c/sensors#343, by @alexshalamov.
-
Update feature detection example w3c/sensors#341, by @alexshalamov.
-
-
6 pull requests merged.
-
Add reference to device fingerprinting research paper w3c/sensors#346.
-
Clarify construction of subclasses w3c/sensors#345.
-
Fix generation error for document metadata w3c/sensors#343.
-
Update feature detection example w3c/sensors#341.
-
Update Rick Waldron affiliation w3c/sensors#326.
-
Add "Local Coordinate System" concept w3c/sensors#340.
-
-
1 pull request closed.
-
Clarify construction of subclasses w3c/sensors#344.
-
-
6 pull requests received 41 new comments.
-
Update feature detection example w3c/sensors#341 (18 comments by @alexshalamov, @anssiko, @kenchris)
-
Clarify the conditions to expose sensor readings w3c/sensors#347 (3 comments by @alexshalamov, @anssiko)
-
w3c/orientation-sensor
-
2 pull requests opened.
-
Use newly introduced "initialize a sensor object" operation w3c/orientation-sensor#54, by @anssiko.
-
Orientation sensors can use the screen local coordinates w3c/orientation-sensor#53, by @pozdnyakov.
-
-
2 pull requests merged.
-
Use newly introduced "initialize a sensor object" operation w3c/orientation-sensor#54.
-
Orientation sensors can use the screen local coordinates w3c/orientation-sensor#53.
-
-
2 pull requests received 5 new comments.
-
Use newly introduced "initialize a sensor object" operation w3c/orientation-sensor#54 (3 comments by @anssiko, @pozdnyakov)
-
Orientation sensors can use the screen local coordinates w3c/orientation-sensor#53 (2 comments by @kenchris, @pozdnyakov)
-
w3c/gyroscope
-
1 issue opened.
-
Construct a gyroscope object w3c/gyroscope#30, by @anssiko.
-
-
1 issue closed.
-
Include Known Gyroscope Privacy Exposures in Gyroscope Document w3c/gyroscope#27.
-
-
1 issue received 1 new comment.
-
Include Known Gyroscope Privacy Exposures in Gyroscope Document w3c/gyroscope#27 (1 comment by @anssiko)
-
-
3 pull requests opened.
-
Update the Gyroscope construction w3c/gyroscope#31, by @pozdnyakov.
-
Gyroscope-specific construction operation and construction options w3c/gyroscope#29, by @pozdnyakov.
-
Gyroscope can use the screen local coordinates w3c/gyroscope#28, by @pozdnyakov.
-
-
3 pull requests merged.
-
Update the Gyroscope construction w3c/gyroscope#31.
-
Gyroscope-specific construction operation and construction options w3c/gyroscope#29.
-
Gyroscope can use the screen local coordinates w3c/gyroscope#28.
-
-
3 pull requests received 9 new comments.
-
Gyroscope-specific construction operation and construction options w3c/gyroscope#29 (4 comments by @alexshalamov, @anssiko, @pozdnyakov)
w3c/magnetometer
-
3 pull requests opened.
-
Add keystroke monitoring threat w3c/magnetometer#41, by @alexshalamov.
-
Use newly introduced "initialize a sensor object" operation w3c/magnetometer#40, by @anssiko.
-
Magnetometer can use the screen local coordinates w3c/magnetometer#39, by @alexshalamov.
-
-
3 pull requests merged.
-
Add keystroke monitoring threat w3c/magnetometer#41.
-
Use newly introduced "initialize a sensor object" operation w3c/magnetometer#40.
-
Magnetometer can use the screen local coordinates w3c/magnetometer#39.
-
-
3 pull requests received 17 new comments.
-
Magnetometer can use the screen local coordinates w3c/magnetometer#39 (11 comments by @alexshalamov, @anssiko, @pozdnyakov, @riju)
-
Use newly introduced "initialize a sensor object" operation w3c/magnetometer#40 (4 comments by @alexshalamov, @anssiko, @pozdnyakov)
-
w3c/proximity
-
1 pull request opened.
-
Use newly introduced "initialize a sensor object" operation. w3c/proximity#33, by @riju.
-
-
1 pull request merged.
-
Use newly introduced "initialize a sensor object" operation. w3c/proximity#33.
-
-
1 pull request received 2 new comments.
-
Use newly introduced "initialize a sensor object" operation. w3c/proximity#33 (2 comments by @anssiko, @riju)
-
w3c/html-media-capture
-
5 issues opened.
-
[meta] Translations tracker w3c/html-media-capture#27, by @anssiko.
-
Obsolete link? w3c/html-media-capture#26, by @Kirill-Johnson.
-
Minor issue: superfluous dot w3c/html-media-capture#25, by @Kirill-Johnson.
-
Android: compress videos before uploading w3c/html-media-capture#24, by @octavn.
-
Limit the length of the recorded video w3c/html-media-capture#23, by @octavn.
-
-
2 issues closed.
-
Minor issue: superfluous dot w3c/html-media-capture#25.
-
Obsolete link? w3c/html-media-capture#26.
-
-
5 issues received 7 new comments.
-
1 pull request opened.
-
Make ED reflect TR w3c/html-media-capture#22, by @anssiko.
-
-
1 pull request merged.
-
Make ED reflect TR w3c/html-media-capture#22.
-
-
1 pull request closed.
-
Stage PR snapshot w3c/html-media-capture#21.
-
-
2 pull requests received 2 new comments.
w3c/battery
-
1 issue received 4 new comments.
w3c/das-charter
-
1 pull request opened.
-
Update HTML Media Capture state to REC w3c/das-charter#61, by @xfq.
-
-
1 pull request merged.
-
Update HTML Media Capture state to REC w3c/das-charter#61.
-
-
1 pull request received 1 new comment.
w3c/geolocation
-
1 issue closed.
-
Only allow to ask for location on user interaction w3c/geolocation#16.
-
-
1 issue received 3 new comments.
-
Only allow to ask for location on user interaction w3c/geolocation#16 (3 comments by @jimmywarting, @plehegar)
-
w3c/das-wg
-
1 pull request opened.
-
Update the roadmap w3c/das-wg#11, by @anssiko.
-
-
1 pull request merged.
-
Update the roadmap w3c/das-wg#11.
-
-
1 pull request received 1 new comment.
GitHub
w3c/accelerometer
-
1 issue opened.
-
Include Known Accelerometer Privacy Exposures in Accelerometer Document w3c/accelerometer#30, by @jasonanovak.
-
-
1 pull request opened.
-
Screen and Device local coordinates w3c/accelerometer#31, by @pozdnyakov.
-
-
1 pull request received 23 new comments.
-
Screen and Device local coordinates w3c/accelerometer#31 (23 comments by @alexshalamov, @anssiko, @kenchris, @pozdnyakov)
-
w3c/sensors
-
1 issue opened.
-
Add more complete examples to the Feature Detection section w3c/sensors#339, by @anssiko.
-
-
2 issues received 26 new comments.
-
Investigate possibility of synchronizing coordinate systems w3c/sensors#257 (25 comments by @alexshalamov, @anssiko, @kenchris, @pozdnyakov)
-
-
1 pull request opened.
-
Add "Local Coordinate System" concept w3c/sensors#340, by @pozdnyakov.
-
-
2 pull requests received 9 new comments.
-
Add "Local Coordinate System" concept w3c/sensors#340 (8 comments by @alexshalamov, @anssiko, @kenchris, @pozdnyakov)
-
w3c/contact-picker
-
1 issue opened.
-
Add latitude and longitude to ContactAddress interface? w3c/contact-picker#72, by @stpeter.
-
-
2 issues received 9 new comments.
-
ContactAddress 'region' inconsistencies w3c/contact-picker#65 (5 comments by @marcoscaceres, @mnoorenberghe, @sebsg, @TSMatthews)
-
Add payerGivenName + payerFamilyName to PaymentAddress w3c/contact-picker#69 (4 comments by @aphillips, @marcoscaceres, @stpeter)
-
w3c/battery
-
1 issue received 3 new comments.
-
1 pull request received 6 new comments.
-
Allow use in same-origin children, add Feature Policy integration w3c/battery#13 (6 comments by @anssiko, @clelland, @mounirlamouri)
-
w3c/proximity
-
3 issues opened.
-
Missing PermissionName definition w3c/proximity#32, by @xiuqijix.
-
What's the distance value when the visible surface is beyond the max value? w3c/proximity#30, by @xiuqijix.
-
What's the initial value of near attribute? w3c/proximity#29, by @xiuqijix.
-
-
2 issues closed.
-
What's the initial value of near attribute? w3c/proximity#29.
-
3 issues received 12 new comments.
-
What's the distance value when the visible surface is beyond the max value? w3c/proximity#30 (5 comments by @anssiko, @riju, @xiuqijix)
-
What's the initial value of near attribute? w3c/proximity#29 (5 comments by @anssiko, @Honry, @riju, @xiuqijix)
-
-
1 pull request opened.
-
Clarify distance and near behavior when outside the sensing range w3c/proximity#31, by @anssiko.
-
-
1 pull request merged.
-
Clarify distance and near behavior when outside the sensing range w3c/proximity#31.
-
-
1 pull request received 5 new comments.
-
Clarify distance and near behavior when outside the sensing range w3c/proximity#31 (5 comments by @anssiko, @Honry, @xiuqijix)
-
w3c/gyroscope
-
1 issue opened.
-
Include Known Gyroscope Privacy Exposures in Gyroscope Document w3c/gyroscope#27, by @jasonanovak.
-