Devices and Sensors Working Group - Activity in 2021
No matches.
TR publications
-
17 documents published.
-
Generic Sensor API published 5 times as a Candidate Recommendation Draft. History of Generic Sensor API
-
Accelerometer published 3 times as a Candidate Recommendation Draft. History of Accelerometer
-
Gyroscope published twice as a Candidate Recommendation Draft. History of Gyroscope
-
Ambient Light Sensor published 4 times as a Working Draft. History of Ambient Light Sensor
-
Magnetometer published twice as a Working Draft. History of Magnetometer
-
Screen Wake Lock API published as a Working Draft. History of Screen Wake Lock API
-
GitHub
w3c/sensors
-
3 issues opened.
-
Other Sensor API standards from OGC w3c/sensors#431, by @KoalaGeo.
-
Inline Sensor Lifecycle SVG does not play well with dark mode color scheme w3c/sensors#423, by @rakuco.
-
-
3 issues closed.
-
Other Sensor API standards from OGC w3c/sensors#431.
-
Adding a sensor.activated attribute w3c/sensors#95.
-
-
3 issues received 6 new comments.
-
Properly specify the constructor algorithm and internal slots for SensorErrorEvent w3c/sensors#426 (3 comments by @domenic, @rakuco)
-
-
12 pull requests opened.
-
Improve SensorErrorEvent description. w3c/sensors#430, by @rakuco.
-
Declare quantization and threshold check algorithms for extension to the spec w3c/sensors#429, by @rakuco.
-
Add syntax highlighting to Web IDL examples. w3c/sensors#428, by @rakuco.
-
Capitalize "low-level" correctly in the text w3c/sensors#427, by @rakuco.
-
Do some editorial adjustments to the Sensor algorithms. w3c/sensors#425, by @rakuco.
-
Fix dark mode SVG w3c/sensors#424, by @tomayac.
-
Remove default.css. w3c/sensors#422, by @rakuco.
-
Proof-read the "Sensor Model" section. w3c/sensors#421, by @rakuco.
-
Use "e.g." rather than "i.e." in example of non-spatial sensor. w3c/sensors#420, by @rakuco.
-
Clean up custom anchors set in the spec. w3c/sensors#419, by @rakuco.
-
Adjust references to terms defined in the Permissions spec. w3c/sensors#418, by @rakuco.
-
Update stability status in SOTD w3c/sensors#417, by @anssiko.
-
-
11 pull requests merged.
-
Capitalize "low-level" correctly in the text w3c/sensors#427.
-
Add syntax highlighting to Web IDL examples. w3c/sensors#428.
-
Do some editorial adjustments to the Sensor algorithms. w3c/sensors#425.
-
Fix dark mode SVG w3c/sensors#424.
-
Use "e.g." rather than "i.e." in example of non-spatial sensor. w3c/sensors#420.
-
Remove default.css. w3c/sensors#422.
-
Proof-read the "Sensor Model" section. w3c/sensors#421.
-
Clean up custom anchors set in the spec. w3c/sensors#419.
-
Adjust references to terms defined in the Permissions spec. w3c/sensors#418.
-
Update stability status in SOTD w3c/sensors#417.
-
Integrate Permissions API changes w3c/sensors#416.
-
-
9 pull requests received 14 new comments.
-
Do some editorial adjustments to the Sensor algorithms. w3c/sensors#425 (3 comments by @anssiko, @reillyeon)
-
Declare quantization and threshold check algorithms for extension to the spec w3c/sensors#429 (2 comments by @anssiko, @rakuco)
-
Use "e.g." rather than "i.e." in example of non-spatial sensor. w3c/sensors#420 (1 comment by @rakuco)
-
w3c/contact-picker
-
1 issue opened.
-
Move repo to W3C w3c/contact-picker#46, by @marcoscaceres.
-
-
1 pull request opened.
-
Prepare for WICG -> W3C migration w3c/contact-picker#47, by @rayankans.
-
-
1 pull request merged.
-
Prepare for WICG -> W3C migration w3c/contact-picker#47.
-
-
1 pull request received 7 new comments.
w3c/screen-wake-lock
-
1 issue opened.
-
Visibility dependencies are broken w3c/screen-wake-lock#331, by @marcoscaceres.
-
-
1 issue closed.
-
Visibility dependencies are broken w3c/screen-wake-lock#331.
-
-
3 pull requests opened.
-
Add brightness-mode-explainer.md. w3c/screen-wake-lock#334, by @rakuco.
-
Remove "page-visibility" from xref spec list. w3c/screen-wake-lock#333, by @rakuco.
-
editorial: Adapt to Page Visibility spec integration into HTML w3c/screen-wake-lock#332, by @rakuco.
-
-
3 pull requests merged.
-
editorial: Use Web IDL's definition conventions for methods and getters. w3c/screen-wake-lock#330.
-
Remove "page-visibility" from xref spec list. w3c/screen-wake-lock#333.
-
editorial: Adapt to Page Visibility spec integration into HTML w3c/screen-wake-lock#332.
-
-
3 pull requests received 12 new comments.
-
Add brightness-mode-explainer.md. w3c/screen-wake-lock#334 (5 comments by @anssiko, @marcoscaceres, @rakuco)
-
editorial: Adapt to Page Visibility spec integration into HTML w3c/screen-wake-lock#332 (4 comments by @marcoscaceres, @noamr)
-
editorial: Use Web IDL's definition conventions for methods and getters. w3c/screen-wake-lock#330 (3 comments by @marcoscaceres, @rakuco)
-
w3c/das-wg
-
1 issue received 3 new comments.
-
Devices and Sensors WG - Screen Wake Lock Brightness follow-up w3c/das-wg#51 (3 comments by @anssiko, @beaufortfrancois, @rakuco)
-
w3c/ambient-light
-
1 issue received 5 new comments.
-
Consider making granularity of the data normative w3c/ambient-light#63 (5 comments by @anssiko, @rakuco, @sandandsnow)
-
-
6 pull requests opened.
-
editorial: Add reading quantization and threshold check algorithms. w3c/ambient-light#77, by @rakuco.
-
Remove references to the `light-level` CSS media feature. w3c/ambient-light#76, by @rakuco.
-
Clean up Bikeshed metadata w3c/ambient-light#75, by @rakuco.
-
Use [=powerful feature/name=] dfn instead of custom w3c/ambient-light#74, by @anssiko.
-
Remove a few custom GENERIC-SENSORS anchors that are exported by the spec. w3c/ambient-light#73, by @rakuco.
-
Remove custom biblio entry for MEDIAQUERIES-5. w3c/ambient-light#72, by @rakuco.
-
-
6 pull requests merged.
-
Remove a few custom GENERIC-SENSORS anchors that are exported by the spec. w3c/ambient-light#73.
-
Remove references to the `light-level` CSS media feature. w3c/ambient-light#76.
-
Clean up Bikeshed metadata w3c/ambient-light#75.
-
Use [=powerful feature/name=] dfn instead of custom w3c/ambient-light#74.
-
Remove custom biblio entry for MEDIAQUERIES-5. w3c/ambient-light#72.
-
Permissions integration tweaks w3c/ambient-light#71.
-
-
5 pull requests received 14 new comments.
-
Remove references to the `light-level` CSS media feature. w3c/ambient-light#76 (4 comments by @anssiko, @rakuco)
-
editorial: Add reading quantization and threshold check algorithms. w3c/ambient-light#77 (2 comments by @anssiko, @rakuco)
-
Remove custom biblio entry for MEDIAQUERIES-5. w3c/ambient-light#72 (2 comments by @anssiko, @rakuco)
w3c/geolocation
-
2 issues opened.
-
"Queue a task" / "in parallel" usage appears wrong w3c/geolocation#114, by @domenic.
-
List of active times is gone w3c/geolocation#113, by @marcoscaceres.
-
-
2 issues reopened.
-
How to specify desired accuracy / resolution of data? w3c/geolocation#49, by @samuelweiler.
-
Section 6: Non-normative but containing implementation requirements? w3c/geolocation#56, by @samuelweiler.
-
-
3 issues received 7 new comments.
-
How to specify desired accuracy / resolution of data? w3c/geolocation#49 (3 comments by @anssiko, @marcoscaceres, @samuelweiler)
-
Section 6: Non-normative but containing implementation requirements? w3c/geolocation#56 (1 comment by @samuelweiler)
-
-
1 pull request received 2 new comments.
-
chore(github/workflows/pr-push): autopub w3c/geolocation#79 (2 comments by @marcoscaceres, @saschanaz)
-
w3c/compute-pressure
-
1 issue closed.
-
No indication of max amount of thresholds available per metrics. w3c/compute-pressure#11.
-
-
3 issues received 6 new comments.
-
How do you handle multiple ComputePressureObserver? w3c/compute-pressure#2 (4 comments by @kenchris, @yoavweiss)
-
No indication of max amount of thresholds available per metrics. w3c/compute-pressure#11 (1 comment by @kenchris)
-
-
1 pull request opened.
-
Fix issue in algo part II w3c/compute-pressure#12, by @arskama.
-
-
1 pull request merged.
-
Fix issue in algo part II w3c/compute-pressure#12.
-
-
1 pull request reopened.
-
Fix issue in algo part II w3c/compute-pressure#12, by @arskama.
-
-
1 pull request received 2 new comments.
w3c/accelerometer
-
3 pull requests opened.
-
Clean up Bikeshed metadata. w3c/accelerometer#65, by @rakuco.
-
Permissions integration w3c/accelerometer#64, by @anssiko.
-
Update stability status in SOTD w3c/accelerometer#63, by @anssiko.
-
-
4 pull requests merged.
-
Clean up Bikeshed metadata. w3c/accelerometer#65.
-
Permissions integration w3c/accelerometer#64.
-
Update stability status in SOTD w3c/accelerometer#63.
-
Integrate Permissions API changes w3c/accelerometer#62.
-
-
1 pull request received 1 new comment.
w3c/magnetometer
-
2 pull requests opened.
-
Permissions integration w3c/magnetometer#63, by @anssiko.
-
Update stability status in SOTD w3c/magnetometer#62, by @anssiko.
-
-
3 pull requests merged.
-
Permissions integration w3c/magnetometer#63.
-
Update stability status in SOTD w3c/magnetometer#62.
-
Integrate Permissions API changes w3c/magnetometer#61.
-
-
1 pull request received 3 new comments.
w3c/gyroscope
-
2 pull requests opened.
-
Permissions integration w3c/gyroscope#49, by @anssiko.
-
Update stability status in SOTD w3c/gyroscope#48, by @anssiko.
-
-
3 pull requests merged.
-
Permissions integration w3c/gyroscope#49.
-
Update stability status in SOTD w3c/gyroscope#48.
-
Integrate Permissions API changes w3c/gyroscope#47.
-
-
1 pull request received 1 new comment.
w3c/orientation-sensor
-
1 issue received 9 new comments.
-
Head orientation tracking w3c/orientation-sensor#68 (9 comments by @anssiko, @himwho, @hoch, @reillyeon)
-
TR publications
-
5 documents published.
-
Geolocation API published 3 times as a Working Draft. History of Geolocation API
-
Battery Status API published as a Working Draft. History of Battery Status API
-
Device Posture API published as a Working Draft. History of Device Posture API
-
Past meetings
GitHub
w3c/screen-wake-lock
-
1 issue received 10 new comments.
-
Need maximum screen brightness mode w3c/screen-wake-lock#129 (10 comments by @beaufortfrancois, @frivoal, @marcoscaceres, @mwatson2, @rakuco)
-
-
1 pull request opened.
-
editorial: Use Web IDL's definition conventions for methods and getters. w3c/screen-wake-lock#330, by @rakuco.
-
-
1 pull request received 3 new comments.
-
editorial: Use Web IDL's definition conventions for methods and getters. w3c/screen-wake-lock#330 (3 comments by @marcoscaceres, @rakuco)
-
w3c/geolocation
-
4 issues closed.
-
Section 3: Why only "SHOULD" for protection of privacy? w3c/geolocation#54.
-
Suggest permission lifetimes? w3c/geolocation#69.
-
Specify behavior for operating system permissions w3c/geolocation#107.
-
Republish as CR w3c/geolocation#93.
-
-
4 issues received 9 new comments.
-
Specify behavior for operating system permissions w3c/geolocation#107 (6 comments by @marcoscaceres, @reillyeon)
-
Section 3: Why only "SHOULD" for protection of privacy? w3c/geolocation#54 (1 comment by @marcoscaceres)
-
-
4 pull requests opened.
-
chore(auto-publish.yml): enable experimental pubrules check w3c/geolocation#111, by @marcoscaceres.
-
Editorial: make use of HTML's page visibility change steps w3c/geolocation#110, by @marcoscaceres.
-
Handle OS permission w3c/geolocation#109, by @marcoscaceres.
-
Suggest permission lifetimes w3c/geolocation#108, by @marcoscaceres.
-
-
4 pull requests merged.
-
Editorial: make use of HTML's page visibility change steps w3c/geolocation#110.
-
Suggest permission lifetimes w3c/geolocation#108.
-
chore(auto-publish.yml): enable experimental pubrules check w3c/geolocation#111.
-
Handle OS permission w3c/geolocation#109.
-
-
4 pull requests received 11 new comments.
-
Suggest permission lifetimes w3c/geolocation#108 (7 comments by @jyasskin, @marcoscaceres, @reillyeon, @yoavweiss)
-
Editorial: make use of HTML's page visibility change steps w3c/geolocation#110 (2 comments by @marcoscaceres, @noamr)
-
w3c/geolocation#112 (1 comment by @w3cbot)
-
w3c/sensors
-
1 pull request opened.
-
Integrate Permissions API changes w3c/sensors#416, by @anssiko.
-
-
1 pull request received 3 new comments.
w3c/das-wg
-
1 issue opened.
-
Devices and Sensors WG - Screen Wake Lock Brightness follow-up w3c/das-wg#51, by @rakuco.
-
-
1 issue received 7 new comments.
-
Devices and Sensors WG - Screen Wake Lock Brightness follow-up w3c/das-wg#51 (7 comments by @anssiko, @beaufortfrancois, @marcoscaceres, @rakuco)
-
w3c/accelerometer
-
1 pull request opened.
-
Integrate Permissions API changes w3c/accelerometer#62, by @anssiko.
-
-
1 pull request received 2 new comments.
w3c/magnetometer
-
2 issues opened.
-
Request for Magnetometer web developer feedback w3c/magnetometer#59, by @anssiko.
-
Update spec status w3c/magnetometer#58, by @rakuco.
-
-
1 issue closed.
-
Update spec status w3c/magnetometer#58.
-
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
Integrate Permissions API changes w3c/magnetometer#61, by @anssiko.
-
Add call for developer feedback into the spec status section w3c/magnetometer#60, by @anssiko.
-
-
1 pull request merged.
-
Add call for developer feedback into the spec status section w3c/magnetometer#60.
-
-
1 pull request received 1 new comment.
w3c/gyroscope
-
1 pull request opened.
-
Integrate Permissions API changes w3c/gyroscope#47, by @anssiko.
-
-
1 pull request received 1 new comment.
w3c/ambient-light
-
1 issue received 3 new comments.
-
Request for Ambient Light Sensor web developer feedback w3c/ambient-light#64 (3 comments by @marcoscaceres, @tomayac)
-
-
2 pull requests opened.
-
Permissions integration tweaks w3c/ambient-light#71, by @anssiko.
-
Define Ambient Light Sensor as a powerful feature w3c/ambient-light#70, by @miketaylr.
-
-
1 pull request merged.
-
Define Ambient Light Sensor as a powerful feature w3c/ambient-light#70.
-
-
2 pull requests received 3 new comments.
-
Define Ambient Light Sensor as a powerful feature w3c/ambient-light#70 (2 comments by @anssiko, @miketaylr)
-
w3c/deviceorientation
-
1 issue closed.
-
Opposite z-axis for example 7 w3c/deviceorientation#96.
-
-
1 issue received 2 new comments.
-
1 pull request received 4 new comments.
-
Drop duplicate PermissionState definition w3c/deviceorientation#88 (4 comments by @FluorescentHallucinogen, @rakuco, @reillyeon)
-
w3c/battery
-
2 pull requests opened.
-
Set respecConfig.github w3c/battery#50, by @rakuco.
-
editorial: Use Web IDL's definition conventions for methods and getters. w3c/battery#49, by @rakuco.
-
-
2 pull requests merged.
-
Set respecConfig.github w3c/battery#50.
-
-
1 pull request received 7 new comments.
-
editorial: Use Web IDL's definition conventions for methods and getters. w3c/battery#49 (7 comments by @anssiko, @rakuco, @xfq)
-
w3c/device-posture
-
1 issue opened.
-
Do developers want to identify when a device is being used with a pen / drawing posture? w3c/device-posture#96, by @diekus.
-
-
2 issues received 2 new comments.
-
Do developers want to identify when a device is being used with a pen / drawing posture? w3c/device-posture#96 (1 comment by @chris480)
-
1 pull request opened.
-
Adding a contributor w3c/device-posture#97, by @torgo.
-
-
1 pull request merged.
-
Adding a contributor w3c/device-posture#97.
-
-
2 pull requests received 2 new comments.
-
w3c/device-posture#98 (1 comment by @w3cbot)
-
TR publications
-
1 document published.
-
Geolocation API published as a Working Draft. History of Geolocation API
-
Past meetings
Participants
-
1 participant joined.
-
Juha Vainio (Intel Corporation) joined.
-
-
1 participant left.
-
Nick Doty (W3C Invited Experts) left.
-
GitHub
w3c/ambient-light
-
1 issue received 1 new comment.
w3c/device-posture
-
1 issue opened.
-
Heads up: refs to `pagevisibility` about to be removed w3c/device-posture#95, by @noamr.
-
-
1 issue closed.
-
Device Posture API to include "Semantic Postures"? w3c/device-posture#94.
-
-
1 issue received 2 new comments.
-
Device Posture API to include "Semantic Postures"? w3c/device-posture#94 (2 comments by @darktears, @diekus)
-
w3c/screen-wake-lock
-
1 issue opened.
-
Add a note about brightness w3c/screen-wake-lock#329, by @marcoscaceres.
-
-
2 issues received 9 new comments.
-
Need maximum screen brightness mode w3c/screen-wake-lock#129 (8 comments by @beaufortfrancois, @marcoscaceres, @rakuco)
-
-
1 pull request opened.
-
editorial: Readd text saying requests may be denied based on battery level w3c/screen-wake-lock#328, by @rakuco.
-
-
1 pull request merged.
-
editorial: Readd text saying requests may be denied based on battery level w3c/screen-wake-lock#328.
-
-
3 pull requests received 7 new comments.
-
editorial: Readd text saying requests may be denied based on battery level w3c/screen-wake-lock#328 (4 comments by @marcoscaceres, @rakuco)
-
w3c/geolocation
-
1 issue opened.
-
Specify behavior for operating system permissions w3c/geolocation#107, by @reillyeon.
-
-
1 issue closed.
-
Consider using DOMHighResTimestamp instead of DOMTimeStamp w3c/geolocation#103.
-
-
1 issue received 2 new comments.
-
Consider using DOMHighResTimestamp instead of DOMTimeStamp w3c/geolocation#103 (2 comments by @npm1)
-
-
1 pull request merged.
-
Switch DOMTimeStamp to EpochTimeStamp w3c/geolocation#104.
-
-
1 pull request received 3 new comments.
w3c/deviceorientation
-
1 pull request opened.
-
Use Permission Spec's PermissionState w3c/deviceorientation#101, by @marcoscaceres.
-
-
1 pull request closed.
-
Use Permission Spec's PermissionState w3c/deviceorientation#101.
-
-
1 pull request received 2 new comments.
-
Use Permission Spec's PermissionState w3c/deviceorientation#101 (2 comments by @marcoscaceres, @rakuco)
-
w3c/das-wg
-
1 issue received 3 new comments.
TR publications
-
11 documents published.
-
Accelerometer published as a Candidate Recommendation Draft. History of Accelerometer
-
Gyroscope published as a Candidate Recommendation Draft. History of Gyroscope
-
Geolocation API published as a Working Draft. History of Geolocation API
-
Screen Wake Lock API published twice as a Working Draft. History of Screen Wake Lock API
-
Battery Status API published as a Working Draft. History of Battery Status API
-
Ambient Light Sensor published as a Working Draft. History of Ambient Light Sensor
-
Proximity Sensor published as a Working Draft. History of Proximity Sensor
-
Geolocation Sensor published as a Working Draft. History of Geolocation Sensor
-
Magnetometer published as a Working Draft. History of Magnetometer
-
Orientation Sensor published as a Working Draft. History of Orientation Sensor
-
Participants
-
1 participant left.
-
Alexandre Gouaillard (CoSMo Software Consulting Pte Ltd) left.
-
GitHub
w3c/geolocation
-
1 issue reopened.
-
Section 3: Why only "SHOULD" for protection of privacy? w3c/geolocation#54, by @samuelweiler.
-
-
2 issues received 7 new comments.
-
Suggest permission lifetimes? w3c/geolocation#69 (5 comments by @anssiko, @marcoscaceres, @pes10k, @samuelweiler)
-
Section 3: Why only "SHOULD" for protection of privacy? w3c/geolocation#54 (2 comments by @marcoscaceres, @samuelweiler)
-
-
2 pull requests opened.
-
Editorial: update permission policy usage w3c/geolocation#105, by @marcoscaceres.
-
Switch DOMTimeStamp to EpochTimeStamp w3c/geolocation#104, by @marcoscaceres.
-
-
1 pull request merged.
-
Editorial: update permission policy usage w3c/geolocation#105.
-
-
3 pull requests received 5 new comments.
-
Editorial: update permission policy usage w3c/geolocation#105 (3 comments by @marcoscaceres, @reillyeon)
-
w3c/geolocation#106 (1 comment by @w3cbot)
-
w3c/screen-wake-lock
-
1 issue opened.
-
Add a state transition diagram w3c/screen-wake-lock#325, by @marcoscaceres.
-
-
1 issue closed.
-
Recommend some UI indicator for when wake lock is active w3c/screen-wake-lock#282.
-
-
2 issues received 14 new comments.
-
Need maximum screen brightness mode w3c/screen-wake-lock#129 (13 comments by @beaufortfrancois, @daniel-fahl, @marcoscaceres, @tomayac)
-
Recommend some UI indicator for when wake lock is active w3c/screen-wake-lock#282 (1 comment by @marcoscaceres)
-
-
1 pull request opened.
-
Remove permission check w3c/screen-wake-lock#326, by @marcoscaceres.
-
-
1 pull request merged.
-
Cleanup priv-sec wording + recommend an indicator w3c/screen-wake-lock#323.
-
-
3 pull requests received 15 new comments.
-
Remove permission check w3c/screen-wake-lock#326 (7 comments by @marcoscaceres, @rakuco, @reillyeon)
-
Cleanup priv-sec wording + recommend an indicator w3c/screen-wake-lock#323 (7 comments by @David-Chadwick, @marcoscaceres, @rakuco)
-
w3c/screen-wake-lock#327 (1 comment by @w3cbot)
-
w3c/ambient-light
-
1 issue opened.
-
I can't use it for my time telling bot project w3c/ambient-light#69, by @Aayam555.
-
-
1 issue closed.
-
I can't use it for my time telling bot project w3c/ambient-light#69.
-
-
3 issues received 10 new comments.
-
Consider making granularity of the data normative w3c/ambient-light#63 (5 comments by @anssiko, @cynthia, @jonathanKingston, @rakuco, @sandandsnow)
-
Request for Ambient Light Sensor web developer feedback w3c/ambient-light#64 (4 comments by @anssiko, @marcoscaceres, @rakuco)
-
-
1 pull request opened.
-
Make default allowlist normative w3c/ambient-light#68, by @anssiko.
-
-
1 pull request merged.
-
Make default allowlist normative w3c/ambient-light#68.
-
w3c/das-wg
-
1 issue received 4 new comments.
-
Devices and Sensors WG - TPAC 2021 agenda w3c/das-wg#47 (4 comments by @anssiko, @darktears, @marcoscaceres)
-
-
3 pull requests opened.
-
Update Compute Pressure API links w3c/das-wg#50, by @anssiko.
-
Update latest TR dates using W3C API integration w3c/das-wg#49, by @anssiko.
-
Roadmap refresh w3c/das-wg#48, by @anssiko.
-
-
3 pull requests merged.
-
Update Compute Pressure API links w3c/das-wg#50.
-
Update latest TR dates using W3C API integration w3c/das-wg#49.
-
Roadmap refresh w3c/das-wg#48.
-
-
1 pull request received 2 new comments.
w3c/compute-pressure
-
1 issue opened.
-
No indication of max amount of thresholds available per metrics. w3c/compute-pressure#11, by @arskama.
-
w3c/device-posture
-
1 issue opened.
-
Device Posture API to include "Semantic Postures"? w3c/device-posture#94, by @diekus.
-
-
2 issues received 10 new comments.
-
Device Posture API to include "Semantic Postures"? w3c/device-posture#94 (9 comments by @anssiko, @chris480, @diekus, @kenchris, @lauramorinigo, @reillyeon, @torgo)
-
w3c/das-charter
-
1 pull request opened.
-
Fix Compute Pressure API URLs w3c/das-charter#121, by @anssiko.
-
w3c/sensors
-
1 issue opened.
-
Support non-"fully active" documents w3c/sensors#415, by @anssiko.
-
w3c/battery
-
2 issues opened.
-
BatteryManager: Describe instance creation in an algorithm w3c/battery#48, by @rakuco.
-
-
1 pull request opened.
-
editorial: Modernize and replace prose with algorithms in BatteryManager w3c/battery#46, by @rakuco.
-
-
1 pull request merged.
-
1 pull request received 26 new comments.
-
editorial: Modernize and replace prose with algorithms in BatteryManager w3c/battery#46 (26 comments by @anssiko, @marcoscaceres, @rakuco, @reillyeon)
-
w3c/proximity
-
1 pull request opened.
-
Make default allowlist normative w3c/proximity#52, by @anssiko.
-
-
1 pull request merged.
-
Make default allowlist normative w3c/proximity#52.
-
w3c/accelerometer
-
1 pull request merged.
-
Make default allowlist normative w3c/accelerometer#61.
-
-
1 pull request closed.
-
Add a Permissions Policy Integration section w3c/accelerometer#60.
-
-
1 pull request received 4 new comments.
w3c/orientation-sensor
-
1 pull request opened.
-
Make default allowlist normative w3c/orientation-sensor#74, by @anssiko.
-
-
1 pull request merged.
-
Make default allowlist normative w3c/orientation-sensor#74.
-
w3c/magnetometer
-
1 pull request opened.
-
Make default allowlist normative w3c/magnetometer#57, by @anssiko.
-
-
1 pull request merged.
-
Make default allowlist normative w3c/magnetometer#57.
-
w3c/gyroscope
-
1 pull request opened.
-
Make default allowlist normative w3c/gyroscope#46, by @anssiko.
-
-
1 pull request merged.
-
Make default allowlist normative w3c/gyroscope#46.
-
w3c/html-media-capture
-
1 issue opened.
-
No way of setting image resolution w3c/html-media-capture#39, by @ronreiter.
-
-
1 issue received 2 new comments.
TR publications
-
16 documents published.
-
Battery Status API published 7 times as a Working Draft. History of Battery Status API
-
Screen Wake Lock API published as a Working Draft. History of Screen Wake Lock API
-
Proximity Sensor published twice as a Working Draft. History of Proximity 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
-
Orientation Sensor published twice as a Working Draft. History of Orientation Sensor
-
Geolocation API published as a Working Draft. History of Geolocation API
-
Device Posture API published as a Working Draft. History of Device Posture API
-
GitHub
w3c/battery
-
1 issue closed.
-
make privacy mitigations normative w3c/battery#27.
-
-
1 issue received 4 new comments.
-
9 pull requests opened.
-
editorial: Modernize the section covering Navigator.getBattery(). w3c/battery#45, by @rakuco.
-
editorial: Remove Web IDL paragraph from Conformance section. w3c/battery#44, by @rakuco.
-
Make privacy mitigations normative w3c/battery#43, by @anssiko.
-
editorial: Remove reference to getBattery() from Permissions Policy section w3c/battery#42, by @rakuco.
-
chore: Reformat index.html and run tidy on pull requests w3c/battery#41, by @rakuco.
-
editorial: Add IDL index and terms index as appendices. w3c/battery#40, by @rakuco.
-
editorial: Add xref to respecConfig, remove duplicate terms from Terminology w3c/battery#39, by @rakuco.
-
Chore: update the SoTD w3c/battery#38, by @xfq.
-
Chore: update the SoTD w3c/battery#37, by @xfq.
-
-
10 pull requests merged.
-
Make privacy mitigations normative w3c/battery#43.
-
editorial: Remove Web IDL paragraph from Conformance section. w3c/battery#44.
-
chore: Reformat index.html and run tidy on pull requests w3c/battery#41.
-
editorial: Add IDL index and terms index as appendices. w3c/battery#40.
-
Chore: update the SoTD w3c/battery#38.
-
Chore: update the SoTD w3c/battery#37.
-
Enable automated publication system w3c/battery#36.
-
5 pull requests received 16 new comments.
-
chore: Reformat index.html and run tidy on pull requests w3c/battery#41 (9 comments by @anssiko, @marcoscaceres, @rakuco, @xfq)
-
editorial: Modernize the section covering Navigator.getBattery(). w3c/battery#45 (4 comments by @rakuco, @reillyeon)
-
editorial: Remove reference to getBattery() from Permissions Policy section w3c/battery#42 (1 comment by @anssiko)
-
w3c/geolocation
-
1 issue opened.
-
Consider using DOMHighResTimestamp instead of DOMTimeStamp w3c/geolocation#103, by @yoavweiss.
-
-
1 issue closed.
-
Looking for test suite maintainers for geo API w3c/geolocation#99.
-
-
1 issue reopened.
-
Suggest permission lifetimes? w3c/geolocation#69, by @marcoscaceres.
-
-
5 issues received 22 new comments.
-
Suggest permission lifetimes? w3c/geolocation#69 (8 comments by @johannhof, @marcoscaceres, @tomayac, @yoavweiss)
-
Consider using DOMHighResTimestamp instead of DOMTimeStamp w3c/geolocation#103 (3 comments by @marcoscaceres, @yoavweiss)
-
-
1 pull request opened.
-
chore: add change log since FPWD w3c/geolocation#102, by @marcoscaceres.
-
-
1 pull request merged.
-
chore: add change log since FPWD w3c/geolocation#102.
-
-
2 pull requests received 4 new comments.
-
Callback with error if doc is not fully active w3c/geolocation#97 (3 comments by @marcoscaceres, @reillyeon)
-
w3c/sensors
-
1 issue closed.
-
Update the reference to Feature Policy w3c/sensors#405.
-
-
2 issues received 4 new comments.
w3c/accelerometer
-
1 pull request opened.
-
Make default allowlist normative w3c/accelerometer#61, by @anssiko.
-
w3c/screen-wake-lock
-
1 issue opened.
-
Should this prompt? w3c/screen-wake-lock#324, by @marcoscaceres.
-
-
10 issues closed.
-
Turn on screen and screen lock from system lock or the like w3c/screen-wake-lock#130.
-
Introduce rate limiting to prevent wake lock abuse w3c/screen-wake-lock#124.
-
Be able to query if there are any screen wake-lock object active for the current page w3c/screen-wake-lock#273.
-
Navigation and maintaining locks w3c/screen-wake-lock#249.
-
request(): Order for permission and other checks w3c/screen-wake-lock#202.
-
User prompts to show an active screen-lock should have an associated domain w3c/screen-wake-lock#278.
-
screen wake lock should be able to make use of proximy sensor w3c/screen-wake-lock#175.
-
Figure out what to do with workers and permission requests w3c/screen-wake-lock#246.
-
Need to add "wake-lock" to permissions registry w3c/screen-wake-lock#184.
-
Publish a new Candidate Recommendation w3c/screen-wake-lock#262.
-
-
1 issue reopened.
-
Recommend some UI indicator for when wake lock is active w3c/screen-wake-lock#282, by @marcoscaceres.
-
-
13 issues received 36 new comments.
-
Recommend some UI indicator for when wake lock is active w3c/screen-wake-lock#282 (8 comments by @David-Chadwick, @marcoscaceres)
-
Should this prompt? w3c/screen-wake-lock#324 (6 comments by @marcoscaceres, @martinthomson, @rakuco, @reillyeon)
-
Be able to query if there are any screen wake-lock object active for the current page w3c/screen-wake-lock#273 (5 comments by @marcoscaceres, @reillyeon)
-
WakeLock and only require activation once w3c/screen-wake-lock#139 (4 comments by @marcoscaceres, @rakuco, @reillyeon)
-
User prompts to show an active screen-lock should have an associated domain w3c/screen-wake-lock#278 (3 comments by @marcoscaceres, @xfq)
-
Turn on screen and screen lock from system lock or the like w3c/screen-wake-lock#130 (2 comments by @marcoscaceres, @tomayac)
-
Need to add "wake-lock" to permissions registry w3c/screen-wake-lock#184 (2 comments by @marcoscaceres, @rakuco)
-
Introduce rate limiting to prevent wake lock abuse w3c/screen-wake-lock#124 (1 comment by @marcoscaceres)
-
request(): Order for permission and other checks w3c/screen-wake-lock#202 (1 comment by @marcoscaceres)
-
screen wake lock should be able to make use of proximy sensor w3c/screen-wake-lock#175 (1 comment by @marcoscaceres)
-
Figure out what to do with workers and permission requests w3c/screen-wake-lock#246 (1 comment by @marcoscaceres)
-
-
2 pull requests opened.
-
Cleanup priv-sec wording + recommend an indicator w3c/screen-wake-lock#323, by @marcoscaceres.
-
Handle garbage collection w3c/screen-wake-lock#322, by @marcoscaceres.
-
-
1 pull request merged.
-
Handle garbage collection w3c/screen-wake-lock#322.
-
-
2 pull requests received 11 new comments.
-
Cleanup priv-sec wording + recommend an indicator w3c/screen-wake-lock#323 (6 comments by @David-Chadwick, @rakuco, @reillyeon)
-
Handle garbage collection w3c/screen-wake-lock#322 (5 comments by @marcoscaceres, @rakuco, @reillyeon)
-
w3c/vibration
-
1 issue closed.
-
Vibration does not work in silent mode. w3c/vibration#28.
-
-
1 issue received 2 new comments.
w3c/system-wake-lock
-
1 issue opened.
-
Can a system wake lock trigger a screen wake lock (that is, wake up the screen)? w3c/system-wake-lock#12, by @tomayac.
-
w3c/das-charter
-
1 issue closed.
-
DASWG: Drop Network Information API because it is harmful to the web w3c/das-charter#105.
-
-
1 issue reopened.
-
DASWG: Drop Network Information API because it is harmful to the web w3c/das-charter#105, by @anssiko.
-
-
2 issues received 5 new comments.
-
DASWG: Drop Network Information API because it is harmful to the web w3c/das-charter#105 (4 comments by @anssiko, @marcoscaceres, @tomayac)
-
-
2 pull requests opened.
-
Make Contact Picker API a joint deliverable w3c/das-charter#120, by @xfq.
-
Add Audio WG as a liaison w3c/das-charter#119, by @xfq.
-
-
2 pull requests merged.
-
Add Audio WG as a liaison w3c/das-charter#119.
-
Make Contact Picker API a joint deliverable w3c/das-charter#120.
-
-
1 pull request received 5 new comments.
w3c/proximity
-
2 pull requests opened.
-
Chore: update the SoTD w3c/proximity#51, by @xfq.
-
Chore: update the SoTD w3c/proximity#50, by @xfq.
-
-
2 pull requests merged.
-
Chore: update the SoTD w3c/proximity#51.
-
Chore: update the SoTD w3c/proximity#50.
-
w3c/ambient-light
-
1 pull request opened.
-
Chore: update the SoTD w3c/ambient-light#67, by @xfq.
-
-
1 pull request merged.
-
Chore: update the SoTD w3c/ambient-light#67.
-
w3c/orientation-sensor
-
1 pull request opened.
-
Chore: update the SoTD w3c/orientation-sensor#73, by @xfq.
-
-
1 pull request merged.
-
Chore: update the SoTD w3c/orientation-sensor#73.
-
w3c/contact-picker
-
2 issues opened.
-
Handling contact addresses w3c/contact-picker#43, by @rayankans.
-
Transplant PaymentAddress into ContactInfo w3c/contact-picker#42, by @marcoscaceres.
-
-
2 issues closed.
-
Handling contact addresses w3c/contact-picker#43.
-
Transplant PaymentAddress into ContactInfo w3c/contact-picker#42.
-
-
4 issues received 9 new comments.
-
Migrate into a working group w3c/contact-picker#37 (4 comments by @marcoscaceres, @plehegar, @rayankans)
-
Transplant PaymentAddress into ContactInfo w3c/contact-picker#42 (3 comments by @marcoscaceres, @rayankans)
-
-
2 pull requests opened.
-
Remove references to #43. w3c/contact-picker#45, by @rayankans.
-
docs(README): remove outdated IDL w3c/contact-picker#44, by @marcoscaceres.
-
-
4 pull requests merged.
-
Remove references to #43. w3c/contact-picker#45.
-
docs(README): remove outdated IDL w3c/contact-picker#44.
-
Fix SecureContext extended attribute w3c/contact-picker#41.
-
Move Address definitions/interfaces from the Payment Request API. w3c/contact-picker#39.
-
-
1 pull request received 2 new comments.
-
Move Address definitions/interfaces from the Payment Request API. w3c/contact-picker#39 (2 comments by @marcoscaceres, @rayankans)
-
w3c/device-posture
-
2 issues opened.
-
Naming of this spec w3c/device-posture#93, by @xfq.
-
Polyfill should be updated to device-posture w3c/device-posture#91, by @lauramorinigo.
-
-
1 issue closed.
-
Polyfill should be updated to device-posture w3c/device-posture#91.
-
-
1 issue received 4 new comments.
-
1 pull request opened.
-
Polyfill update w3c/device-posture#92, by @lauramorinigo.
-
-
1 pull request merged.
-
Polyfill update w3c/device-posture#92.
-
TR publications
-
12 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 as a Candidate Recommendation Draft. History of Gyroscope
-
Geolocation API published 5 times as a Working Draft. History of Geolocation API
-
Orientation Sensor published as a Working Draft. History of Orientation Sensor
-
Magnetometer published as a Working Draft. History of Magnetometer
-
Device Posture API published as a Working Draft. History of Device Posture API
-
Participants
-
1 participant left.
-
Peter Burrows (Fiserv) left.
-
-
1 organization left.
-
Fiserv left.
-
GitHub
w3c/geolocation
-
4 issues opened.
-
Looking for test suite maintainers for geo API w3c/geolocation#99, by @marcoscaceres.
-
Error when method are called on not fully active docs w3c/geolocation#96, by @marcoscaceres.
-
Harmonize error code for watchPosition() w3c/geolocation#95, by @marcoscaceres.
-
Republish as CR w3c/geolocation#93, by @marcoscaceres.
-
-
6 issues closed.
-
Harmonize error code for watchPosition() w3c/geolocation#95.
-
Error when method are called on not fully active docs w3c/geolocation#96.
-
Deal with not fully active documents w3c/geolocation#78.
-
Callbacks are invoked while in parallel w3c/geolocation#80.
-
Background Geolocation w3c/geolocation#74.
-
Change text for description of GeolocationPositionError.message attribute w3c/geolocation#50.
-
-
1 issue reopened.
-
Harmonize error code for watchPosition() w3c/geolocation#95, by @marcoscaceres.
-
-
6 issues received 12 new comments.
-
Require user activation to use API w3c/geolocation#48 (5 comments by @marcoscaceres, @reillyeon, @Tom333Trinity)
-
Error when method are called on not fully active docs w3c/geolocation#96 (1 comment by @marcoscaceres)
-
Change text for description of GeolocationPositionError.message attribute w3c/geolocation#50 (1 comment by @marcoscaceres)
-
-
3 pull requests opened.
-
Return 0 when watchPosition() errors w3c/geolocation#100, by @marcoscaceres.
-
Callback with error if doc is not fully active w3c/geolocation#97, by @marcoscaceres.
-
Require transient activation to use API w3c/geolocation#94, by @marcoscaceres.
-
-
4 pull requests merged.
-
Return 0 when watchPosition() errors w3c/geolocation#100.
-
Callback with error if doc is not fully active w3c/geolocation#97.
-
Gracefully handle documents that are not fully active w3c/geolocation#90.
-
Add "geolocation task queue" w3c/geolocation#87.
-
-
6 pull requests received 23 new comments.
-
Gracefully handle documents that are not fully active w3c/geolocation#90 (9 comments by @marcoscaceres, @rakina, @reillyeon)
-
Callback with error if doc is not fully active w3c/geolocation#97 (8 comments by @marcoscaceres, @reillyeon, @saschanaz)
-
Require transient activation to use API w3c/geolocation#94 (2 comments by @marcoscaceres, @reillyeon)
-
w3c/geolocation#98 (1 comment by @w3cbot)
-
w3c/geolocation#91 (1 comment by @w3cbot)
-
w3c/sensors
-
1 issue opened.
-
Auto-publish the spec w3c/sensors#413, by @xfq.
-
-
1 issue closed.
-
Auto-publish the spec w3c/sensors#413.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Export "generic sensor permission revocation algorithm" w3c/sensors#414, by @marcoscaceres.
-
-
2 pull requests merged.
-
Export "generic sensor permission revocation algorithm" w3c/sensors#414.
-
Fix broken links w3c/sensors#412.
-
w3c/device-posture
-
1 issue opened.
-
logos are preventing auto-publish w3c/device-posture#90, by @marcoscaceres.
-
-
2 issues received 2 new comments.
-
Adding fold position to identify orientation instead of identify device model w3c/device-posture#63 (1 comment by @darktears)
-
-
4 pull requests opened.
-
chore: cleanup root dir w3c/device-posture#89, by @marcoscaceres.
-
chore: add tidy workflow w3c/device-posture#88, by @marcoscaceres.
-
From Diego: Deletes unnecessary images w3c/device-posture#87, by @kenchris.
-
Deletes unnecessary images w3c/device-posture#86, by @diekus.
-
-
5 pull requests merged.
-
chore: add tidy workflow w3c/device-posture#88.
-
chore: cleanup root dir w3c/device-posture#89.
-
chore: fixup internal slots w3c/device-posture#80.
-
chore: rename pr-push.yml to auto-publish.yml w3c/device-posture#76.
-
From Diego: Deletes unnecessary images w3c/device-posture#87.
-
-
2 pull requests closed.
-
Deletes unnecessary images w3c/device-posture#86.
-
Updates postures. w3c/device-posture#83.
-
-
3 pull requests received 6 new comments.
-
chore: rename pr-push.yml to auto-publish.yml w3c/device-posture#76 (3 comments by @kenchris, @marcoscaceres)
-
w3c/vibration
-
1 issue opened.
-
Vibration does not work in silent mode. w3c/vibration#28, by @doong-jo.
-
w3c/html-media-capture
-
1 pull request opened.
-
Avoid using company names to express when an editor retired. w3c/html-media-capture#38, by @jyasskin.
-
-
1 pull request merged.
-
Avoid using company names to express when an editor retired. w3c/html-media-capture#38.
-
w3c/das-wg
-
1 issue opened.
-
Devices and Sensors WG - TPAC 2021 agenda w3c/das-wg#47, by @reillyeon.
-
-
2 issues closed.
-
Devices and Sensors WG - 2021 Q2 virtual meeting w3c/das-wg#39.
-
Devices and Sensors WG - TPAC 2020 agenda w3c/das-wg#31.
-
w3c/deviceorientation
-
3 issues opened.
-
Automatic publishing broken due to Specberus errors w3c/deviceorientation#100, by @reillyeon.
-
Example 9 doesn't match the situation w3c/deviceorientation#98, by @chaals.
-
Opposite z-axis for example 7 w3c/deviceorientation#96, by @jipodine.
-
-
1 issue closed.
-
Example 9 doesn't match the situation w3c/deviceorientation#98.
-
-
2 issues received 8 new comments.
-
2 pull requests opened.
-
Fix example 9 w3c/deviceorientation#99, by @chaals.
-
DeviceMotionEvent: Add a note about acceleration properties. w3c/deviceorientation#97, by @rakuco.
-
-
2 pull requests merged.
-
Fix example 9 w3c/deviceorientation#99.
-
DeviceMotionEvent: Add a note about acceleration properties. w3c/deviceorientation#97.
-
-
2 pull requests received 5 new comments.
-
DeviceMotionEvent: Add a note about acceleration properties. w3c/deviceorientation#97 (3 comments by @rakuco, @reillyeon)
-
w3c/das-charter
-
1 issue received 2 new comments.
-
DASWG: Drop Ambient light sensor API for privacy and lack of implementer support w3c/das-charter#100 (2 comments by @brianhumphreys, @rakuco)
-
w3c/contact-picker
-
1 issue received 1 new comment.
TR publications
-
19 documents published.
-
Generic Sensor API published as a Candidate Recommendation Draft. History of Generic Sensor API
-
Screen Wake Lock API published 6 times as a Working Draft. History of Screen Wake Lock API
-
Geolocation API published 4 times as a Working Draft. History of Geolocation API
-
Orientation Sensor published as a Working Draft. History of Orientation Sensor
-
Ambient Light Sensor published twice as a Working Draft. History of Ambient Light Sensor
-
Proximity Sensor published twice as a Working Draft. History of Proximity Sensor
-
Device Posture API published as a Working Draft. History of Device Posture API
-
Geolocation Sensor published as a Working Draft. History of Geolocation Sensor
-
Battery Status API published as a Working Draft. History of Battery Status API
-
Participants
-
1 participant joined.
-
Arnaud Mandy (Intel Corporation) joined.
-
GitHub
w3c/device-posture
-
3 issues opened.
-
We need to add more examples in the explainer w3c/device-posture#79, by @darktears.
-
Fetching the posture type should be async? w3c/device-posture#78, by @darktears.
-
Linking to plural forms w3c/device-posture#77, by @xfq.
-
-
4 issues closed.
-
Improve fingerprinting of screen fold changes w3c/device-posture#46.
-
environment variable might be useless w3c/device-posture#11.
-
Clarify posture may be derived from sensors w3c/device-posture#57.
-
[admin] Enable auto-publish w3c/device-posture#55.
-
-
4 issues received 12 new comments.
-
Fetching the posture type should be async? w3c/device-posture#78 (5 comments by @darktears, @kenchris, @reillyeon)
-
-
9 pull requests opened.
-
Update README.md w3c/device-posture#85, by @diekus.
-
Update Affiliation for Diego w3c/device-posture#84, by @diekus.
-
Updates postures. w3c/device-posture#83, by @diekus.
-
updates the explainer w3c/device-posture#82, by @diekus.
-
Device Posture update w3c/device-posture#81, by @diekus.
-
chore: fixup internal slots w3c/device-posture#80, by @marcoscaceres.
-
chore: rename pr-push.yml to auto-publish.yml w3c/device-posture#76, by @marcoscaceres.
-
Closes #46: Use internal slot w3c/device-posture#75, by @kenchris.
-
Add info about using additional signals w3c/device-posture#73, by @kenchris.
-
-
6 pull requests merged.
-
Update README.md w3c/device-posture#85.
-
Update Affiliation for Diego w3c/device-posture#84.
-
updates the explainer w3c/device-posture#82.
-
Device Posture update w3c/device-posture#81.
-
Closes #46: Use internal slot w3c/device-posture#75.
-
Add info about using additional signals w3c/device-posture#73.
-
-
3 pull requests received 15 new comments.
-
updates the explainer w3c/device-posture#82 (8 comments by @darktears, @diekus, @kenchris, @lauramorinigo)
-
w3c/contact-picker
-
1 pull request opened.
-
Fix SecureContext extended attribute w3c/contact-picker#41, by @dontcallmedom.
-
w3c/screen-wake-lock
-
2 issues closed.
-
In obtain permission: don't co-opt resultPromise - it's creating a custom permission model w3c/screen-wake-lock#198.
-
Implementation report needs to be updated w3c/screen-wake-lock#313.
-
-
2 issues received 6 new comments.
-
Need maximum screen brightness mode w3c/screen-wake-lock#129 (3 comments by @marcoscaceres, @willmorgan)
-
-
6 pull requests opened.
-
Adapt to ReSpec's new syntax for internal slots. w3c/screen-wake-lock#321, by @rakuco.
-
editorial: Reference the "external now hidden" algorithm from Page Visibility w3c/screen-wake-lock#320, by @rakuco.
-
Revert "workflows/tidy: Run on ubuntu-20.04. (#317)" w3c/screen-wake-lock#319, by @rakuco.
-
workflows/tidy: Run on ubuntu-20.04. w3c/screen-wake-lock#317, by @rakuco.
-
chore(workflows/tidy): tidy document on PR w3c/screen-wake-lock#316, by @marcoscaceres.
-
chore: clean up repo root w3c/screen-wake-lock#315, by @marcoscaceres.
-
-
8 pull requests merged.
-
Adapt to ReSpec's new syntax for internal slots. w3c/screen-wake-lock#321.
-
editorial: Reference the "external now hidden" algorithm from Page Visibility w3c/screen-wake-lock#320.
-
editorial: Remove the "obtain a permission" algorithm. w3c/screen-wake-lock#298.
-
Revert "workflows/tidy: Run on ubuntu-20.04. (#317)" w3c/screen-wake-lock#319.
-
workflows/tidy: Run on ubuntu-20.04. w3c/screen-wake-lock#317.
-
chore: clean up repo root w3c/screen-wake-lock#315.
-
chore(workflows/tidy): tidy document on PR w3c/screen-wake-lock#316.
-
Switch to w3c/spec-prod to automate publication to /TR w3c/screen-wake-lock#314.
-
-
6 pull requests received 20 new comments.
-
editorial: Remove the "obtain a permission" algorithm. w3c/screen-wake-lock#298 (5 comments by @marcoscaceres, @rakuco)
-
chore(workflows/tidy): tidy document on PR w3c/screen-wake-lock#316 (4 comments by @marcoscaceres, @rakuco)
-
workflows/tidy: Run on ubuntu-20.04. w3c/screen-wake-lock#317 (2 comments by @marcoscaceres, @rakuco)
-
Revert "workflows/tidy: Run on ubuntu-20.04. (#317)" w3c/screen-wake-lock#319 (2 comments by @marcoscaceres, @rakuco)
w3c/orientation-sensor
-
1 issue opened.
-
Broken link w3c/orientation-sensor#71, by @xfq.
-
-
1 issue closed.
-
Broken link w3c/orientation-sensor#71.
-
-
2 issues received 2 new comments.
-
1 pull request opened.
-
Fix bibliography link w3c/orientation-sensor#72, by @xfq.
-
-
2 pull requests merged.
-
Fix bibliography link w3c/orientation-sensor#72.
-
Chore: update spec metadata w3c/orientation-sensor#70.
-
-
1 pull request received 1 new comment.
w3c/motion-sensors
-
1 pull request opened.
-
Adding example on gravity sensor. w3c/motion-sensors#30, by @arskama.
-
-
1 pull request merged.
-
Adding example on gravity sensor. w3c/motion-sensors#30.
-
-
1 pull request received 4 new comments.
w3c/sensors
-
1 issue opened.
-
money w3c/sensors#410, by @Nathaniel82166.
-
-
1 issue closed.
-
money w3c/sensors#410.
-
-
2 pull requests opened.
-
Fix broken links w3c/sensors#412, by @xfq.
-
Switch to w3c/spec-prod to automate publication to /TR w3c/sensors#411, by @xfq.
-
-
1 pull request merged.
-
Switch to w3c/spec-prod to automate publication to /TR w3c/sensors#411.
-
w3c/geolocation
-
2 issues closed.
-
Nit: clearly indicate implementation-defined behavior w3c/geolocation#82.
-
Nit: new IDL style w3c/geolocation#81.
-
-
2 issues received 7 new comments.
-
Support geolocation (especially geofencing) in the "background" w3c/geolocation#214 (1 comment by @James-E-A)
-
7 pull requests opened.
-
Gracefully handle documents that are not fully active w3c/geolocation#90, by @marcoscaceres.
-
Editorial: cleanup RS config w3c/geolocation#89, by @marcoscaceres.
-
Editorial: use WebIDL style prose for method calls w3c/geolocation#88, by @marcoscaceres.
-
Add "geolocation task queue" w3c/geolocation#87, by @marcoscaceres.
-
Editorial: link up implementation defined w3c/geolocation#86, by @marcoscaceres.
-
Rename pr-push.yml to auto-publish.yml w3c/geolocation#85, by @xfq.
-
Typo Fix on Readme.md w3c/geolocation#84, by @Warin.
-
-
5 pull requests merged.
-
Editorial: cleanup RS config w3c/geolocation#89.
-
Editorial: link up implementation defined w3c/geolocation#86.
-
Editorial: use WebIDL style prose for method calls w3c/geolocation#88.
-
Rename pr-push.yml to auto-publish.yml w3c/geolocation#85.
-
Typo Fix on Readme.md w3c/geolocation#84.
-
-
6 pull requests received 21 new comments.
-
Add "geolocation task queue" w3c/geolocation#87 (10 comments by @annevk, @marcoscaceres, @reillyeon)
-
Editorial: link up implementation defined w3c/geolocation#86 (3 comments by @marcoscaceres, @reillyeon)
-
Gracefully handle documents that are not fully active w3c/geolocation#90 (2 comments by @marcoscaceres, @reillyeon)
-
w3c/das-charter
-
3 pull requests opened.
-
Update draft states w3c/das-charter#118, by @xfq.
-
Add APA as a liaison w3c/das-charter#117, by @xfq.
-
Update Fold Angle Sensor in timeline w3c/das-charter#116, by @xfq.
-
-
4 pull requests merged.
-
Add APA as a liaison w3c/das-charter#117.
-
Update draft states w3c/das-charter#118.
-
Update Fold Angle Sensor in timeline w3c/das-charter#116.
-
flag rename of Fold Angle w3c/das-charter#112.
-
-
2 pull requests received 3 new comments.
w3c/battery
-
1 pull request opened.
-
Enable automated publication system w3c/battery#36, by @xfq.
-
w3c/das-wg
-
3 pull requests opened.
-
Add Orientation Sensor WD w3c/das-wg#46, by @anssiko.
-
Add Proximity Sensor WD w3c/das-wg#45, by @anssiko.
-
Update roadmap with new WDs w3c/das-wg#44, by @anssiko.
-
-
3 pull requests merged.
-
Add Orientation Sensor WD w3c/das-wg#46.
-
Add Proximity Sensor WD w3c/das-wg#45.
-
Update roadmap with new WDs w3c/das-wg#44.
-
w3c/deviceorientation
-
3 pull requests opened.
-
http -> https w3c/deviceorientation#95, by @xfq.
-
Automate publication w3c/deviceorientation#94, by @xfq.
-
Fix reference to HTML spec in devicemotion event description. w3c/deviceorientation#93, by @rakuco.
-
-
3 pull requests merged.
-
Automate publication w3c/deviceorientation#94.
-
http -> https w3c/deviceorientation#95.
-
Fix reference to HTML spec in devicemotion event description. w3c/deviceorientation#93.
-
-
1 pull request received 1 new comment.
-
Fix reference to HTML spec in devicemotion event description. w3c/deviceorientation#93 (1 comment by @anssiko)
-
w3c/ambient-light
-
1 pull request opened.
-
Rename pr-push.yml to auto-publish.yml w3c/ambient-light#66, by @marcoscaceres.
-
-
2 pull requests merged.
-
Rename pr-push.yml to auto-publish.yml w3c/ambient-light#66.
-
Add Status Text for WD publication w3c/ambient-light#65.
-
-
1 pull request received 1 new comment.
w3c/proximity
-
1 pull request opened.
-
chore: rename pr-push.yml to auto-publish.yml w3c/proximity#49, by @marcoscaceres.
-
-
2 pull requests merged.
-
chore: rename pr-push.yml to auto-publish.yml w3c/proximity#49.
-
Add Status Text for WD publication w3c/proximity#48.
-
-
2 pull requests received 2 new comments.
TR publications
-
6 documents published.
-
Ambient Light Sensor published as a Working Draft. History of Ambient Light Sensor
-
Geolocation API published as a Working Draft. History of Geolocation API
-
Proximity Sensor published twice as a Working Draft. History of Proximity Sensor
-
Device Posture API published as a Working Draft. History of Device Posture API
-
Geolocation API published as a First Public Working Draft. History of Geolocation API
-
Participants
-
2 participants joined.
-
George Menzel (Microsoft Corporation) joined.
-
Sathyanarayan Karivaradaswamy (Microsoft Corporation) joined.
-
GitHub
w3c/geolocation
-
7 issues opened.
-
Nit: clearly indicate implementation-defined behavior w3c/geolocation#82, by @annevk.
-
Nit: new IDL style w3c/geolocation#81, by @annevk.
-
Callbacks are invoked while in parallel w3c/geolocation#80, by @annevk.
-
Deal with not fully active documents w3c/geolocation#78, by @marcoscaceres.
-
Permissions Policy integration incomplete w3c/geolocation#75, by @annevk.
-
Background Geolocation w3c/geolocation#74, by @Tom333Trinity.
-
Geolocation API banned for Iranian users w3c/geolocation#73, by @Navid61.
-
-
6 issues closed.
-
[meta] Wide review tracker - FPWD w3c/geolocation#43.
-
Publish as FPWD w3c/geolocation#42.
-
Broken fragments w3c/geolocation#71.
-
Permissions Policy integration incomplete w3c/geolocation#75.
-
Geolocation API banned for Iranian users w3c/geolocation#73.
-
Broken link w3c/geolocation#70.
-
-
2 issues reopened.
-
Change text for description of GeolocationPositionError.message attribute w3c/geolocation#50, by @marcoscaceres.
-
Background Geolocation w3c/geolocation#74, by @marcoscaceres.
-
-
10 issues received 41 new comments.
-
Background Geolocation w3c/geolocation#74 (11 comments by @jyasskin, @marcoscaceres, @Tom333Trinity)
-
Publish as FPWD w3c/geolocation#42 (9 comments by @anssiko, @deniak, @marcoscaceres, @reillyeon, @xfq)
-
Deal with not fully active documents w3c/geolocation#78 (4 comments by @marcoscaceres, @rakina, @Tom333Trinity)
-
Change text for description of GeolocationPositionError.message attribute w3c/geolocation#50 (4 comments by @chaals, @marcoscaceres, @Tom333Trinity)
-
Permissions Policy integration incomplete w3c/geolocation#75 (4 comments by @annevk, @marcoscaceres)
-
Nit: clearly indicate implementation-defined behavior w3c/geolocation#82 (2 comments by @annevk, @marcoscaceres)
-
-
4 pull requests opened.
-
Some suggestions and fixes w3c/geolocation#83, by @tomayac.
-
chore(github/workflows/pr-push): autopub w3c/geolocation#79, by @marcoscaceres.
-
Update the shortname w3c/geolocation#77, by @xfq.
-
Editorial: update test suite link w3c/geolocation#76, by @xfq.
-
-
5 pull requests merged.
-
Some suggestions and fixes w3c/geolocation#83.
-
chore(github/workflows/pr-push): autopub w3c/geolocation#79.
-
Update the shortname w3c/geolocation#77.
-
Editorial: reword .message i18n note w3c/geolocation#72.
-
Editorial: update test suite link w3c/geolocation#76.
-
-
1 pull request received 2 new comments.
w3c/screen-wake-lock
-
1 issue opened.
-
Implementation report needs to be updated w3c/screen-wake-lock#313, by @xfq.
-
-
2 issues received 8 new comments.
-
Need maximum screen brightness mode w3c/screen-wake-lock#129 (7 comments by @dhensby, @marcoscaceres, @mburrett-jumio)
-
-
1 pull request opened.
-
Switch to w3c/spec-prod to automate publication to /TR w3c/screen-wake-lock#314, by @xfq.
-
-
1 pull request received 2 new comments.
-
Switch to w3c/spec-prod to automate publication to /TR w3c/screen-wake-lock#314 (2 comments by @marcoscaceres)
-
w3c/das-charter
-
2 issues opened.
-
consolidate testing and sec/priv lines in Success Criteria w3c/das-charter#114, by @samuelweiler.
-
Adopt separate sec/priv considerations sections (from template) w3c/das-charter#113, by @samuelweiler.
-
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
Mention interest from multiple implementers w3c/das-charter#115, by @xfq.
-
flag rename of Fold Angle w3c/das-charter#112, by @samuelweiler.
-
-
1 pull request merged.
-
Mention interest from multiple implementers w3c/das-charter#115.
-
-
2 pull requests received 2 new comments.
w3c/orientation-sensor
-
1 pull request opened.
-
Chore: update spec metadata w3c/orientation-sensor#70, by @xfq.
-
w3c/ambient-light
-
1 issue received 1 new comment.
-
Request for Ambient Light Sensor web developer feedback w3c/ambient-light#64 (1 comment by @mburrett-jumio)
-
-
1 pull request opened.
-
Add Status Text for WD publication w3c/ambient-light#65, by @xfq.
-
w3c/proximity
-
2 pull requests opened.
-
Add Status Text for WD publication w3c/proximity#48, by @xfq.
-
chore(ci): fix W3C_BUILD_OVERRIDE value w3c/proximity#47, by @sidvishnoi.
-
-
1 pull request closed.
-
chore(ci): fix W3C_BUILD_OVERRIDE value w3c/proximity#47.
-
-
1 pull request received 3 new comments.
-
chore(ci): fix W3C_BUILD_OVERRIDE value w3c/proximity#47 (3 comments by @anssiko, @sidvishnoi, @xfq)
-
w3c/battery
-
1 issue closed.
-
[meta] Publish a revised Candidate Recommendation w3c/battery#12.
-
-
1 issue received 2 new comments.
-
4 pull requests opened.
-
Update link to the test suite w3c/battery#35, by @xfq.
-
http -> https w3c/battery#34, by @xfq.
-
Add w3cid for the editors w3c/battery#33, by @xfq.
-
Chore: update the metadata and SoTD w3c/battery#32, by @xfq.
-
-
4 pull requests merged.
-
Update link to the test suite w3c/battery#35.
-
Add w3cid for the editors w3c/battery#33.
-
http -> https w3c/battery#34.
-
Chore: update the metadata and SoTD w3c/battery#32.
-
-
2 pull requests received 3 new comments.
w3c/html-media-capture
-
1 pull request opened.
-
Chore: fixup some ReSpec usage w3c/html-media-capture#37, by @marcoscaceres.
-
-
1 pull request received 1 new comment.
w3c/das-wg
-
1 pull request opened.
-
Add re-published Geolocation API FPWD w3c/das-wg#43, by @anssiko.
-
-
1 pull request merged.
-
Add re-published Geolocation API FPWD w3c/das-wg#43.
-
w3c/contact-picker
-
1 issue opened.
-
Add a way to obtain oneself w3c/contact-picker#40, by @tomayac.
-
-
2 issues received 2 new comments.
-
Add some security considerations for sites using this API w3c/contact-picker#38 (1 comment by @samuelweiler)
-
1 pull request opened.
-
Move Address definitions/interfaces from the Payment Request API. w3c/contact-picker#39, by @rayankans.
-
-
1 pull request received 3 new comments.
-
Move Address definitions/interfaces from the Payment Request API. w3c/contact-picker#39 (3 comments by @beverloo, @jcayzac, @rayankans)
-
w3c/compute-pressure
-
4 issues opened.
-
Use-case: GPU pressure w3c/compute-pressure#9, by @alexcyn.
-
Use-case: Current process contribution w3c/compute-pressure#8, by @alexcyn.
-
Explain trimming the quantization scheme w3c/compute-pressure#7, by @pwnall.
-
Quantization clarification - how are threshold values handled? w3c/compute-pressure#6, by @pwnall.
-
-
1 issue received 2 new comments.
-
Quantization clarification - how are threshold values handled? w3c/compute-pressure#6 (2 comments by @pwnall)
-
-
2 pull requests opened.
-
Add security/privacy considerations from explainer w3c/compute-pressure#10, by @kenchris.
-
Add @kenchris to author list w3c/compute-pressure#5, by @oyiptong.
-
-
3 pull requests merged.
-
Add security/privacy considerations from explainer w3c/compute-pressure#10.
-
Add @kenchris to author list w3c/compute-pressure#5.
-
Initial spec draft w3c/compute-pressure#4.
-
-
1 pull request received 2 new comments.
w3c/system-wake-lock
-
2 issues opened.
-
Use case: Photo frame webapp w3c/system-wake-lock#9, by @marcofugaro.
-
Use case: develop websites with real-time updates on mobile devices wirelessly w3c/system-wake-lock#8, by @marcofugaro.
-
w3c/device-posture
-
1 issue closed.
-
Definition for "posture" missing w3c/device-posture#59.
-
-
3 pull requests merged.
-
Switch to w3c/spec-prod to automate publication to /TR w3c/device-posture#72.
-
update affiliation for Diego w3c/device-posture#52.
-
Adding posture definition and clarification w3c/device-posture#69.
-
-
2 pull requests received 5 new comments.
Past meetings
-
4 meetings.
Participants
-
1 participant joined.
-
Diego Gonzalez-Zuniga (Microsoft Corporation) joined.
-
-
1 organization joined.
-
Microsoft Corporation joined.
-
GitHub
w3c/device-posture
-
2 issues opened.
-
Requesting Accessibility Considerations section w3c/device-posture#70, by @becka11y.
-
Move the posture object out of the Screen interface. w3c/device-posture#67, by @darktears.
-
-
2 issues closed.
-
Move the posture object out of the Screen interface. w3c/device-posture#67.
-
Rename "posture modes" to "posture types" w3c/device-posture#64.
-
-
3 issues received 13 new comments.
-
Move the posture object out of the Screen interface. w3c/device-posture#67 (10 comments by @anssiko, @beaufortfrancois, @darktears, @kenchris, @lauramorinigo)
-
Rename "posture modes" to "posture types" w3c/device-posture#64 (2 comments by @darktears, @kenchris)
-
-
4 pull requests opened.
-
Switch to w3c/spec-prod to automate publication to /TR w3c/device-posture#72, by @xfq.
-
Move the entry point of the API to the window.navigator interface. w3c/device-posture#71, by @darktears.
-
Adding posture definition and clarification w3c/device-posture#69, by @lauramorinigo.
-
Rename word "mode" in the posture definition to "type". w3c/device-posture#68, by @darktears.
-
-
2 pull requests merged.
-
Move the entry point of the API to the window.navigator interface. w3c/device-posture#71.
-
Rename word "mode" in the posture definition to "type". w3c/device-posture#68.
-
-
1 pull request reopened.
-
Rename word "mode" in the posture definition to "type". w3c/device-posture#68, by @darktears.
-
-
5 pull requests received 13 new comments.
-
Adding posture definition and clarification w3c/device-posture#69 (4 comments by @anssiko, @darktears, @kenchris, @xfq)
-
Rename word "mode" in the posture definition to "type". w3c/device-posture#68 (4 comments by @anssiko, @darktears)
-
Move the entry point of the API to the window.navigator interface. w3c/device-posture#71 (3 comments by @beaufortfrancois, @darktears)
-
Switch to w3c/spec-prod to automate publication to /TR w3c/device-posture#72 (1 comment by @anssiko)
-
w3c/geolocation
-
2 issues opened.
-
Broken fragments w3c/geolocation#71, by @xfq.
-
Broken link w3c/geolocation#70, by @xfq.
-
-
3 issues reopened.
-
Change text for description of GeolocationPositionError.message attribute w3c/geolocation#50, by @aphillips.
-
Require user activation to use API w3c/geolocation#48, by @pes10k.
-
How to specify desired accuracy / resolution of data? w3c/geolocation#49, by @marcoscaceres.
-
-
8 issues received 38 new comments.
-
Change text for description of GeolocationPositionError.message attribute w3c/geolocation#50 (9 comments by @aphillips, @marcoscaceres)
-
Require user activation to use API w3c/geolocation#48 (9 comments by @johannhof, @marcoscaceres, @martinthomson, @pes10k, @reillyeon)
-
How to specify desired accuracy / resolution of data? w3c/geolocation#49 (3 comments by @marcoscaceres)
-
Support geolocation (especially geofencing) in the "background" w3c/geolocation#214 (2 comments by @clshortfuse, @jakearchibald)
-
-
1 pull request opened.
-
Editorial: reword .message i18n note w3c/geolocation#72, by @marcoscaceres.
-
w3c/compute-pressure
-
1 pull request opened.
-
Initial spec draft w3c/compute-pressure#4, by @kenchris.
-
w3c/das-charter
-
2 issues opened.
-
Compute Pressure API -> System Pressure w3c/das-charter#111, by @oyiptong.
-
Idle Detection API w3c/das-charter#110, by @xfq.
-
-
3 issues received 7 new comments.
w3c/contact-picker
-
2 issues opened.
-
Add some security considerations for sites using this API w3c/contact-picker#38, by @jyasskin.
-
Migrate into a working group w3c/contact-picker#37, by @xfq.
-
-
2 issues received 3 new comments.
-
Add some security considerations for sites using this API w3c/contact-picker#38 (2 comments by @jyasskin, @rayankans)
-
-
2 pull requests opened.
-
Build/validate/publish spec using GitHub actions w3c/contact-picker#36, by @rayankans.
-
Editorial: Align with Web IDL specification w3c/contact-picker#35, by @autokagami.
-
-
1 pull request merged.
-
Editorial: Align with Web IDL specification w3c/contact-picker#35.
-
-
1 pull request closed.
-
Build/validate/publish spec using GitHub actions w3c/contact-picker#36.
-
w3c/ambient-light
-
1 issue received 2 new comments.
-
Request for Ambient Light Sensor web developer feedback w3c/ambient-light#64 (2 comments by @anssiko, @willmorgan)
-
w3c/deviceorientation
-
1 pull request received 4 new comments.
-
Drop duplicate PermissionState definition w3c/deviceorientation#88 (4 comments by @anssiko, @foolip, @reillyeon, @saschanaz)
-
w3c/screen-wake-lock
-
1 issue closed.
-
Auto-releasing wake lock depending on the user presence w3c/screen-wake-lock#300.
-
-
2 issues received 3 new comments.
-
Auto-releasing wake lock depending on the user presence w3c/screen-wake-lock#300 (1 comment by @anssiko)
-
1 pull request merged.
-
Editorial: Update auto-releasing wake lock examples w3c/screen-wake-lock#310.
-
w3c/das-wg
-
1 issue received 4 new comments.
-
1 pull request opened.
-
Link to Past Events in W3C Calendar w3c/das-wg#42, by @anssiko.
-
-
1 pull request merged.
-
Link to Past Events in W3C Calendar w3c/das-wg#42.
-
w3c/system-wake-lock
-
1 issue opened.
-
Use case: Simulations, rendering and creative coding w3c/system-wake-lock#7, by @spite.
-
-
1 issue received 1 new comment.
w3c/proximity
-
1 issue received 6 new comments.
-
Behavior of `distance` attribute when sensor cannot provide distance measurements? w3c/proximity#44 (6 comments by @domenic, @kenchris, @larsgk, @marcoscaceres, @reillyeon)
-
TR publications
-
1 document published.
-
Device Posture API published as a Working Draft. History of Device Posture API
-
Participants
-
3 participants joined.
-
Michael[tm] Smith (sideshowbarker) (W3C) joined.
-
Marcos Caceres (W3C) joined.
-
Frank Werner (Software AG) joined.
-
-
1 participant left.
-
Marcos Caceres (W3C) left.
-
-
1 organization joined.
-
Software AG joined.
-
GitHub
w3c/compute-pressure
-
3 issues opened.
-
ComputePressureObserver ownership w3c/compute-pressure#3, by @pwnall.
-
How do you handle multiple ComputePressureObserver? w3c/compute-pressure#2, by @npm1.
-
Explainer can go in README w3c/compute-pressure#1, by @npm1.
-
-
1 issue closed.
-
Explainer can go in README w3c/compute-pressure#1.
-
-
3 issues received 9 new comments.
-
How do you handle multiple ComputePressureObserver? w3c/compute-pressure#2 (4 comments by @npm1, @pwnall)
w3c/screen-wake-lock
-
1 issue closed.
-
"Release a wake lock": should we queue a task to fire the "release" event? w3c/screen-wake-lock#293.
-
-
2 issues received 4 new comments.
-
shouldn't this be part of the permissions API? w3c/screen-wake-lock#59 (3 comments by @reillyeon, @tamb, @tomayac)
-
Auto-releasing wake lock depending on the user presence w3c/screen-wake-lock#300 (1 comment by @marcoscaceres)
-
-
3 pull requests opened.
-
editorial: Remove the "state record" concept. w3c/screen-wake-lock#312, by @rakuco.
-
Editorial: remove uses of "responsible document" w3c/screen-wake-lock#311, by @domenic.
-
Editorial: Update auto-releasing wake lock examples w3c/screen-wake-lock#310, by @anssiko.
-
-
3 pull requests merged.
-
editorial: Remove the "state record" concept. w3c/screen-wake-lock#312.
-
Editorial: remove uses of "responsible document" w3c/screen-wake-lock#311.
-
editorial: Tidy up uses of "in parallel". w3c/screen-wake-lock#299.
-
-
1 pull request closed.
-
Clean up task queuing and document management w3c/screen-wake-lock#307.
-
-
6 pull requests received 31 new comments.
-
editorial: Tidy up uses of "in parallel". w3c/screen-wake-lock#299 (13 comments by @annevk, @domenic, @marcoscaceres, @rakuco, @reillyeon)
-
editorial: Remove the "state record" concept. w3c/screen-wake-lock#312 (6 comments by @marcoscaceres, @rakuco)
-
Editorial: remove uses of "responsible document" w3c/screen-wake-lock#311 (4 comments by @domenic, @rakuco)
-
Editorial: Update auto-releasing wake lock examples w3c/screen-wake-lock#310 (4 comments by @anssiko, @marcoscaceres)
-
Clean up task queuing and document management w3c/screen-wake-lock#307 (2 comments by @domenic, @rakuco)
-
editorial: Remove the "obtain a permission" algorithm. w3c/screen-wake-lock#298 (2 comments by @marcoscaceres, @rakuco)
-
w3c/geolocation
-
3 issues closed.
-
Add explainer to the spec repo w3c/geolocation#59.
-
Security review: General observations w3c/geolocation#57.
-
-
2 issues reopened.
-
Change text for description of GeolocationPositionError.message attribute w3c/geolocation#50, by @xfq.
-
Suggest permission lifetimes? w3c/geolocation#69, by @pes10k.
-
-
6 issues received 34 new comments.
-
Suggest permission lifetimes? w3c/geolocation#69 (13 comments by @johannhof, @jyasskin, @marcoscaceres, @martinthomson, @pes10k, @reillyeon, @samuelweiler)
-
Change text for description of GeolocationPositionError.message attribute w3c/geolocation#50 (6 comments by @marcoscaceres, @r12a, @xfq)
-
Section 3: Why only "SHOULD" for protection of privacy? w3c/geolocation#54 (5 comments by @marcoscaceres, @reillyeon)
-
Section 6: Non-normative but containing implementation requirements? w3c/geolocation#56 (4 comments by @magnus-git, @marcoscaceres, @samuelweiler)
-
-
7 pull requests opened.
-
Hook into Permissions API to get permission w3c/geolocation#68, by @marcoscaceres.
-
Only update position if document is showing w3c/geolocation#67, by @marcoscaceres.
-
Editorial: recipients are not a conformance class w3c/geolocation#66, by @marcoscaceres.
-
Editorial: call out examples more clearly + add explainer w3c/geolocation#65, by @marcoscaceres.
-
MUST have express permission to share location w3c/geolocation#64, by @marcoscaceres.
-
Editorial: remove RFC2119 words from Requirements w3c/geolocation#63, by @marcoscaceres.
-
Default errorCallback to null w3c/geolocation#62, by @marcoscaceres.
-
-
6 pull requests merged.
-
Hook into Permissions API to get permission w3c/geolocation#68.
-
Editorial: recipients are not a conformance class w3c/geolocation#66.
-
Editorial: call out examples more clearly + add explainer w3c/geolocation#65.
-
Editorial: remove RFC2119 words from Requirements w3c/geolocation#63.
-
Default errorCallback to null w3c/geolocation#62.
-
Editorial: fix up .message text w3c/geolocation#51.
-
-
2 pull requests closed.
-
Only update position if document is showing w3c/geolocation#67.
-
MUST have express permission to share location w3c/geolocation#64.
-
-
6 pull requests received 42 new comments.
-
Hook into Permissions API to get permission w3c/geolocation#68 (15 comments by @jyasskin, @marcoscaceres, @reillyeon)
-
Only update position if document is showing w3c/geolocation#67 (8 comments by @marcoscaceres, @reillyeon)
-
Editorial: recipients are not a conformance class w3c/geolocation#66 (6 comments by @jyasskin, @marcoscaceres)
-
Editorial: call out examples more clearly + add explainer w3c/geolocation#65 (5 comments by @marcoscaceres, @xfq)
-
MUST have express permission to share location w3c/geolocation#64 (3 comments by @marcoscaceres, @reillyeon)
-
w3c/accelerometer
-
1 pull request opened.
-
Add a Permissions Policy Integration section w3c/accelerometer#60, by @sideshowbarker.
-
-
1 pull request received 2 new comments.
-
Add a Permissions Policy Integration section w3c/accelerometer#60 (2 comments by @anssiko, @sideshowbarker)
-
w3c/das-wg
-
1 issue opened.
-
Devices and Sensors WG - 2021 Q2 virtual meeting w3c/das-wg#39, by @anssiko.
-
-
1 issue received 3 new comments.
-
Devices and Sensors WG - 2021 Q2 virtual meeting w3c/das-wg#39 (3 comments by @anssiko, @willmorgan)
-
-
3 pull requests opened.
-
Device Posture WD w3c/das-wg#41, by @anssiko.
-
Update meetings page w3c/das-wg#40, by @anssiko.
-
Screen Fold API -> Device Posture API w3c/das-wg#38, by @anssiko.
-
-
3 pull requests merged.
-
Device Posture WD w3c/das-wg#41.
-
Update meetings page w3c/das-wg#40.
-
Screen Fold API -> Device Posture API w3c/das-wg#38.
-
-
1 pull request received 1 new comment.
w3c/proximity
-
1 issue received 2 new comments.
-
Behavior of `distance` attribute when sensor cannot provide distance measurements? w3c/proximity#44 (2 comments by @andycarle, @anssiko)
-
w3c/device-posture
-
3 issues opened.
-
Rename "posture modes" to "posture types" w3c/device-posture#64, by @beaufortfrancois.
-
Adding fold position to identify orientation instead of identify device model w3c/device-posture#63, by @lauramorinigo.
-
Definition for "posture" missing w3c/device-posture#59, by @anssiko.
-
-
2 issues closed.
-
Suggestion: Rename to Device Posture API w3c/device-posture#54.
-
Drop ScreenFold.angle from the Screen Fold API? w3c/device-posture#56.
-
-
1 issue reopened.
-
Rename "posture modes" to "posture types" w3c/device-posture#64, by @anssiko.
-
-
3 issues received 6 new comments.
-
Rename "posture modes" to "posture types" w3c/device-posture#64 (3 comments by @anssiko, @beaufortfrancois)
-
Drop ScreenFold.angle from the Screen Fold API? w3c/device-posture#56 (2 comments by @anssiko, @darktears)
-
-
6 pull requests opened.
-
Update URL of the drawing of different postures w3c/device-posture#66, by @beaufortfrancois.
-
Fix name of enum values w3c/device-posture#65, by @beaufortfrancois.
-
Fixes after renaming. w3c/device-posture#62, by @darktears.
-
Rename the spec w3c/device-posture#61, by @xfq.
-
Rename spec device posture w3c/device-posture#60, by @darktears.
-
Remove fold angle value from the specification. w3c/device-posture#58, by @darktears.
-
-
6 pull requests merged.
-
Fix name of enum values w3c/device-posture#65.
-
Update URL of the drawing of different postures w3c/device-posture#66.
-
Fixes after renaming. w3c/device-posture#62.
-
Rename the spec w3c/device-posture#61.
-
Rename spec device posture w3c/device-posture#60.
-
Remove fold angle value from the specification. w3c/device-posture#58.
-
-
4 pull requests received 23 new comments.
-
Remove fold angle value from the specification. w3c/device-posture#58 (14 comments by @anssiko, @darktears, @kenchris)
-
w3c/das-charter
-
1 issue received 5 new comments.
w3c/html-media-capture
-
1 issue received 1 new comment.
w3c/battery
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Migrate from respec-w3c-common to respec-w3c w3c/battery#31, by @anssiko.
-
-
1 pull request merged.
-
Migrate from respec-w3c-common to respec-w3c w3c/battery#31.
-
-
1 pull request received 1 new comment.
w3c/sensors
-
1 issue opened.
-
IR sender/receiver w3c/sensors#409, by @jimmywarting.
-
-
1 issue received 2 new comments.
Participants
-
1 participant joined.
-
Laura Morinigo (Samsung Electronics Co., Ltd.) joined.
-
GitHub
w3c/screen-wake-lock
-
2 issues opened.
-
Auto-releasing wake lock depending on the user presence w3c/screen-wake-lock#300, by @anssiko.
-
"Release a wake lock": should we queue a task to fire the "release" event? w3c/screen-wake-lock#293, by @rakuco.
-
-
1 issue closed.
-
obtain permission seems wrong w3c/screen-wake-lock#187.
-
-
1 issue received 13 new comments.
-
"Release a wake lock": should we queue a task to fire the "release" event? w3c/screen-wake-lock#293 (13 comments by @annevk, @domenic, @rakuco)
-
-
15 pull requests opened.
-
editorial: Say "this's" instead of "this'". w3c/screen-wake-lock#309, by @rakuco.
-
editorial: Adjust nesting levels in the WakeLock.request() algorithm. w3c/screen-wake-lock#308, by @rakuco.
-
Clean up task queuing and document management w3c/screen-wake-lock#307, by @domenic.
-
editorial: Improve references to terms from the Page Visibility spec. w3c/screen-wake-lock#306, by @rakuco.
-
Cite extra specifications in xref, not the data-cite attribute. w3c/screen-wake-lock#305, by @rakuco.
-
editorial: Use Web IDL's "this" definition instead of "this object". w3c/screen-wake-lock#304, by @rakuco.
-
editorial: Simplify the "obtain permission" algorithm. w3c/screen-wake-lock#303, by @rakuco.
-
Move reference to wakelockpermissiondescriptor.https.html. w3c/screen-wake-lock#302, by @rakuco.
-
editorial: Define a task source for the tasks run by this specification. w3c/screen-wake-lock#301, by @rakuco.
-
editorial: Tidy up uses of "in parallel". w3c/screen-wake-lock#299, by @rakuco.
-
editorial: Remove the "obtain a permission" algorithm. w3c/screen-wake-lock#298, by @rakuco.
-
editorial: Formally define a permission revocation algorithm. w3c/screen-wake-lock#297, by @rakuco.
-
editorial: Adjust state record selection. w3c/screen-wake-lock#296, by @rakuco.
-
Adjust state record selection in "Managing Wake Locks". w3c/screen-wake-lock#295, by @rakuco.
-
Stop returning a boolean in the "acquire a wake lock" algorithm. w3c/screen-wake-lock#294, by @rakuco.
-
-
11 pull requests merged.
-
editorial: Adjust nesting levels in the WakeLock.request() algorithm. w3c/screen-wake-lock#308.
-
editorial: Say "this's" instead of "this'". w3c/screen-wake-lock#309.
-
editorial: Improve references to terms from the Page Visibility spec. w3c/screen-wake-lock#306.
-
Cite extra specifications in xref, not the data-cite attribute. w3c/screen-wake-lock#305.
-
editorial: Use Web IDL's "this" definition instead of "this object". w3c/screen-wake-lock#304.
-
editorial: Simplify the "obtain permission" algorithm. w3c/screen-wake-lock#303.
-
Move reference to wakelockpermissiondescriptor.https.html. w3c/screen-wake-lock#302.
-
editorial: Define a task source for the tasks run by this specification. w3c/screen-wake-lock#301.
-
editorial: Formally define a permission revocation algorithm. w3c/screen-wake-lock#297.
-
editorial: Adjust state record selection. w3c/screen-wake-lock#296.
-
Stop returning a boolean in the "acquire a wake lock" algorithm. w3c/screen-wake-lock#294.
-
-
1 pull request closed.
-
Adjust state record selection in "Managing Wake Locks". w3c/screen-wake-lock#295.
-
-
7 pull requests received 80 new comments.
-
editorial: Tidy up uses of "in parallel". w3c/screen-wake-lock#299 (45 comments by @annevk, @domenic, @kenchris, @marcoscaceres, @rakuco, @reillyeon)
-
editorial: Remove the "obtain a permission" algorithm. w3c/screen-wake-lock#298 (15 comments by @kenchris, @marcoscaceres, @rakuco, @reillyeon)
-
Clean up task queuing and document management w3c/screen-wake-lock#307 (8 comments by @domenic, @kenchris, @rakuco)
-
editorial: Improve references to terms from the Page Visibility spec. w3c/screen-wake-lock#306 (6 comments by @annevk, @marcoscaceres, @rakuco, @reillyeon)
-
editorial: Formally define a permission revocation algorithm. w3c/screen-wake-lock#297 (3 comments by @rakuco)
-
editorial: Simplify the "obtain permission" algorithm. w3c/screen-wake-lock#303 (2 comments by @kenchris, @rakuco)
-
Adjust state record selection in "Managing Wake Locks". w3c/screen-wake-lock#295 (1 comment by @rakuco)
-
w3c/battery
-
1 issue closed.
-
Update the reference to Feature Policy w3c/battery#26.
-
-
1 issue received 9 new comments.
-
Assess compatibility risk of using [SecureContext] w3c/battery#15 (9 comments by @anssiko, @domenic, @reillyeon)
-
-
1 pull request opened.
-
Improve getBattery() algorithm w3c/battery#30, by @domenic.
-
-
1 pull request merged.
-
Improve getBattery() algorithm w3c/battery#30.
-
-
1 pull request received 1 new comment.
w3c/device-posture
-
4 issues opened.
-
Clarify posture may be derived from sensors w3c/device-posture#57, by @anssiko.
-
Drop ScreenFold.angle from the Screen Fold API? w3c/device-posture#56, by @anssiko.
-
[admin] Enable auto-publish w3c/device-posture#55, by @anssiko.
-
Suggestion: Rename to Device Posture API w3c/device-posture#54, by @kenchris.
-
-
4 issues received 13 new comments.
-
Fold Angle fingerprinting concerns and its usefulness w3c/device-posture#45 (4 comments by @davidben, @kenchris, @lauramorinigo, @torgo)
-
Suggestion: Rename to Device Posture API w3c/device-posture#54 (4 comments by @anssiko, @kenchris, @lauramorinigo, @torgo)
-
Links from sec/priv sections back to normative mitigations? w3c/device-posture#53 (1 comment by @anssiko)
-
w3c/das-charter
-
1 issue received 2 new comments.
w3c/accelerometer
-
1 issue opened.
-
Explain how the implementation separates gravity from linear acceleration w3c/accelerometer#58, by @jyasskin.
-
-
1 issue closed.
-
Explain how the implementation separates gravity from linear acceleration w3c/accelerometer#58.
-
-
1 issue received 3 new comments.
-
Explain how the implementation separates gravity from linear acceleration w3c/accelerometer#58 (3 comments by @anssiko, @jyasskin, @reillyeon)
-
-
1 pull request opened.
-
Note gravity and linear accelerometer relationship w3c/accelerometer#59, by @anssiko.
-
-
1 pull request merged.
-
Note gravity and linear accelerometer relationship w3c/accelerometer#59.
-
-
1 pull request received 5 new comments.
-
Note gravity and linear accelerometer relationship w3c/accelerometer#59 (5 comments by @anssiko, @jyasskin)
-
w3c/contact-picker
-
1 issue received 1 new comment.
-
Matching ContactAddress fields to autofill attributes w3c/contact-picker#71 (1 comment by @marcoscaceres)
-
-
1 pull request opened.
-
Add default value {} for options argument w3c/contact-picker#34, by @foolip.
-
-
1 pull request merged.
-
Add default value {} for options argument w3c/contact-picker#34.
-
-
1 pull request received 2 new comments.
w3c/proximity
-
1 issue opened.
-
https://w3c.github.io/proximity/ not updated w3c/proximity#45, by @foolip.
-
-
1 issue closed.
-
https://w3c.github.io/proximity/ not updated w3c/proximity#45.
-
-
2 issues received 4 new comments.
-
Behavior of `distance` attribute when sensor cannot provide distance measurements? w3c/proximity#44 (2 comments by @andycarle, @anssiko)
-
1 pull request opened.
-
Regenerate HTML snapshot to trigger rebuild w3c/proximity#46, by @anssiko.
-
-
1 pull request merged.
-
Regenerate HTML snapshot to trigger rebuild w3c/proximity#46.
-
-
1 pull request received 1 new comment.
w3c/das-wg
-
1 pull request opened.
-
Add anchors to the roadmap w3c/das-wg#37, by @anssiko.
-
-
1 pull request merged.
-
Add anchors to the roadmap w3c/das-wg#37.
-
w3c/orientation-sensor
-
1 pull request opened.
-
fix: img width/height percentages to style w3c/orientation-sensor#69, by @nschonni.
-
-
1 pull request merged.
-
fix: img width/height percentages to style w3c/orientation-sensor#69.
-
-
1 pull request received 2 new comments.
-
fix: img width/height percentages to style w3c/orientation-sensor#69 (2 comments by @anssiko, @w3cbot)
-
w3c/motion-sensors
-
1 pull request opened.
-
fix: HTML validation issues with table w3c/motion-sensors#29, by @nschonni.
-
-
1 pull request received 4 new comments.
Participants
-
3 participants joined.
-
Rick Waldron (W3C Invited Experts) joined.
-
Dongwoo Joshua Im (Samsung Electronics Co., Ltd.) joined.
-
Francois Beaufort (Google LLC) joined.
-
-
3 participants left.
-
Eiji Yamamoto (Mitsubishi Electric Corporation) left.
-
Laura Morinigo (Samsung Electronics Co., Ltd.) left.
-
Rick Waldron (W3C Invited Experts) left.
-
-
2 organizations joined.
-
Samsung Electronics Co., Ltd. joined.
-
Fiserv joined.
-
GitHub
w3c/proximity
-
1 issue opened.
-
Behavior of `distance` attribute when sensor cannot provide distance measurements? w3c/proximity#44, by @andycarle.
-
-
1 issue received 2 new comments.
-
Behavior of `distance` attribute when sensor cannot provide distance measurements? w3c/proximity#44 (2 comments by @anssiko, @reillyeon)
-
w3c/sensors
-
1 pull request opened.
-
Update editor affiliation w3c/sensors#408, by @anssiko.
-
-
1 pull request merged.
-
Update editor affiliation w3c/sensors#408.
-
-
2 pull requests received 6 new comments.
w3c/contact-picker
-
1 issue received 3 new comments.
w3c/device-posture
-
1 issue opened.
-
Links from sec/priv sections back to normative mitigations? w3c/device-posture#53, by @samuelweiler.
-
-
3 issues received 13 new comments.
-
Fold Angle fingerprinting concerns and its usefulness w3c/device-posture#45 (11 comments by @beaufortfrancois, @darktears, @davidben, @diekus, @jyasskin, @kenchris, @LaszloGombos, @lauramorinigo)
-
-
1 pull request received 1 new comment.
w3c/vibration
-
1 issue received 1 new comment.
-
api.Navigator.vibrate - Throwing intervention error of vibration after user already interacted with UI. w3c/vibration#25 (1 comment by @rakuco)
-
-
2 pull requests opened.
-
Add IDL index to the end of the spec. w3c/vibration#27, by @rakuco.
-
respec: Migrate from the respec-w3c-common profile to respec-w3c. w3c/vibration#26, by @rakuco.
-
-
2 pull requests merged.
-
respec: Migrate from the respec-w3c-common profile to respec-w3c. w3c/vibration#26.
-
Add IDL index to the end of the spec. w3c/vibration#27.
-