Devices and Sensors Working Group - Activity in 2023
No matches.
TR publications
-
5 documents published.
-
Gyroscope published as a Candidate Recommendation Draft. History of Gyroscope
-
Compute Pressure Level 1 published as a Working Draft. History of Compute Pressure Level 1
-
DeviceOrientation Event Specification published 3 times as a Working Draft. History of DeviceOrientation Event Specification
-
GitHub
w3c/sensors
-
1 issue received 3 new comments.
w3c/compute-pressure
-
1 issue opened.
-
Exposing low-level metrics via permissions w3c/compute-pressure#246, by @DenizUgur.
-
-
3 issues closed.
-
Security and privacy review tracker w3c/compute-pressure#79.
-
Accessibility Checklist w3c/compute-pressure#183.
-
Internationalization Checklist w3c/compute-pressure#184.
-
-
5 issues received 8 new comments.
-
Exposing low-level metrics via permissions w3c/compute-pressure#246 (2 comments by @anssiko, @DenizUgur)
-
2 pull requests opened.
-
Add Accessibility considerations w3c/compute-pressure#247, by @anssiko.
-
Update security and privacy self assesment documents w3c/compute-pressure#245, by @arskama.
-
-
2 pull requests merged.
-
Add Accessibility considerations w3c/compute-pressure#247.
-
Update security and privacy self assesment documents w3c/compute-pressure#245.
-
-
1 pull request received 1 new comment.
w3c/screen-wake-lock
-
1 issue received 2 new comments.
-
Clarify use cases in Screen Brightness API explainer w3c/screen-wake-lock#341 (2 comments by @anssiko, @marcoscaceres)
-
-
3 pull requests opened.
-
Remove redundant check w3c/screen-wake-lock#368, by @marcoscaceres.
-
Add doc is fully active check w3c/screen-wake-lock#367, by @marcoscaceres.
-
Remove permission check w3c/screen-wake-lock#366, by @marcoscaceres.
-
-
3 pull requests received 4 new comments.
w3c/deviceorientation
-
2 issues closed.
-
Add integration with Permissions Policy w3c/deviceorientation#64.
-
Add integration with the Permissions API w3c/deviceorientation#70.
-
-
3 pull requests opened.
-
Simplify readme w3c/deviceorientation#127, by @anssiko.
-
Add Security and Privacy Self-Review Questionnaire w3c/deviceorientation#126, by @anssiko.
-
Add Changes section w3c/deviceorientation#125, by @anssiko.
-
-
4 pull requests merged.
-
Simplify readme w3c/deviceorientation#127.
-
Add Changes section w3c/deviceorientation#125.
-
Add Permissions Policy integration w3c/deviceorientation#121.
-
Add Permissions API integration, start requiring requestPermission() usage w3c/deviceorientation#123.
-
-
5 pull requests received 22 new comments.
-
Add Security and Privacy Self-Review Questionnaire w3c/deviceorientation#126 (10 comments by @anssiko, @reillyeon)
-
Add Permissions API integration, start requiring requestPermission() usage w3c/deviceorientation#123 (3 comments by @anssiko, @rakuco)
-
w3c/orientation-sensor
-
1 pull request opened.
-
Automation: integrate with Device Orientation API's Automation section w3c/orientation-sensor#83, by @rakuco.
-
-
1 pull request received 3 new comments.
-
Automation: integrate with Device Orientation API's Automation section w3c/orientation-sensor#83 (3 comments by @rakuco, @reillyeon)
-
w3c/geolocation
-
1 issue opened.
-
need help- with the use of geolocation how can i make a tracking device w3c/geolocation#140, by @git-krishnabisht.
-
-
1 issue closed.
-
need help- with the use of geolocation how can i make a tracking device w3c/geolocation#140.
-
-
2 issues received 2 new comments.
-
Support geolocation (especially geofencing) in the "background" w3c/geolocation#214 (1 comment by @dlilga)
-
need help- with the use of geolocation how can i make a tracking device w3c/geolocation#140 (1 comment by @anssiko)
-
w3c/gyroscope
-
1 issue opened.
-
Broken references in Gyroscope w3c/gyroscope#58, by @dontcallmedom-bot.
-
-
1 issue closed.
-
Broken references in Gyroscope w3c/gyroscope#58.
-
-
1 pull request merged.
-
Adapt to virtual sensor changes in w3c/sensors#475 w3c/gyroscope#57.
-
-
1 pull request received 3 new comments.
-
Adapt to virtual sensor changes in w3c/sensors#475 w3c/gyroscope#57 (3 comments by @anssiko, @rakuco)
-
TR publications
-
15 documents published.
-
Accelerometer published twice as a Candidate Recommendation Draft. History of Accelerometer
-
Generic Sensor API published as a Candidate Recommendation Draft. History of Generic Sensor API
-
Orientation Sensor published twice as a Working Draft. History of Orientation Sensor
-
Ambient Light Sensor published as a Working Draft. History of Ambient Light Sensor
-
Geolocation Sensor published as a Working Draft. History of Geolocation Sensor
-
Magnetometer published as a Working Draft. History of Magnetometer
-
Proximity Sensor published as a Working Draft. History of Proximity Sensor
-
DeviceOrientation Event Specification published 3 times as a Working Draft. History of DeviceOrientation Event Specification
-
Compute Pressure Level 1 published twice as a Working Draft. History of Compute Pressure Level 1
-
Screen Wake Lock API published as a Working Draft. History of Screen Wake Lock API
-
GitHub
w3c/deviceorientation
-
3 issues opened.
-
Add automation support using WebDriver w3c/deviceorientation#122, by @rakuco.
-
DeviceOrientationEvent.absolute's value when data cannot be obtained w3c/deviceorientation#119, by @rakuco.
-
Behavior when event data cannot be provided is underspecified w3c/deviceorientation#118, by @rakuco.
-
-
4 issues received 16 new comments.
-
Add automation support using WebDriver w3c/deviceorientation#122 (8 comments by @rakuco, @reillyeon)
-
Add integration with Permissions Policy w3c/deviceorientation#64 (5 comments by @rakuco, @reillyeon)
-
Add integration with the Permissions API w3c/deviceorientation#70 (2 comments by @rakuco, @reillyeon)
-
Behavior when event data cannot be provided is underspecified w3c/deviceorientation#118 (1 comment by @reillyeon)
-
-
7 pull requests opened.
-
Add automation support via WebDriver w3c/deviceorientation#124, by @rakuco.
-
Add Permissions API integration, start requiring requestPermission() usage w3c/deviceorientation#123, by @rakuco.
-
Add Permissions Policy integration w3c/deviceorientation#121, by @rakuco.
-
editorial: Define API section more normatively and with more <dfn>s w3c/deviceorientation#120, by @rakuco.
-
editorial: Add a separate section describing model, rewrite contents w3c/deviceorientation#117, by @rakuco.
-
editorial: Refer to [[SCREEN-ORIENTATION]] instead of the orientationchange event w3c/deviceorientation#116, by @rakuco.
-
editorial: Use more precise event handling terms, modernize others w3c/deviceorientation#115, by @rakuco.
-
-
5 pull requests merged.
-
editorial: Define API section more normatively and with more <dfn>s w3c/deviceorientation#120.
-
editorial: Add a separate section describing model, rewrite contents w3c/deviceorientation#117.
-
editorial: Refer to [[SCREEN-ORIENTATION]] instead of the orientationchange event w3c/deviceorientation#116.
-
editorial: Use more precise event handling terms, modernize others w3c/deviceorientation#115.
-
editorial: Reword requirements in "Security and privacy considerations" w3c/deviceorientation#114.
-
-
5 pull requests received 48 new comments.
-
editorial: Define API section more normatively and with more <dfn>s w3c/deviceorientation#120 (10 comments by @reillyeon)
-
editorial: Add a separate section describing model, rewrite contents w3c/deviceorientation#117 (7 comments by @anssiko, @rakuco, @reillyeon)
-
Add Permissions API integration, start requiring requestPermission() usage w3c/deviceorientation#123 (6 comments by @rakuco, @reillyeon)
w3c/sensors
-
1 issue received 2 new comments.
-
1 pull request opened.
-
Automation: Remove "virtual sensor type" from virtual sensor metadata w3c/sensors#475, by @rakuco.
-
-
1 pull request merged.
-
1 pull request received 1 new comment.
-
Automation: Remove "virtual sensor type" from virtual sensor metadata w3c/sensors#475 (1 comment by @rakuco)
-
w3c/screen-wake-lock
-
1 issue received 4 new comments.
-
Require transient activation to request lock w3c/screen-wake-lock#350 (4 comments by @marcoscaceres, @reillyeon, @vinhill)
-
-
1 pull request merged.
-
editorial: Use more precise terms to define WakeLockSentinel.onrelease w3c/screen-wake-lock#365.
-
w3c/accelerometer
-
1 issue opened.
-
Adapt spec to Automation section changes in Generic Sensor API spec w3c/accelerometer#72, by @rakuco.
-
-
1 issue closed.
-
Adapt spec to Automation section changes in Generic Sensor API spec w3c/accelerometer#72.
-
-
2 pull requests opened.
-
Adapt to virtual sensor changes in w3c/sensors#475 w3c/accelerometer#74, by @rakuco.
-
Rewrite Automation section after changes in Generic Sensor API spec w3c/accelerometer#73, by @JuhaVainio.
-
-
2 pull requests merged.
-
Adapt to virtual sensor changes in w3c/sensors#475 w3c/accelerometer#74.
-
Rewrite Automation section after changes in Generic Sensor API spec w3c/accelerometer#73.
-
-
2 pull requests received 3 new comments.
-
Adapt to virtual sensor changes in w3c/sensors#475 w3c/accelerometer#74 (2 comments by @rakuco, @reillyeon)
-
Rewrite Automation section after changes in Generic Sensor API spec w3c/accelerometer#73 (1 comment by @rakuco)
-
w3c/orientation-sensor
-
2 pull requests opened.
-
Adapt to virtual sensor changes in w3c/sensors#475 w3c/orientation-sensor#82, by @rakuco.
-
editorial: Export "Earth's reference coordinate system" <dfn> w3c/orientation-sensor#81, by @rakuco.
-
-
2 pull requests merged.
-
Adapt to virtual sensor changes in w3c/sensors#475 w3c/orientation-sensor#82.
-
editorial: Export "Earth's reference coordinate system" <dfn> w3c/orientation-sensor#81.
-
w3c/proximity
-
1 pull request opened.
-
Adapt to virtual sensor changes in w3c/sensors#475 w3c/proximity#59, by @rakuco.
-
-
1 pull request merged.
-
Adapt to virtual sensor changes in w3c/sensors#475 w3c/proximity#59.
-
w3c/magnetometer
-
2 pull requests opened.
-
Adapt to virtual sensor changes in w3c/sensors#475 w3c/magnetometer#71, by @rakuco.
-
editorial: Use <xmp> tag instead of <pre> in example w3c/magnetometer#70, by @rakuco.
-
-
2 pull requests merged.
-
Adapt to virtual sensor changes in w3c/sensors#475 w3c/magnetometer#71.
-
editorial: Use <xmp> tag instead of <pre> in example w3c/magnetometer#70.
-
-
1 pull request received 2 new comments.
-
editorial: Use <xmp> tag instead of <pre> in example w3c/magnetometer#70 (2 comments by @rakuco, @reillyeon)
-
w3c/ambient-light
-
1 pull request opened.
-
Adapt to virtual sensor changes in w3c/sensors#475 w3c/ambient-light#88, by @rakuco.
-
-
1 pull request merged.
-
Adapt to virtual sensor changes in w3c/sensors#475 w3c/ambient-light#88.
-
w3c/gyroscope
-
1 pull request opened.
-
Adapt to virtual sensor changes in w3c/sensors#475 w3c/gyroscope#57, by @rakuco.
-
w3c/compute-pressure
-
1 issue opened.
-
Permission policy needs to be checked when owner set changes w3c/compute-pressure#243, by @kenchris.
-
-
8 issues closed.
-
Feature can be abused to create cross-site covert channels w3c/compute-pressure#197.
-
permissions policy: Default allowlist syntax needs to be updated w3c/compute-pressure#154.
-
Focus control in privacy test steps w3c/compute-pressure#185.
-
Add "resource-contention" or "contention" as a contributing factor w3c/compute-pressure#117.
-
Add hooks for Permission Revocation w3c/compute-pressure#147.
-
Contributing factors definition needs clarification w3c/compute-pressure#181.
-
What version Chrome can support the new PressureObserver interface? w3c/compute-pressure#113.
-
Provide better timing guidelines for mitigation algorithms. w3c/compute-pressure#240.
-
-
9 issues received 16 new comments.
-
Feature can be abused to create cross-site covert channels w3c/compute-pressure#197 (5 comments by @kenchris, @pes10k, @toreini)
-
Add "resource-contention" or "contention" as a contributing factor w3c/compute-pressure#117 (1 comment by @kenchris)
-
What version Chrome can support the new PressureObserver interface? w3c/compute-pressure#113 (1 comment by @kenchris)
-
Use-case: provide a battery draining rate indication for application w3c/compute-pressure#126 (1 comment by @arskama)
-
Contributing factors definition needs clarification w3c/compute-pressure#181 (1 comment by @arskama)
-
-
3 pull requests opened.
-
Use right notation for default allowlist value. w3c/compute-pressure#244, by @arskama.
-
Add user interactions to use-cases w3c/compute-pressure#242, by @kenchris.
-
Provide guidelines for mitigation algorithms w3c/compute-pressure#241, by @arskama.
-
-
3 pull requests merged.
-
Use right notation for default allowlist value. w3c/compute-pressure#244.
-
Add user interactions to use-cases w3c/compute-pressure#242.
-
Provide guidelines for mitigation algorithms w3c/compute-pressure#241.
-
-
2 pull requests received 17 new comments.
-
Provide guidelines for mitigation algorithms w3c/compute-pressure#241 (12 comments by @anssiko, @arskama, @pes10k, @rakuco)
-
w3c/das-charter
-
1 issue closed.
-
Joint deliverables with WebApps WG w3c/das-charter#123.
-
-
1 issue received 1 new comment.
w3c/motion-sensors
-
3 pull requests opened.
-
Fix some Bikeshed link errors w3c/motion-sensors#33, by @rakuco.
-
Make Alexander Shalamov a Former Editor w3c/motion-sensors#32, by @rakuco.
-
Update DAS website URL in README.md w3c/motion-sensors#31, by @rakuco.
-
-
3 pull requests merged.
-
Fix some Bikeshed link errors w3c/motion-sensors#33.
-
Make Alexander Shalamov a Former Editor w3c/motion-sensors#32.
-
Update DAS website URL in README.md w3c/motion-sensors#31.
-
-
2 pull requests received 2 new comments.
TR publications
-
17 documents published.
-
Generic Sensor API published twice as a Candidate Recommendation Draft. History of Generic Sensor API
-
Accelerometer published as a Candidate Recommendation Draft. History of Accelerometer
-
Gyroscope published 3 times as a Candidate Recommendation Draft. History of Gyroscope
-
Geolocation Sensor published as a Working Draft. History of Geolocation Sensor
-
Magnetometer published 3 times as a Working Draft. History of Magnetometer
-
Proximity Sensor published as a Working Draft. History of Proximity Sensor
-
Orientation Sensor published twice as a Working Draft. History of Orientation Sensor
-
Ambient Light Sensor published as a Working Draft. History of Ambient Light Sensor
-
Compute Pressure Level 1 published twice as a Working Draft. History of Compute Pressure Level 1
-
Contact Picker API published as a Working Draft. History of Contact Picker API
-
Participants
-
1 participant joined.
-
Sanjeev Reddy (Microsoft Corporation) joined.
-
GitHub
w3c/deviceorientation
-
4 issues received 9 new comments.
-
DeviceMotionEvent atttributes can't be null per current IDL w3c/deviceorientation#91 (6 comments by @annevk, @rakuco, @saschanaz)
-
-
1 pull request opened.
-
editorial: Reword requirements in "Security and privacy considerations" w3c/deviceorientation#114, by @rakuco.
-
w3c/screen-wake-lock
-
1 pull request opened.
-
editorial: Use more precise terms to define WakeLockSentinel.onrelease w3c/screen-wake-lock#365, by @rakuco.
-
w3c/compute-pressure
-
1 issue opened.
-
Provide better timing guidelines for mitigation algorithms. w3c/compute-pressure#240, by @arskama.
-
-
2 issues closed.
-
Same-origin check for workers w3c/compute-pressure#215.
-
Does the privacy test need a same origin-domain or a same origin check? w3c/compute-pressure#187.
-
-
1 issue received 1 new comment.
-
3 pull requests opened.
-
Require all owning documents to have permission policy enabled w3c/compute-pressure#239, by @kenchris.
-
Support workers in privacy algos w3c/compute-pressure#238, by @kenchris.
-
Demo rework w3c/compute-pressure#237, by @kenchris.
-
-
4 pull requests merged.
-
Require all owning documents to have permission policy enabled w3c/compute-pressure#239.
-
Support workers in privacy algos w3c/compute-pressure#238.
-
Demo rework w3c/compute-pressure#237.
-
Use same origin checks instead of same origin-domain ones w3c/compute-pressure#236.
-
-
3 pull requests received 42 new comments.
-
Support workers in privacy algos w3c/compute-pressure#238 (31 comments by @arskama, @himorin, @kenchris, @rakuco, @wangw-1991)
-
Require all owning documents to have permission policy enabled w3c/compute-pressure#239 (10 comments by @kenchris, @rakuco)
-
w3c/sensors
-
1 pull request opened.
-
Fix reference to "coarsened moment" w3c/sensors#473, by @rakuco.
-
-
2 pull requests merged.
-
Fix reference to "coarsened moment" w3c/sensors#473.
-
-
1 pull request received 2 new comments.
-
Rewrite the Automation section and redefine the spec's extension commands w3c/sensors#470 (2 comments by @rakuco)
-
w3c/proximity
-
1 issue opened.
-
Broken references in Proximity Sensor w3c/proximity#56, by @dontcallmedom-bot.
-
-
1 issue closed.
-
Broken references in Proximity Sensor w3c/proximity#56.
-
-
2 pull requests opened.
-
Clean up Model section, export permission and policy-controlled feature name w3c/proximity#58, by @rakuco.
-
Rewrite Automation section after w3c/sensors#470 w3c/proximity#57, by @JuhaVainio.
-
-
2 pull requests merged.
-
Rewrite Automation section after w3c/sensors#470 w3c/proximity#57.
-
1 pull request received 27 new comments.
-
Rewrite Automation section after w3c/sensors#470 w3c/proximity#57 (27 comments by @JuhaVainio, @rakuco)
-
w3c/magnetometer
-
1 issue opened.
-
Broken references in Magnetometer w3c/magnetometer#65, by @dontcallmedom-bot.
-
-
1 issue closed.
-
Broken references in Magnetometer w3c/magnetometer#65.
-
-
4 pull requests opened.
-
Rewrite Automation section after w3c/sensors#470 w3c/magnetometer#69, by @JuhaVainio.
-
Modernize construction steps w3c/magnetometer#68, by @rakuco.
-
Define and export "magnetometer" permission w3c/magnetometer#67, by @rakuco.
-
Define a separate "Uncalibrated Magnetometer" sensor type, tighten definitions w3c/magnetometer#66, by @rakuco.
-
-
4 pull requests merged.
-
Rewrite Automation section after w3c/sensors#470 w3c/magnetometer#69.
-
Modernize construction steps w3c/magnetometer#68.
-
Define and export "magnetometer" permission w3c/magnetometer#67.
-
Define a separate "Uncalibrated Magnetometer" sensor type, tighten definitions w3c/magnetometer#66.
-
-
1 pull request received 18 new comments.
-
Rewrite Automation section after w3c/sensors#470 w3c/magnetometer#69 (18 comments by @JuhaVainio, @rakuco)
-
w3c/geolocation
-
1 issue opened.
-
2 issues closed.
-
Background Geolocation w3c/geolocation#131.
-
2 issues received 2 new comments.
w3c/orientation-sensor
-
1 issue opened.
-
Broken references in Orientation Sensor w3c/orientation-sensor#77, by @dontcallmedom-bot.
-
-
1 issue closed.
-
Broken references in Orientation Sensor w3c/orientation-sensor#77.
-
-
1 issue reopened.
-
Broken references in Orientation Sensor w3c/orientation-sensor#77, by @rakuco.
-
-
1 issue received 2 new comments.
-
3 pull requests opened.
-
Define the Absolute/Relative Orientation Sensor sensor types in this spec w3c/orientation-sensor#80, by @rakuco.
-
Fix exception name used in permissions example w3c/orientation-sensor#79, by @rakuco.
-
Rewrite Automation section after w3c/sensors#470 w3c/orientation-sensor#78, by @JuhaVainio.
-
-
3 pull requests merged.
-
Rewrite Automation section after w3c/sensors#470 w3c/orientation-sensor#78.
-
Define the Absolute/Relative Orientation Sensor sensor types in this spec w3c/orientation-sensor#80.
-
Fix exception name used in permissions example w3c/orientation-sensor#79.
-
-
2 pull requests received 13 new comments.
-
Rewrite Automation section after w3c/sensors#470 w3c/orientation-sensor#78 (12 comments by @JuhaVainio, @rakuco)
-
Define the Absolute/Relative Orientation Sensor sensor types in this spec w3c/orientation-sensor#80 (1 comment by @kenchris)
-
w3c/accelerometer
-
1 issue opened.
-
Disable Accelerometer use while Vibration API is in use w3c/accelerometer#69, by @MrBrain295.
-
-
1 issue received 2 new comments.
-
Disable Accelerometer use while Vibration API is in use w3c/accelerometer#69 (2 comments by @anssiko, @reillyeon)
-
-
2 pull requests opened.
-
Split Model section up, export policy-controlled feature name w3c/accelerometer#71, by @rakuco.
-
Modernize object construction steps w3c/accelerometer#70, by @rakuco.
-
-
2 pull requests merged.
-
Split Model section up, export policy-controlled feature name w3c/accelerometer#71.
-
Modernize object construction steps w3c/accelerometer#70.
-
-
1 pull request received 1 new comment.
-
Split Model section up, export policy-controlled feature name w3c/accelerometer#71 (1 comment by @reillyeon)
-
w3c/gyroscope
-
1 issue opened.
-
Broken references in Gyroscope w3c/gyroscope#51, by @dontcallmedom-bot.
-
-
1 issue closed.
-
Broken references in Gyroscope w3c/gyroscope#51.
-
-
5 pull requests opened.
-
Clean up Model section, export permission and policy-controlled feature name w3c/gyroscope#56, by @rakuco.
-
Modernize Gyroscope constructor steps w3c/gyroscope#55, by @rakuco.
-
Remove "sensor permission name" custom anchor w3c/gyroscope#54, by @rakuco.
-
editorial: Add an empty line after the "Automation" header w3c/gyroscope#53, by @rakuco.
-
Rewrite Automation section after w3c/sensors#470 w3c/gyroscope#52, by @rakuco.
-
-
5 pull requests merged.
-
Modernize Gyroscope constructor steps w3c/gyroscope#55.
-
Remove "sensor permission name" custom anchor w3c/gyroscope#54.
-
editorial: Add an empty line after the "Automation" header w3c/gyroscope#53.
-
Rewrite Automation section after w3c/sensors#470 w3c/gyroscope#52.
-
1 pull request received 1 new comment.
w3c/vibration
-
1 issue received 2 new comments.
w3c/ambient-light
-
1 issue opened.
-
Broken references in Ambient Light Sensor w3c/ambient-light#86, by @dontcallmedom-bot.
-
-
1 issue closed.
-
Broken references in Ambient Light Sensor w3c/ambient-light#86.
-
-
1 pull request opened.
-
Rewrite Automation section after w3c/sensors#470 w3c/ambient-light#87, by @JuhaVainio.
-
-
1 pull request merged.
-
Rewrite Automation section after w3c/sensors#470 w3c/ambient-light#87.
-
-
1 pull request received 3 new comments.
-
Rewrite Automation section after w3c/sensors#470 w3c/ambient-light#87 (3 comments by @JuhaVainio, @rakuco)
-
w3c/battery
-
1 issue opened.
-
Johnson07Son's w3c/battery#57, by @nikijohnson4.
-
-
1 issue closed.
-
Johnson07Son's w3c/battery#57.
-
-
1 issue received 1 new comment.
w3c/contact-picker
-
1 issue closed.
-
Editor update w3c/contact-picker#66.
-
-
1 issue received 2 new comments.
-
1 pull request opened.
-
Editorial: move Ryan Kanso to Former Editor w3c/contact-picker#67, by @marcoscaceres.
-
-
1 pull request merged.
-
Editorial: move Ryan Kanso to Former Editor w3c/contact-picker#67.
-
w3c/das-charter
-
1 pull request merged.
-
updated spec TR URLs, and target dates of completion w3c/das-charter#130.
-
-
1 pull request received 1 new comment.
TR publications
-
1 document published.
-
Compute Pressure Level 1 published as a Working Draft. History of Compute Pressure Level 1
-
Past meetings
-
1 meeting.
GitHub
w3c/compute-pressure
-
2 issues opened.
-
Use-case: For improving interactivity w3c/compute-pressure#235, by @nhelfman.
-
Use-case: Analytics / RUM w3c/compute-pressure#233, by @nicjansma.
-
-
3 issues received 3 new comments.
-
Does the privacy test need a same origin-domain or a same origin check? w3c/compute-pressure#187 (1 comment by @arskama)
-
Does compute pressure reflect OS-level speed limit changes due to throttling? w3c/compute-pressure#228 (1 comment by @kenchris)
-
-
2 pull requests opened.
-
Use same origin checks instead of same origin-domain ones w3c/compute-pressure#236, by @arskama.
-
editorial: Do not use unordered list in "passes privacy test" steps w3c/compute-pressure#234, by @rakuco.
-
-
1 pull request merged.
-
editorial: Do not use unordered list in "passes privacy test" steps w3c/compute-pressure#234.
-
-
2 pull requests received 4 new comments.
-
Use same origin checks instead of same origin-domain ones w3c/compute-pressure#236 (3 comments by @arskama)
-
editorial: Do not use unordered list in "passes privacy test" steps w3c/compute-pressure#234 (1 comment by @arskama)
-
w3c/das-charter
-
1 issue received 5 new comments.
-
Joint deliverables with WebApps WG w3c/das-charter#123 (5 comments by @anssiko, @himorin, @plehegar, @reillyeon)
-
-
1 pull request opened.
-
updated spec TR URLs, and target dates of completion w3c/das-charter#130, by @himorin.
-
-
1 pull request received 4 new comments.
-
updated spec TR URLs, and target dates of completion w3c/das-charter#130 (4 comments by @anssiko, @himorin)
-
w3c/screen-wake-lock
-
1 issue received 3 new comments.
-
Require transient activation to request lock w3c/screen-wake-lock#350 (3 comments by @reillyeon, @vinhill)
-
w3c/contact-picker
-
1 issue opened.
-
Editor update w3c/contact-picker#66, by @marcoscaceres.
-
-
2 issues closed.
-
Consider Web Intents w3c/contact-picker#11.
-
-
1 issue received 1 new comment.
w3c/deviceorientation
-
1 issue received 1 new comment.
w3c/das-wg
-
1 issue received 1 new comment.
w3c/geolocation
-
3 issues opened.
-
Position data isn't passed into 'new GeolocationPosition' w3c/geolocation#137, by @jyasskin.
-
Define "geographic coordinates" w3c/geolocation#136, by @mgiuca.
-
What does "decimal degrees" mean? w3c/geolocation#135, by @mgiuca.
-
-
3 issues received 6 new comments.
-
What does "decimal degrees" mean? w3c/geolocation#135 (3 comments by @chaals, @jyasskin, @reillyeon)
-
-
1 pull request opened.
-
Correction: Clarify units and reference geodetic system for latitude and longitude w3c/geolocation#138, by @reillyeon.
-
-
1 pull request received 2 new comments.
-
Correction: Clarify units and reference geodetic system for latitude and longitude w3c/geolocation#138 (2 comments by @jyasskin, @reillyeon)
-
TR publications
-
6 documents published.
-
Generic Sensor API published 3 times as a Candidate Recommendation Draft. History of Generic Sensor API
-
Compute Pressure Level 1 published twice as a Working Draft. History of Compute Pressure Level 1
-
Orientation Sensor published as a Working Draft. History of Orientation Sensor
-
GitHub
w3c/compute-pressure
-
1 issue opened.
-
Data delivery and mitigation penalty algorithm issue. w3c/compute-pressure#229, by @arskama.
-
-
2 issues closed.
-
Data delivery and mitigation penalty algorithm issue. w3c/compute-pressure#229.
-
Fix definition of ChangesCountMap w3c/compute-pressure#226.
-
-
3 issues received 11 new comments.
-
Does compute pressure reflect OS-level speed limit changes due to throttling? w3c/compute-pressure#228 (5 comments by @anssiko, @brycepj, @kenchris)
-
Feature can be abused to create cross-site covert channels w3c/compute-pressure#197 (3 comments by @anssiko, @pes10k)
-
Data delivery and mitigation penalty algorithm issue. w3c/compute-pressure#229 (3 comments by @arskama, @kenchris, @rakuco)
-
-
3 pull requests opened.
-
Fix another reference for "map/exists" w3c/compute-pressure#232, by @arskama.
-
Fix reference to map/exists. w3c/compute-pressure#231, by @arskama.
-
Fix penalty algorithm w3c/compute-pressure#230, by @arskama.
-
-
4 pull requests merged.
-
Fix another reference for "map/exists" w3c/compute-pressure#232.
-
Fix reference to map/exists. w3c/compute-pressure#231.
-
Fix penalty algorithm w3c/compute-pressure#230.
-
Fix definition of ChangesCountMap w3c/compute-pressure#227.
-
-
2 pull requests received 37 new comments.
-
Fix penalty algorithm w3c/compute-pressure#230 (33 comments by @arskama, @himorin, @kenchris, @rakuco)
-
Fix definition of ChangesCountMap w3c/compute-pressure#227 (4 comments by @anssiko, @arskama, @kenchris)
-
w3c/geolocation
-
1 issue received 7 new comments.
-
Support geolocation (especially geofencing) in the "background" w3c/geolocation#214 (7 comments by @anssiko, @CarelessCourage, @clshortfuse, @mfulton26, @orpic, @tomayac)
-
w3c/sensors
-
1 issue opened.
-
Specify behavior when device sensor is no longer available w3c/sensors#471, by @rakuco.
-
-
4 pull requests opened.
-
Rewrite the Automation section and redefine the spec's extension commands w3c/sensors#470, by @rakuco.
-
Tighten the Sensor.timestamp and latest reading["timestamp"] definitions w3c/sensors#469, by @rakuco.
-
Overhaul frequency management in the specification w3c/sensors#468, by @rakuco.
-
Explicitly associate a Sensor and a sensor type w3c/sensors#467, by @rakuco.
-
-
4 pull requests merged.
-
Overhaul frequency management in the specification w3c/sensors#468.
-
Explicitly associate a Sensor and a sensor type w3c/sensors#467.
-
4 pull requests received 18 new comments.
-
Rewrite the Automation section and redefine the spec's extension commands w3c/sensors#470 (11 comments by @rakuco, @reillyeon)
-
Overhaul frequency management in the specification w3c/sensors#468 (4 comments by @rakuco, @reillyeon)
-
Tighten the Sensor.timestamp and latest reading["timestamp"] definitions w3c/sensors#469 (2 comments by @rakuco, @reillyeon)
-
Reword the "Sensor Type" section, move permission revocation algorithm w3c/sensors#466 (1 comment by @rakuco)
-
w3c/das-wg
-
1 pull request opened.
-
Remove api.w3.org API key that is no longer required w3c/das-wg#67, by @anssiko.
-
w3c/orientation-sensor
-
1 issue opened.
-
Broken references in Orientation Sensor w3c/orientation-sensor#75, by @dontcallmedom-bot.
-
-
1 issue closed.
-
Broken references in Orientation Sensor w3c/orientation-sensor#75.
-
-
1 pull request opened.
-
Use more common language in populateMatrix()'s description w3c/orientation-sensor#76, by @rakuco.
-
-
1 pull request merged.
-
Use more common language in populateMatrix()'s description w3c/orientation-sensor#76.
-
-
1 pull request received 1 new comment.
-
Use more common language in populateMatrix()'s description w3c/orientation-sensor#76 (1 comment by @rakuco)
-
TR publications
-
7 documents published.
-
Generic Sensor API published 4 times as a Candidate Recommendation Draft. History of Generic Sensor API
-
Ambient Light Sensor published as a Working Draft. History of Ambient Light Sensor
-
Screen Wake Lock API published twice as a Working Draft. History of Screen Wake Lock API
-
GitHub
w3c/sensors
-
1 issue opened.
-
[Meta] Proof-read and modernize spec w3c/sensors#463, by @rakuco.
-
-
4 pull requests opened.
-
Reword the "Sensor Type" section, move permission revocation algorithm w3c/sensors#466, by @rakuco.
-
Clean up some <dfn>s that were not referenced w3c/sensors#465, by @rakuco.
-
Clean up spec metadata w3c/sensors#464, by @rakuco.
-
editorial: Capitalize first letter in notes w3c/sensors#462, by @rakuco.
-
-
4 pull requests merged.
-
Clean up some <dfn>s that were not referenced w3c/sensors#465.
-
Clean up spec metadata w3c/sensors#464.
-
editorial: Capitalize first letter in notes w3c/sensors#462.
-
editorial: Fix some Bikeshed warnings about ambiguous references w3c/sensors#460.
-
-
2 pull requests received 4 new comments.
-
Reword the "Sensor Type" section, move permission revocation algorithm w3c/sensors#466 (3 comments by @reillyeon)
-
w3c/compute-pressure
-
2 issues opened.
-
Does compute pressure reflect OS-level speed limit changes due to throttling? w3c/compute-pressure#228, by @brycepj.
-
Fix definition of ChangesCountMap w3c/compute-pressure#226, by @arskama.
-
-
1 pull request opened.
-
Fix definition of ChangesCountMap w3c/compute-pressure#227, by @arskama.
-
w3c/das-charter
-
1 issue received 2 new comments.
w3c/ambient-light
-
1 pull request opened.
-
Fix comparison of rounded readings in threshold check algorithm w3c/ambient-light#85, by @rakuco.
-
-
1 pull request merged.
-
Fix comparison of rounded readings in threshold check algorithm w3c/ambient-light#85.
-
-
1 pull request received 1 new comment.
-
Fix comparison of rounded readings in threshold check algorithm w3c/ambient-light#85 (1 comment by @rakuco)
-
w3c/screen-wake-lock
-
1 issue opened.
-
Stop using "browsing context" in the spec w3c/screen-wake-lock#362, by @rakuco.
-
-
1 issue closed.
-
Stop using "browsing context" in the spec w3c/screen-wake-lock#362.
-
-
1 issue received 3 new comments.
-
Stop using "browsing context" in the spec w3c/screen-wake-lock#362 (3 comments by @rakuco, @reillyeon)
-
-
2 pull requests opened.
-
editorial: Add an index to the appendices w3c/screen-wake-lock#364, by @rakuco.
-
Remove browsing context check from WakeLock.request() w3c/screen-wake-lock#363, by @rakuco.
-
-
2 pull requests merged.
-
editorial: Add an index to the appendices w3c/screen-wake-lock#364.
-
Remove browsing context check from WakeLock.request() w3c/screen-wake-lock#363.
-
TR publications
-
3 documents published.
-
Compute Pressure Level 1 published 3 times as a Working Draft. History of Compute Pressure Level 1
-
GitHub
w3c/sensors
-
1 pull request opened.
-
editorial: Fix some Bikeshed warnings about ambiguous references w3c/sensors#460, by @rakuco.
-
w3c/contact-picker
-
1 issue reopened.
-
ContactAddress 'region' inconsistencies w3c/contact-picker#65, by @marcoscaceres.
-
w3c/compute-pressure
-
2 issues opened.
-
Broken references in Compute Pressure Level 1 w3c/compute-pressure#220, by @dontcallmedom-bot.
-
Same-origin check for workers w3c/compute-pressure#215, by @anssiko.
-
-
6 issues closed.
-
Broken references in Compute Pressure Level 1 w3c/compute-pressure#220.
-
"User notifications" section should be more specific w3c/compute-pressure#194.
-
"no side channels" subsection issues w3c/compute-pressure#205.
-
Specify what kind of attacks are considered and addressed w3c/compute-pressure#204.
-
First-party context definition w3c/compute-pressure#179.
-
"first party context" section concerns w3c/compute-pressure#206.
-
-
7 issues received 34 new comments.
-
"User notifications" section should be more specific w3c/compute-pressure#194 (5 comments by @anssiko, @pes10k)
-
Specify what kind of attacks are considered and addressed w3c/compute-pressure#204 (1 comment by @anssiko)
-
9 pull requests opened.
-
Break calibration w3c/compute-pressure#225, by @kenchris.
-
Note TAG guidance on private browsing modes in mitigations w3c/compute-pressure#224, by @anssiko.
-
Add rate obfuscation test requirement w3c/compute-pressure#223, by @kenchris.
-
Fix 'declared policy' reference w3c/compute-pressure#222, by @anssiko.
-
fix anchor for declared-policy w3c/compute-pressure#221, by @arskama.
-
Add proposed Cross-site covert channel attack description w3c/compute-pressure#219, by @anssiko.
-
Improve User notifications section w3c/compute-pressure#218, by @anssiko.
-
Fix 'declared policy' reference w3c/compute-pressure#217, by @anssiko.
-
Reorganize Security and privacy considerations w3c/compute-pressure#216, by @anssiko.
-
-
8 pull requests merged.
-
Break calibration w3c/compute-pressure#225.
-
Add rate obfuscation test requirement w3c/compute-pressure#223.
-
Note TAG guidance on private browsing modes in mitigations w3c/compute-pressure#224.
-
Add proposed Cross-site covert channel attack description w3c/compute-pressure#219.
-
fix anchor for declared-policy w3c/compute-pressure#221.
-
Improve User notifications section w3c/compute-pressure#218.
-
Fix 'declared policy' reference w3c/compute-pressure#217.
-
Reorganize Security and privacy considerations w3c/compute-pressure#216.
-
-
1 pull request closed.
-
Fix 'declared policy' reference w3c/compute-pressure#222.
-
-
7 pull requests received 44 new comments.
-
Add proposed Cross-site covert channel attack description w3c/compute-pressure#219 (18 comments by @anssiko, @arskama, @kenchris)
-
Note TAG guidance on private browsing modes in mitigations w3c/compute-pressure#224 (5 comments by @anssiko, @himorin)
-
Reorganize Security and privacy considerations w3c/compute-pressure#216 (4 comments by @anssiko, @kenchris, @pes10k)
-
w3c/das-charter
-
1 issue received 2 new comments.
-
2 pull requests merged.
-
Compute Pressure w3c/das-charter#128.
-
Joint deliverables w3c/das-charter#126.
-
-
1 pull request received 3 new comments.
w3c/battery
-
1 issue received 2 new comments.
w3c/das-wg
-
1 issue opened.
-
Devices and Sensors WG - TPAC 2023 agenda w3c/das-wg#66, by @anssiko.
-
TR publications
-
1 document published.
-
Compute Pressure Level 1 published as a Working Draft. History of Compute Pressure Level 1
-
GitHub
w3c/compute-pressure
-
1 issue opened.
-
Allow an array of sources w3c/compute-pressure#213, by @tomayac.
-
-
5 issues received 6 new comments.
-
"User notifications" section should be more specific w3c/compute-pressure#194 (2 comments by @anssiko, @pes10k)
-
Feature can be abused to create cross-site covert channels w3c/compute-pressure#197 (1 comment by @anssiko)
-
Specify what kind of attacks are considered and addressed w3c/compute-pressure#204 (1 comment by @anssiko)
-
-
2 pull requests opened.
-
Update demo for OT w3c/compute-pressure#214, by @kenchris.
-
Fix example 5 w3c/compute-pressure#212, by @anssiko.
-
-
2 pull requests merged.
-
Update demo for OT w3c/compute-pressure#214.
-
Fix example 5 w3c/compute-pressure#212.
-
-
1 pull request received 1 new comment.
w3c/battery
-
1 issue opened.
-
dark mode w3c/battery#56, by @jimmywarting.
-
-
1 issue closed.
-
dark mode w3c/battery#56.
-
-
2 issues received 5 new comments.
w3c/das-charter
-
1 pull request received 2 new comments.
w3c/sensors
-
1 issue opened.
-
Only positive frequency values should be accepted w3c/sensors#459, by @rakuco.
-
w3c/ambient-light
-
1 issue received 5 new comments.
-
Request for Ambient Light Sensor web developer feedback w3c/ambient-light#64 (5 comments by @anaestheticsapp, @anssiko, @marcoscaceres, @willmorgan)
-
w3c/geolocation
-
1 issue received 1 new comment.
-
Support geolocation (especially geofencing) in the "background" w3c/geolocation#214 (1 comment by @timbtimbtimb)
-
TR publications
-
6 documents published.
-
DeviceOrientation Event Specification published 3 times as a Working Draft. History of DeviceOrientation Event Specification
-
Screen Wake Lock API published as a Working Draft. History of Screen Wake Lock API
-
Device Posture API published twice as a Working Draft. History of Device Posture API
-
GitHub
w3c/das-charter
-
3 pull requests opened.
-
Add pr-preview.json for das-wg-charter.html w3c/das-charter#129, by @himorin.
-
Compute Pressure w3c/das-charter#128, by @anssiko.
-
draft text for starting discussion - 2023 DAS charter w3c/das-charter#127, by @himorin.
-
-
1 pull request merged.
-
Add pr-preview.json for das-wg-charter.html w3c/das-charter#129.
-
-
1 pull request closed.
-
draft text for starting discussion - 2023 DAS charter w3c/das-charter#127.
-
-
3 pull requests received 10 new comments.
-
Joint deliverables w3c/das-charter#126 (8 comments by @anssiko, @himorin, @marcoscaceres, @reillyeon)
-
w3c/compute-pressure
-
1 issue opened.
-
Use-case: Automated performance regression testing in Utopia w3c/compute-pressure#211, by @Rheeseyb.
-
-
3 issues received 4 new comments.
-
Use-case: Automated performance regression testing in Utopia w3c/compute-pressure#211 (1 comment by @anssiko)
-
1 pull request opened.
-
Adding Wei and Raphael to contributors list w3c/compute-pressure#210, by @arskama.
-
-
1 pull request merged.
-
Adding Wei and Raphael to contributors list w3c/compute-pressure#210.
-
w3c/deviceorientation
-
1 issue opened.
-
Broken references in DeviceOrientation Event Specification w3c/deviceorientation#109, by @dontcallmedom-bot.
-
-
1 issue closed.
-
Broken references in DeviceOrientation Event Specification w3c/deviceorientation#109.
-
-
1 issue received 2 new comments.
-
requestPermission() and event handling clarification w3c/deviceorientation#74 (2 comments by @reillyeon, @stepancar)
-
-
3 pull requests opened.
-
Add new editors w3c/deviceorientation#111, by @anssiko.
-
Update remaining reference to "triggered by user activation" w3c/deviceorientation#110, by @reillyeon.
-
Editorial: mark sections as non-normative w3c/deviceorientation#108, by @marcoscaceres.
-
-
3 pull requests merged.
-
Add new editors w3c/deviceorientation#111.
-
Update remaining reference to "triggered by user activation" w3c/deviceorientation#110.
-
Editorial: mark sections as non-normative w3c/deviceorientation#108.
-
w3c/geolocation
-
1 issue opened.
-
1 issue closed.
-
1 issue received 1 new comment.
-
Effectively no-op step in the “acquire a position” algorithm (suggesting something is wrong) w3c/geolocation#134 (1 comment by @triple-underscore)
-
w3c/html-media-capture
-
1 issue opened.
-
Broken references in HTML Media Capture w3c/html-media-capture#40, by @dontcallmedom-bot.
-
-
1 issue closed.
-
Broken references in HTML Media Capture w3c/html-media-capture#40.
-
-
1 pull request opened.
-
Editorial: fix broken references w3c/html-media-capture#41, by @anssiko.
-
-
1 pull request merged.
-
Editorial: fix broken references w3c/html-media-capture#41.
-
-
1 pull request received 2 new comments.
w3c/screen-wake-lock
-
1 pull request opened.
-
editorial: Fix references to "default allowlist". w3c/screen-wake-lock#361, by @rakuco.
-
-
1 pull request merged.
-
editorial: Fix references to "default allowlist". w3c/screen-wake-lock#361.
-
w3c/device-posture
-
1 issue opened.
-
Use Navigables instead of browsing contexts w3c/device-posture#104, by @kenchris.
-
-
1 issue closed.
-
Replace usage of "responsible document" w3c/device-posture#101.
-
-
2 issues received 2 new comments.
-
1 pull request opened.
-
fix "active document" cite w3c/device-posture#105, by @himorin.
-
-
3 pull requests merged.
-
Remove Folded Over from Device Posture w3c/device-posture#100.
-
fix "active document" cite w3c/device-posture#105.
-
Editorial: use associated Document in place of responsible document w3c/device-posture#102.
-
-
1 pull request reopened.
-
Remove Folded Over from Device Posture w3c/device-posture#100, by @supo2co.
-
-
2 pull requests received 6 new comments.
-
Editorial: use associated Document in place of responsible document w3c/device-posture#102 (1 comment by @anssiko)
TR publications
-
8 documents published.
-
Compute Pressure Level 1 published 6 times as a Working Draft. History of Compute Pressure Level 1
-
DeviceOrientation Event Specification published as a Working Draft. History of DeviceOrientation Event Specification
-
Contact Picker API published as a Working Draft. History of Contact Picker API
-
GitHub
w3c/compute-pressure
-
10 issues opened.
-
"first party context" section concerns w3c/compute-pressure#206, by @pes10k.
-
"no side channels" subsection issues w3c/compute-pressure#205, by @pes10k.
-
Specify what kind of attacks are considered and addressed w3c/compute-pressure#204, by @pes10k.
-
Adding document explaining API Surface Changes since last Origin Trial w3c/compute-pressure#199, by @arskama.
-
Feature can be abused to create cross-site covert channels w3c/compute-pressure#197, by @pes10k.
-
Text and clarity issues in the security and privacy considerations section w3c/compute-pressure#196, by @pes10k.
-
"power-supply" is a fingerprinting vector w3c/compute-pressure#195, by @pes10k.
-
"User notifications" section should be more specific w3c/compute-pressure#194, by @pes10k.
-
(I think) Document sections are misformatted w3c/compute-pressure#193, by @pes10k.
-
privacy check: workers and window privacy check should be decoupled in the execution order. w3c/compute-pressure#190, by @arskama.
-
-
6 issues closed.
-
"power-supply" is a fingerprinting vector w3c/compute-pressure#195.
-
Text and clarity issues in the security and privacy considerations section w3c/compute-pressure#196.
-
Adding document explaining API Surface Changes since last Origin Trial w3c/compute-pressure#199.
-
(I think) Document sections are misformatted w3c/compute-pressure#193.
-
privacy check: workers and window privacy check should be decoupled in the execution order. w3c/compute-pressure#190.
-
missing link in security and privacy section w3c/compute-pressure#186.
-
-
5 issues received 9 new comments.
-
"power-supply" is a fingerprinting vector w3c/compute-pressure#195 (3 comments by @anssiko, @kenchris, @pes10k)
-
Text and clarity issues in the security and privacy considerations section w3c/compute-pressure#196 (2 comments by @kenchris, @pes10k)
-
Adding document explaining API Surface Changes since last Origin Trial w3c/compute-pressure#199 (1 comment by @tomayac)
-
-
12 pull requests opened.
-
Add ack to the PING for their great privacy review and feedback w3c/compute-pressure#209, by @kenchris.
-
Fix typo in "Contributing Factors" section. w3c/compute-pressure#208, by @rakuco.
-
Update S&P section to reflect rest of spec w3c/compute-pressure#207, by @kenchris.
-
Do not expose contributing factors w3c/compute-pressure#203, by @kenchris.
-
Introduce 'thermals' source type w3c/compute-pressure#202, by @kenchris.
-
Slightly modify use-cases after discussion with Anssi w3c/compute-pressure#201, by @kenchris.
-
Add CHANGES.md w3c/compute-pressure#200, by @arskama.
-
specification: Fix sections w3c/compute-pressure#198, by @arskama.
-
Adjust pressure states and add new explorations as a result w3c/compute-pressure#192, by @kenchris.
-
Privacy check: Remove ordered list between worker and window w3c/compute-pressure#191, by @arskama.
-
Fix missing link in security and privacy section w3c/compute-pressure#189, by @arskama.
-
Add explorations w3c/compute-pressure#188, by @kenchris.
-
-
12 pull requests merged.
-
Add ack to the PING for their great privacy review and feedback w3c/compute-pressure#209.
-
Fix typo in "Contributing Factors" section. w3c/compute-pressure#208.
-
Update S&P section to reflect rest of spec w3c/compute-pressure#207.
-
Do not expose contributing factors w3c/compute-pressure#203.
-
Introduce 'thermals' source type w3c/compute-pressure#202.
-
Slightly modify use-cases after discussion with Anssi w3c/compute-pressure#201.
-
Add CHANGES.md w3c/compute-pressure#200.
-
specification: Fix sections w3c/compute-pressure#198.
-
Privacy check: Remove ordered list between worker and window w3c/compute-pressure#191.
-
Adjust pressure states and add new explorations as a result w3c/compute-pressure#192.
-
Fix missing link in security and privacy section w3c/compute-pressure#189.
-
Add explorations w3c/compute-pressure#188.
-
-
10 pull requests received 38 new comments.
-
Slightly modify use-cases after discussion with Anssi w3c/compute-pressure#201 (4 comments by @arskama, @kenchris)
-
Privacy check: Remove ordered list between worker and window w3c/compute-pressure#191 (3 comments by @arskama, @beaufortfrancois, @kenchris)
-
Adjust pressure states and add new explorations as a result w3c/compute-pressure#192 (2 comments by @arskama)
-
Fix missing link in security and privacy section w3c/compute-pressure#189 (2 comments by @arskama, @kenchris)
w3c/contact-picker
-
2 issues opened.
-
Accessibility review w3c/contact-picker#64, by @matatk.
-
missing metadata of language and direction for string values in natural language w3c/contact-picker#63, by @himorin.
-
-
1 pull request merged.
-
Editorial: Add Contacts API history note w3c/contact-picker#58.
-
-
1 pull request received 1 new comment.
w3c/deviceorientation
-
1 issue closed.
-
compassneedscalibration event - cannot confirm interoperability w3c/deviceorientation#38.
-
-
1 pull request opened.
-
Remove the oncompassneedscalibration event w3c/deviceorientation#107, by @reillyeon.
-
-
1 pull request merged.
-
Remove the oncompassneedscalibration event w3c/deviceorientation#107.
-
-
1 pull request received 9 new comments.
-
Remove the oncompassneedscalibration event w3c/deviceorientation#107 (9 comments by @anssiko, @diekus, @marcoscaceres, @reillyeon)
-
w3c/html-media-capture
-
1 pull request merged.
-
Chore: fixup some ReSpec usage w3c/html-media-capture#37.
-
w3c/sensors
-
1 pull request opened.
-
Add an informative background article w3c/sensors#458, by @anssiko.
-
w3c/battery
-
1 issue received 2 new comments.
w3c/geolocation
-
1 pull request opened.
-
Editorial: Fix references to "default allowlist" w3c/geolocation#133, by @reillyeon.
-
-
1 pull request merged.
-
Editorial: Fix references to "default allowlist" w3c/geolocation#133.
-
TR publications
-
2 documents published.
-
Compute Pressure Level 1 published twice as a Working Draft. History of Compute Pressure Level 1
-
Participants
-
1 participant joined.
-
Ugan Sivagnanenthirarajah (Microsoft Corporation) joined.
-
GitHub
w3c/compute-pressure
-
6 issues opened.
-
Does the privacy test need a same origin-domain or a same origin check? w3c/compute-pressure#187, by @rakuco.
-
missing link in security and privacy section w3c/compute-pressure#186, by @himorin.
-
Focus control in privacy test steps w3c/compute-pressure#185, by @wangw-1991.
-
Internationalization Checklist w3c/compute-pressure#184, by @anssiko.
-
Accessibility Checklist w3c/compute-pressure#183, by @anssiko.
-
Contributing factors definition needs clarification w3c/compute-pressure#181, by @anssiko.
-
-
1 issue closed.
-
Add an implementation-defined change threshold exceeded check w3c/compute-pressure#176.
-
-
6 issues received 32 new comments.
-
Focus control in privacy test steps w3c/compute-pressure#185 (13 comments by @anssiko, @arskama, @kenchris, @wangw-1991)
-
Does the privacy test need a same origin-domain or a same origin check? w3c/compute-pressure#187 (10 comments by @kenchris, @marcoscaceres, @rakuco)
-
Internationalization Checklist w3c/compute-pressure#184 (5 comments by @anssiko, @aphillips, @himorin, @kenchris)
-
Add an implementation-defined change threshold exceeded check w3c/compute-pressure#176 (2 comments by @anssiko)
-
-
2 pull requests opened.
-
Update Acknowledgments w3c/compute-pressure#182, by @anssiko.
-
Add an implementation-defined change threshold exceeded check w3c/compute-pressure#180, by @anssiko.
-
-
2 pull requests merged.
-
Update Acknowledgments w3c/compute-pressure#182.
-
Add an implementation-defined change threshold exceeded check w3c/compute-pressure#180.
-
-
1 pull request received 20 new comments.
-
Add an implementation-defined change threshold exceeded check w3c/compute-pressure#180 (20 comments by @anssiko, @arskama, @kenchris)
-
w3c/sensors
-
1 issue opened.
-
Should we check for "same origin" or "same origin-domain"? w3c/sensors#457, by @rakuco.
-
-
1 issue received 1 new comment.
w3c/ambient-light
-
1 pull request received 1 new comment.
-
Drop own powerful feature, require active local video source. w3c/ambient-light#83 (1 comment by @anssiko)
-
w3c/contact-picker
-
1 pull request received 2 new comments.
-
Editorial: Add Contacts API history note w3c/contact-picker#58 (2 comments by @anssiko, @marcoscaceres)
-
w3c/battery
-
1 pull request merged.
-
Add Energy Saver Mode explainer w3c/battery#55.
-
-
1 pull request received 1 new comment.
w3c/system-wake-lock
-
1 issue opened.
-
Use case: playback of a list of audio tracks w3c/system-wake-lock#14, by @leonixyz.
-
w3c/device-posture
-
1 issue opened.
-
Avoid using the page visibility change steps hook w3c/device-posture#103, by @anssiko.
-
TR publications
-
15 documents published.
-
Accelerometer published as a Candidate Recommendation Draft. History of Accelerometer
-
Gyroscope published as a Candidate Recommendation Draft. History of Gyroscope
-
Generic Sensor API published 3 times as a Candidate Recommendation Draft. History of Generic Sensor API
-
Compute Pressure Level 1 published twice as a Working Draft. History of Compute Pressure Level 1
-
Ambient Light Sensor published as a Working Draft. History of Ambient Light Sensor
-
DeviceOrientation Event Specification published twice as a Working Draft. History of DeviceOrientation Event Specification
-
Magnetometer published as a Working Draft. History of Magnetometer
-
Proximity Sensor published as a Working Draft. History of Proximity Sensor
-
Contact Picker API published 3 times as a Working Draft. History of Contact Picker API
-
Participants
-
3 participants left.
-
Michael[tm] Smith (sideshowbarker) (W3C) left.
-
Fuqiao Xue (W3C) left.
-
George Menzel (Microsoft Corporation) left.
-
-
1 organization joined.
-
Microsoft Corporation joined.
-
GitHub
w3c/sensors
-
1 issue received 2 new comments.
-
Allowing data batching when poll frequency < sensor frequency w3c/sensors#13 (2 comments by @anssiko, @tangobravo)
-
-
5 pull requests opened.
-
editorial: Export "sensor reading" <dfn>. w3c/sensors#456, by @rakuco.
-
editorial: Remove reference to "exception type" in Sensor.onerror. w3c/sensors#455, by @rakuco.
-
editorial: Export all Abstract Operation definitions. w3c/sensors#454, by @rakuco.
-
editorial: Export "{update,get value from} latest reading". w3c/sensors#453, by @rakuco.
-
Export the "specific conditions" requirement and reword paragraph. w3c/sensors#452, by @rakuco.
-
-
5 pull requests merged.
-
editorial: Remove reference to "exception type" in Sensor.onerror. w3c/sensors#455.
-
editorial: Export "sensor reading" <dfn>. w3c/sensors#456.
-
editorial: Export all Abstract Operation definitions. w3c/sensors#454.
-
editorial: Export "{update,get value from} latest reading". w3c/sensors#453.
-
Export the "specific conditions" requirement and reword paragraph. w3c/sensors#452.
-
-
3 pull requests received 6 new comments.
-
Add changes and required hooks for ALS and Media Capture integration w3c/sensors#451 (2 comments by @anssiko, @rakuco)
-
editorial: Remove reference to "exception type" in Sensor.onerror. w3c/sensors#455 (1 comment by @rakuco)
w3c/compute-pressure
-
3 issues opened.
-
First-party context definition w3c/compute-pressure#179, by @anssiko.
-
Wide review tracker w3c/compute-pressure#177, by @anssiko.
-
Add an implementation-defined change threshold exceeded check w3c/compute-pressure#176, by @anssiko.
-
-
3 issues closed.
-
Contradictory security statement w3c/compute-pressure#157.
-
Can the permission be dropped? w3c/compute-pressure#158.
-
Enable automatic WD publication w3c/compute-pressure#169.
-
-
4 issues received 7 new comments.
-
Add an implementation-defined change threshold exceeded check w3c/compute-pressure#176 (4 comments by @anssiko, @kenchris)
-
-
2 pull requests opened.
-
Clarify exposure to first-party contexts w3c/compute-pressure#178, by @anssiko.
-
Add toJSON for PressureRecord, and fix spec link issues w3c/compute-pressure#175, by @kenchris.
-
-
3 pull requests merged.
-
Clarify exposure to first-party contexts w3c/compute-pressure#178.
-
setup streamlined publication w3c/compute-pressure#174.
-
Add toJSON for PressureRecord, and fix spec link issues w3c/compute-pressure#175.
-
-
1 pull request closed.
-
Fix observer/unobserve case w3c/compute-pressure#165.
-
-
2 pull requests received 6 new comments.
-
setup streamlined publication w3c/compute-pressure#174 (3 comments by @anssiko, @himorin, @kenchris)
-
Add toJSON for PressureRecord, and fix spec link issues w3c/compute-pressure#175 (3 comments by @beaufortfrancois, @kenchris)
-
w3c/contact-picker
-
2 issues opened.
-
Switch obsolete "context object" to "this" w3c/contact-picker#60, by @himorin.
-
W3C_TR_TOKEN is failing w3c/contact-picker#56, by @marcoscaceres.
-
-
4 issues closed.
-
Switch obsolete "context object" to "this" w3c/contact-picker#60.
-
Migrate into a working group w3c/contact-picker#37.
-
Call for Consensus: publish Contact Picker API as First Public Working Draft w3c/contact-picker#49.
-
W3C_TR_TOKEN is failing w3c/contact-picker#56.
-
-
3 issues received 4 new comments.
-
Call for Consensus: publish Contact Picker API as First Public Working Draft w3c/contact-picker#49 (1 comment by @marcoscaceres)
-
4 pull requests opened.
-
replaced 'context object' into 'this' w3c/contact-picker#61, by @himorin.
-
added pr-preview w3c/contact-picker#59, by @himorin.
-
Editorial: Add Contacts API history note w3c/contact-picker#58, by @anssiko.
-
Redirect UD -> ED with hash w3c/contact-picker#57, by @anssiko.
-
-
4 pull requests merged.
-
replaced 'context object' into 'this' w3c/contact-picker#61.
-
Redirect UD -> ED with hash w3c/contact-picker#57.
-
added pr-preview w3c/contact-picker#59.
-
Post FPWD updates w3c/contact-picker#53.
-
-
1 pull request closed.
-
Use FPWD template for spec w3c/contact-picker#51.
-
-
5 pull requests received 11 new comments.
-
Editorial: Add Contacts API history note w3c/contact-picker#58 (6 comments by @anssiko, @marcoscaceres, @rayankans)
-
w3c/magnetometer
-
2 issues received 5 new comments.
-
Request for Magnetometer web developer feedback w3c/magnetometer#59 (3 comments by @anssiko, @Zibri)
-
-
1 pull request opened.
-
editorial: Remove "sensor reading" custom anchor. w3c/magnetometer#64, by @rakuco.
-
-
1 pull request merged.
-
editorial: Remove "sensor reading" custom anchor. w3c/magnetometer#64.
-
w3c/gyroscope
-
1 pull request opened.
-
editorial: Remove "sensor reading" custom anchor. w3c/gyroscope#50, by @rakuco.
-
-
1 pull request merged.
-
editorial: Remove "sensor reading" custom anchor. w3c/gyroscope#50.
-
w3c/accelerometer
-
1 pull request opened.
-
editorial: Remove "sensor reading" custom anchor. w3c/accelerometer#68, by @rakuco.
-
-
1 pull request merged.
-
editorial: Remove "sensor reading" custom anchor. w3c/accelerometer#68.
-
w3c/ambient-light
-
1 pull request opened.
-
editorial: Remove "sensor reading" custom anchor. w3c/ambient-light#84, by @rakuco.
-
-
1 pull request merged.
-
editorial: Remove "sensor reading" custom anchor. w3c/ambient-light#84.
-
-
1 pull request received 3 new comments.
-
Drop own powerful feature, require active local video source. w3c/ambient-light#83 (3 comments by @lknik, @rakuco)
-
w3c/proximity
-
1 issue opened.
-
Broken references in Proximity Sensor w3c/proximity#53, by @dontcallmedom-bot.
-
-
1 issue closed.
-
Broken references in Proximity Sensor w3c/proximity#53.
-
-
2 pull requests opened.
-
Remove bikeshed custom anchor w3c/proximity#55, by @anssiko.
-
Fix bikeshed custom anchor w3c/proximity#54, by @anssiko.
-
-
1 pull request merged.
-
Remove bikeshed custom anchor w3c/proximity#55.
-
-
1 pull request closed.
-
Fix bikeshed custom anchor w3c/proximity#54.
-
-
2 pull requests received 4 new comments.
w3c/deviceorientation
-
1 issue opened.
-
Broken references in DeviceOrientation Event Specification w3c/deviceorientation#105, by @dontcallmedom-bot.
-
-
2 issues closed.
-
PermissionState is already defined in Permission API w3c/deviceorientation#82.
-
Broken references in DeviceOrientation Event Specification w3c/deviceorientation#105.
-
-
1 pull request opened.
-
Update reference to "triggered by user activation" w3c/deviceorientation#106, by @reillyeon.
-
-
2 pull requests merged.
-
Drop duplicate PermissionState definition w3c/deviceorientation#88.
-
Update reference to "triggered by user activation" w3c/deviceorientation#106.
-
-
1 pull request received 4 new comments.
-
Drop duplicate PermissionState definition w3c/deviceorientation#88 (4 comments by @rakuco, @reillyeon)
-
w3c/battery
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Add Energy Saver Mode explainer w3c/battery#55, by @anssiko.
-
w3c/das-wg
-
1 pull request opened.
-
Update Contact Picker API ED links w3c/das-wg#65, by @anssiko.
-
-
1 pull request merged.
-
Update Contact Picker API ED links w3c/das-wg#65.
-
w3c/geolocation
-
2 issues received 3 new comments.
w3c/das-charter
-
3 issues closed.
-
Idle Detection API w3c/das-charter#110.
-
Compute Pressure API -> System Pressure w3c/das-charter#111.
-
Contact Picker API w3c/das-charter#97.
-
-
3 issues received 3 new comments.
w3c/system-wake-lock
-
1 issue opened.
-
Use case: playing generated audio via web audio API with on-screen notes w3c/system-wake-lock#13, by @GeorgeTailor.
-