Devices and Sensors Working Group - Activity in 2022
No matches.
Lifecycle
-
1 charter started.
-
Chartered until 20 February 2024. Participants had to rejoin under this charter.
-
TR publications
-
6 documents published.
-
Generic Sensor API published 4 times as a Candidate Recommendation Draft. History of Generic Sensor API
-
Compute Pressure Level 1 published as a First Public Working Draft. History of Compute Pressure Level 1
-
Contact Picker API published as a First Public Working Draft. History of Contact Picker API
-
Participants
-
1 Team contact appointed.
-
Atsushi Shimono became a Team contact.
-
-
1 Team contact stepped down.
-
Fuqiao Xue stepped down as a Team contact.
-
-
3 participants joined.
-
Varun Singh (Daily, Co) joined.
-
Bruce Nordman (Lawrence Berkeley National Laboratory) joined.
-
Atsushi Shimono (W3C) joined.
-
-
7 organizations joined.
-
Daily, Co joined.
-
Ecole Mohammadia d'Ingenieurs Rabat (EMI) joined.
-
Samsung Electronics Co., Ltd. joined.
-
Fraunhofer Gesellschaft joined.
-
Google LLC joined.
-
Intel Corporation joined.
-
Lawrence Berkeley National Laboratory joined.
-
-
7 organizations left.
-
Microsoft Corporation left.
-
Samsung Electronics Co., Ltd. left.
-
CoSMo Software Consulting Pte Ltd left.
-
Fraunhofer Gesellschaft left.
-
Google LLC left.
-
Ecole Mohammadia d'Ingenieurs Rabat (EMI) left.
-
Intel Corporation left.
-
GitHub
w3c/contact-picker
-
1 issue closed.
-
Prepare for W3C FPWD w3c/contact-picker#50.
-
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
Post FPWD updates w3c/contact-picker#53, by @himorin.
-
Update link to editor's draft as contact-api repo was renamed in cont… w3c/contact-picker#52, by @vivienlacourba.
-
-
1 pull request merged.
-
Update link to editor's draft as contact-api repo was renamed in cont… w3c/contact-picker#52.
-
-
1 pull request received 3 new comments.
w3c/compute-pressure
-
5 issues opened.
-
Enable automatic WD publication w3c/compute-pressure#169, by @anssiko.
-
Handle removing promises from pendingObservePromises list w3c/compute-pressure#168, by @kenchris.
-
Can the permission be dropped? w3c/compute-pressure#158, by @marcoscaceres.
-
Contradictory security statement w3c/compute-pressure#157, by @marcoscaceres.
-
-
1 issue closed.
-
Handle removing promises from pendingObservePromises list w3c/compute-pressure#168.
-
-
1 issue reopened.
-
4 issues received 19 new comments.
-
Determine the behavior when calling unobserve/disconnect method before the promise returned by observe method is settled w3c/compute-pressure#164 (15 comments by @arskama, @kenchris, @rakuco)
-
Handle removing promises from pendingObservePromises list w3c/compute-pressure#168 (2 comments by @kenchris, @rakuco)
-
-
15 pull requests opened.
-
setup streamlined publication w3c/compute-pressure#174, by @himorin.
-
README: Fix examples w3c/compute-pressure#173, by @arskama.
-
Fix nits w3c/compute-pressure#172, by @beaufortfrancois.
-
Update ReSpec config w3c/compute-pressure#171, by @anssiko.
-
Fix respec after FPWD w3c/compute-pressure#170, by @kenchris.
-
Handle abortion properly w3c/compute-pressure#167, by @kenchris.
-
Remove permissions integration w3c/compute-pressure#166, by @kenchris.
-
Fix observer/unobserve case w3c/compute-pressure#165, by @arskama.
-
HOWTO: Add examples w3c/compute-pressure#163, by @arskama.
-
Use 0 workers when stopped w3c/compute-pressure#162, by @kenchris.
-
Show worker count w3c/compute-pressure#161, by @kenchris.
-
Add HOWTO.md w3c/compute-pressure#160, by @arskama.
-
pubrules (html validation) error fixes w3c/compute-pressure#159, by @himorin.
-
Add simple demo w3c/compute-pressure#156, by @kenchris.
-
Address FPWD publication blockers w3c/compute-pressure#155, by @anssiko.
-
-
13 pull requests merged.
-
Fix nits w3c/compute-pressure#172.
-
README: Fix examples w3c/compute-pressure#173.
-
Update ReSpec config w3c/compute-pressure#171.
-
Fix respec after FPWD w3c/compute-pressure#170.
-
Handle abortion properly w3c/compute-pressure#167.
-
Remove permissions integration w3c/compute-pressure#166.
-
HOWTO: Add examples w3c/compute-pressure#163.
-
Add HOWTO.md w3c/compute-pressure#160.
-
Use 0 workers when stopped w3c/compute-pressure#162.
-
Show worker count w3c/compute-pressure#161.
-
pubrules (html validation) error fixes w3c/compute-pressure#159.
-
Address FPWD publication blockers w3c/compute-pressure#155.
-
Add simple demo w3c/compute-pressure#156.
-
-
10 pull requests received 30 new comments.
w3c/das-wg
-
1 issue opened.
-
Add Compute Pressure and Contact Picker API to Repository Manager w3c/das-wg#64, by @anssiko.
-
-
2 issues closed.
-
Devices and Sensors WG - TPAC 2022 agenda w3c/das-wg#56.
-
2 issues received 4 new comments.
-
Add Compute Pressure and Contact Picker API to Repository Manager w3c/das-wg#64 (3 comments by @anssiko, @vivienlacourba)
-
-
3 pull requests opened.
-
Fix link to TR/contact-picker w3c/das-wg#63, by @anssiko.
-
Advance Compute Pressure and Contact Picker API to Rec Track w3c/das-wg#62, by @anssiko.
-
Charter update w3c/das-wg#61, by @anssiko.
-
-
3 pull requests merged.
-
Fix link to TR/contact-picker w3c/das-wg#63.
-
Advance Compute Pressure and Contact Picker API to Rec Track w3c/das-wg#62.
-
Charter update w3c/das-wg#61.
-
-
3 pull requests received 9 new comments.
-
Advance Compute Pressure and Contact Picker API to Rec Track w3c/das-wg#62 (6 comments by @anssiko, @himorin, @vivienlacourba)
-
w3c/ambient-light
-
1 pull request opened.
-
Drop own powerful feature, require active local video source. w3c/ambient-light#83, by @rakuco.
-
-
1 pull request received 17 new comments.
-
Drop own powerful feature, require active local video source. w3c/ambient-light#83 (17 comments by @alvestrand, @anssiko, @lknik, @noamr, @rakuco, @reillyeon)
-
w3c/battery
-
1 issue received 2 new comments.
w3c/sensors
-
2 issues opened.
-
Fix all Bikeshed link errors w3c/sensors#444, by @rakuco.
-
Broken references in Generic Sensor API w3c/sensors#443, by @dontcallmedom-bot.
-
-
1 issue closed.
-
Broken references in Generic Sensor API w3c/sensors#443.
-
-
1 issue received 2 new comments.
-
6 pull requests opened.
-
Add changes and required hooks for ALS and Media Capture integration w3c/sensors#451, by @rakuco.
-
Request sensor access: remove "in parallel" block. w3c/sensors#449, by @rakuco.
-
Bikeshed: Refer to "webdriver2" instead of "webdriver-2" in the anchor section. w3c/sensors#448, by @rakuco.
-
Sensor.start(): Check for permission before attempting to connect to sensor. w3c/sensors#447, by @rakuco.
-
Fix broken references to WebDriver definitions. w3c/sensors#446, by @rakuco.
-
Use "exists" rather than "is present" in dictionary checks. w3c/sensors#445, by @rakuco.
-
-
5 pull requests merged.
-
Request sensor access: remove "in parallel" block. w3c/sensors#449.
-
Fix broken references to WebDriver definitions. w3c/sensors#446.
-
Use "exists" rather than "is present" in dictionary checks. w3c/sensors#445.
-
-
2 pull requests received 2 new comments.
-
Use "exists" rather than "is present" in dictionary checks. w3c/sensors#445 (1 comment by @kenchris)
w3c/device-posture
-
1 pull request received 1 new comment.
w3c/das-charter
-
1 issue reopened.
-
Joint deliverables with WebApps WG w3c/das-charter#123, by @anssiko.
-
-
1 issue received 4 new comments.
-
3 pull requests opened.
-
Joint deliverables w3c/das-charter#126, by @anssiko.
-
Archive update w3c/das-charter#125, by @anssiko.
-
Joint deliverables w3c/das-charter#124, by @anssiko.
-
-
2 pull requests merged.
-
Joint deliverables w3c/das-charter#124.
-
Archive update w3c/das-charter#125.
-
-
1 pull request closed.
-
Charter next w3c/das-charter#122.
-
-
2 pull requests received 2 new comments.
w3c/screen-wake-lock
-
3 issues received 6 new comments.
-
Require transient activation to request lock w3c/screen-wake-lock#350 (2 comments by @marcoscaceres, @reillyeon)
-
Distinguish exceptions on .request() w3c/screen-wake-lock#352 (2 comments by @marcoscaceres, @reillyeon)
-
TR publications
-
3 documents published.
-
Generic Sensor API published as a Candidate Recommendation Draft. History of Generic Sensor API
-
Screen Wake Lock API published twice as a Working Draft. History of Screen Wake Lock API
-
GitHub
w3c/das-charter
-
1 issue opened.
-
Joint deliverables with WebApps WG w3c/das-charter#123, by @anssiko.
-
-
1 issue received 1 new comment.
w3c/geolocation
-
1 issue opened.
-
get location API not working on android webview w3c/geolocation#132, by @kaominghsu.
-
-
1 issue closed.
-
get location API not working on android webview w3c/geolocation#132.
-
-
1 issue received 1 new comment.
w3c/screen-wake-lock
-
3 pull requests opened.
-
Permissions Policy: update default allowlist notation + small fixes. w3c/screen-wake-lock#356, by @rakuco.
-
Reference the "release the wake lock" definition. w3c/screen-wake-lock#355, by @rakuco.
-
Remove note from the "Handling document loss of full activity" section. w3c/screen-wake-lock#354, by @rakuco.
-
-
3 pull requests merged.
-
Permissions Policy: update default allowlist notation + small fixes. w3c/screen-wake-lock#356.
-
Reference the "release the wake lock" definition. w3c/screen-wake-lock#355.
-
Remove note from the "Handling document loss of full activity" section. w3c/screen-wake-lock#354.
-
w3c/sensors
-
1 pull request opened.
-
Use right notation for default allowlist value. w3c/sensors#442, by @rakuco.
-
-
1 pull request merged.
-
Use right notation for default allowlist value. w3c/sensors#442.
-
-
1 pull request received 5 new comments.
w3c/compute-pressure
-
4 issues opened.
-
permissions policy: Default allowlist syntax needs to be updated w3c/compute-pressure#154, by @rakuco.
-
observe()'s runs too many steps in parallel w3c/compute-pressure#152, by @rakuco.
-
Add hooks for Permission Revocation w3c/compute-pressure#147, by @kenchris.
-
observe() attempts to run asynchronous steps synchronously w3c/compute-pressure#146, by @rakuco.
-
-
3 issues closed.
-
observe()'s runs too many steps in parallel w3c/compute-pressure#152.
-
observe() attempts to run asynchronous steps synchronously w3c/compute-pressure#146.
-
"compute pressure" powerful feature should probably be exported w3c/compute-pressure#145.
-
-
2 issues received 13 new comments.
-
observe() attempts to run asynchronous steps synchronously w3c/compute-pressure#146 (11 comments by @kenchris, @rakuco, @wangw-1991)
-
observe()'s runs too many steps in parallel w3c/compute-pressure#152 (2 comments by @kenchris, @rakuco)
-
-
5 pull requests opened.
-
Avoid manipulating global objects in parallel w3c/compute-pressure#153, by @kenchris.
-
ReSpec: Fix errors w3c/compute-pressure#151, by @arskama.
-
Make observe() return a promise w3c/compute-pressure#149, by @kenchris.
-
Export powerful feature name and use in spec w3c/compute-pressure#148, by @kenchris.
-
-
4 pull requests merged.
-
Avoid manipulating global objects in parallel w3c/compute-pressure#153.
-
ReSpec: Fix errors w3c/compute-pressure#151.
-
Make observe() return a promise w3c/compute-pressure#149.
-
Export powerful feature name and use in spec w3c/compute-pressure#148.
-
-
1 pull request closed.
-
Add idl w3c/compute-pressure#150.
-
-
4 pull requests received 23 new comments.
-
Export powerful feature name and use in spec w3c/compute-pressure#148 (17 comments by @kenchris, @miketaylr, @rakuco)
-
w3c/ambient-light
-
1 issue received 2 new comments.
TR publications
-
2 documents published.
-
Accelerometer published as a Candidate Recommendation Draft. History of Accelerometer
-
Ambient Light Sensor published as a Working Draft. History of Ambient Light Sensor
-
GitHub
w3c/compute-pressure
-
6 issues opened.
-
"compute pressure" powerful feature should probably be exported w3c/compute-pressure#145, by @rakuco.
-
Check permissions policy in constructor() method instand of observe() method w3c/compute-pressure#144, by @wangw-1991.
-
"timestamps diff" and "sample rate" comparison should be ">=" and not ">" w3c/compute-pressure#142, by @arskama.
-
Wrong order in subtraction for "passes rate test" w3c/compute-pressure#140, by @arskama.
-
Comparison between seconds and milliseconds in "passes rate test"? w3c/compute-pressure#138, by @arskama.
-
Mismatch between PressureRecord.factors in IDL and definition in spec w3c/compute-pressure#137, by @rakuco.
-
-
8 issues closed.
-
Check permissions policy in constructor() method instand of observe() method w3c/compute-pressure#144.
-
"timestamps diff" and "sample rate" comparison should be ">=" and not ">" w3c/compute-pressure#142.
-
Wrong order in subtraction for "passes rate test" w3c/compute-pressure#140.
-
Comparison between seconds and milliseconds in "passes rate test"? w3c/compute-pressure#138.
-
Mismatch between PressureRecord.factors in IDL and definition in spec w3c/compute-pressure#137.
-
Should `factors` in Data Delivery be a list? w3c/compute-pressure#131.
-
`factors` handling in "Has change in data" in unclear w3c/compute-pressure#132.
-
PressureRecord should be an interface, not a dictionary w3c/compute-pressure#136.
-
-
1 issue reopened.
-
Wrong order in subtraction for "passes rate test" w3c/compute-pressure#140, by @arskama.
-
-
2 issues received 9 new comments.
-
Check permissions policy in constructor() method instand of observe() method w3c/compute-pressure#144 (8 comments by @kenchris, @rakuco, @wangw-1991)
-
-
3 pull requests opened.
-
Fixing comparison in passes rate test w3c/compute-pressure#143, by @arskama.
-
Fixes the order of the time subtraction in Passes rate test w3c/compute-pressure#141, by @arskama.
-
Fixing passes rate test w3c/compute-pressure#139, by @arskama.
-
-
4 pull requests merged.
-
Fixing comparison in passes rate test w3c/compute-pressure#143.
-
Fixes the order of the time subtraction in Passes rate test w3c/compute-pressure#141.
-
Fixing passes rate test w3c/compute-pressure#139.
-
Make PressureRecord an interface w3c/compute-pressure#135.
-
-
2 pull requests received 24 new comments.
w3c/accelerometer
-
1 issue opened.
-
Broken references in Accelerometer w3c/accelerometer#66, by @dontcallmedom-bot.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Define and export "accelerometer" permission w3c/accelerometer#67, by @miketaylr.
-
-
1 pull request merged.
-
Define and export "accelerometer" permission w3c/accelerometer#67.
-
-
1 pull request received 1 new comment.
w3c/ambient-light
-
1 pull request opened.
-
Define and export "ambient-light-sensor" permission w3c/ambient-light#82, by @miketaylr.
-
-
1 pull request merged.
-
Define and export "ambient-light-sensor" permission w3c/ambient-light#82.
-
-
1 pull request received 2 new comments.
-
Define and export "ambient-light-sensor" permission w3c/ambient-light#82 (2 comments by @anssiko, @miketaylr)
-
w3c/screen-wake-lock
-
1 issue closed.
-
An element attribute proposal for increasing screen brightness w3c/screen-wake-lock#348.
-
-
2 issues received 12 new comments.
-
Distinguish exceptions on .request() w3c/screen-wake-lock#352 (7 comments by @marcoscaceres, @reillyeon)
-
An element attribute proposal for increasing screen brightness w3c/screen-wake-lock#348 (5 comments by @beaufortfrancois, @marcoscaceres, @reillyeon, @willmorgan)
-
-
1 pull request closed.
-
Remove permission check w3c/screen-wake-lock#326.
-
-
2 pull requests received 3 new comments.
w3c/geolocation
-
1 issue opened.
-
Background Geolocation w3c/geolocation#131, by @UVLabs.
-
-
1 issue received 3 new comments.
w3c/battery
-
1 issue received 1 new comment.
w3c/sensors
-
1 issue opened.
-
Comparison between seconds and milliseconds in "Report latest reading updated"? w3c/sensors#441, by @rakuco.
-
-
1 issue received 1 new comment.
-
Comparison between seconds and milliseconds in "Report latest reading updated"? w3c/sensors#441 (1 comment by @reillyeon)
-
w3c/das-charter
-
1 pull request received 3 new comments.
TR publications
-
5 documents published.
-
Geolocation API published as a Recommendation. History of Geolocation API
-
Generic Sensor API published as a Candidate Recommendation Draft. History of Generic Sensor API
-
Screen Wake Lock API published twice as a Working Draft. History of Screen Wake Lock API
-
DeviceOrientation Event Specification published as a Working Draft. History of DeviceOrientation Event Specification
-
Past meetings
GitHub
w3c/compute-pressure
-
9 issues opened.
-
PressureRecord should be an interface, not a dictionary w3c/compute-pressure#136, by @rakuco.
-
Use dictionary notation when referring to PressureRecord members w3c/compute-pressure#133, by @rakuco.
-
`factors` handling in "Has change in data" in unclear w3c/compute-pressure#132, by @rakuco.
-
Should `factors` in Data Delivery be a list? w3c/compute-pressure#131, by @rakuco.
-
pressure factors should only be filled with serious and critical state. w3c/compute-pressure#127, by @arskama.
-
Use-case: provide a battery draining rate indication for application w3c/compute-pressure#126, by @taste1981.
-
update pressure option "samplerate" to "sampleRate" w3c/compute-pressure#125, by @arskama.
-
Handling of empty PressureObserverOptions is unclear w3c/compute-pressure#124, by @rakuco.
-
"Has change in data" uses `source` but does not take it as a parameter w3c/compute-pressure#122, by @rakuco.
-
-
5 issues closed.
-
Use dictionary notation when referring to PressureRecord members w3c/compute-pressure#133.
-
Handling of empty PressureObserverOptions is unclear w3c/compute-pressure#124.
-
pressure factors should only be filled with serious and critical state. w3c/compute-pressure#127.
-
update pressure option "samplerate" to "sampleRate" w3c/compute-pressure#125.
-
"Has change in data" uses `source` but does not take it as a parameter w3c/compute-pressure#122.
-
-
1 issue reopened.
-
Handling of empty PressureObserverOptions is unclear w3c/compute-pressure#124, by @kenchris.
-
-
7 issues received 32 new comments.
-
Handling of empty PressureObserverOptions is unclear w3c/compute-pressure#124 (18 comments by @arskama, @kenchris, @rakuco)
-
Should `factors` in Data Delivery be a list? w3c/compute-pressure#131 (6 comments by @kenchris, @rakuco)
-
`factors` handling in "Has change in data" in unclear w3c/compute-pressure#132 (3 comments by @kenchris, @rakuco)
-
Use dictionary notation when referring to PressureRecord members w3c/compute-pressure#133 (2 comments by @kenchris, @rakuco)
-
Use-case: provide a battery draining rate indication for application w3c/compute-pressure#126 (1 comment by @kenchris)
-
update pressure option "samplerate" to "sampleRate" w3c/compute-pressure#125 (1 comment by @beaufortfrancois)
-
"Has change in data" uses `source` but does not take it as a parameter w3c/compute-pressure#122 (1 comment by @kenchris)
-
-
6 pull requests opened.
-
Make PressureRecord an interface w3c/compute-pressure#135, by @kenchris.
-
Use dictionary notation when referring to PressureRecord members w3c/compute-pressure#134, by @kenchris.
-
Fixes #124, use default value and ensure value is > 1 w3c/compute-pressure#130, by @kenchris.
-
Fixes #124, ensure SampleRate is always valid w3c/compute-pressure#129, by @kenchris.
-
Fair state added to the states that should not return factors w3c/compute-pressure#128, by @arskama.
-
Fix #122: add missing source w3c/compute-pressure#123, by @kenchris.
-
-
5 pull requests merged.
-
Use dictionary notation when referring to PressureRecord members w3c/compute-pressure#134.
-
Fixes #124, use default value and ensure value is > 1 w3c/compute-pressure#130.
-
Fixes #124, ensure SampleRate is always valid w3c/compute-pressure#129.
-
Fair state added to the states that should not return factors w3c/compute-pressure#128.
-
Fix #122: add missing source w3c/compute-pressure#123.
-
-
1 pull request reopened.
-
Fixes #124, use default value and ensure value is > 1 w3c/compute-pressure#130, by @kenchris.
-
-
1 pull request received 1 new comment.
-
Fixes #124, use default value and ensure value is > 1 w3c/compute-pressure#130 (1 comment by @kenchris)
-
w3c/screen-wake-lock
-
5 issues opened.
-
Screen wake lock tests still using "feature policy" w3c/screen-wake-lock#353, by @marcoscaceres.
-
Distinguish exceptions on .request() w3c/screen-wake-lock#352, by @marcoscaceres.
-
Require transient activation to request lock w3c/screen-wake-lock#350, by @marcoscaceres.
-
An element attribute proposal for increasing screen brightness w3c/screen-wake-lock#348, by @beaufortfrancois.
-
"current settings object's associated Document" is not defined w3c/screen-wake-lock#346, by @Ms2ger.
-
-
2 issues closed.
-
Screen wake lock tests still using "feature policy" w3c/screen-wake-lock#353.
-
"current settings object's associated Document" is not defined w3c/screen-wake-lock#346.
-
-
6 issues received 21 new comments.
-
An element attribute proposal for increasing screen brightness w3c/screen-wake-lock#348 (9 comments by @beaufortfrancois, @reillyeon, @tomayac, @willmorgan)
-
Distinguish exceptions on .request() w3c/screen-wake-lock#352 (4 comments by @marcoscaceres, @reillyeon)
-
Require transient activation to request lock w3c/screen-wake-lock#350 (4 comments by @geoffreygaren, @marcoscaceres, @reillyeon)
-
"current settings object's associated Document" is not defined w3c/screen-wake-lock#346 (2 comments by @Ms2ger, @rakuco)
-
-
4 pull requests opened.
-
Require transient activation w3c/screen-wake-lock#351, by @marcoscaceres.
-
chore(PULL_REQUEST_TEMPLATE.md): include webkit w3c/screen-wake-lock#349, by @marcoscaceres.
-
editorial: Fetch an associated document from a global, not settings object w3c/screen-wake-lock#347, by @rakuco.
-
Added Xchart.com as interested partner w3c/screen-wake-lock#345, by @HenrikJoreteg.
-
-
3 pull requests merged.
-
chore(PULL_REQUEST_TEMPLATE.md): include webkit w3c/screen-wake-lock#349.
-
editorial: Fetch an associated document from a global, not settings object w3c/screen-wake-lock#347.
-
Added Xchart.com as interested partner w3c/screen-wake-lock#345.
-
-
4 pull requests received 34 new comments.
-
Remove permission check w3c/screen-wake-lock#326 (22 comments by @anssiko, @marcoscaceres, @rakuco, @reillyeon, @xfq)
-
Added Xchart.com as interested partner w3c/screen-wake-lock#345 (3 comments by @anssiko, @rakuco, @w3cbot)
-
editorial: Fetch an associated document from a global, not settings object w3c/screen-wake-lock#347 (1 comment by @rakuco)
-
w3c/das-charter
-
1 pull request opened.
-
Charter next w3c/das-charter#122, by @anssiko.
-
-
1 pull request received 5 new comments.
w3c/geolocation
-
3 issues opened.
-
Alignment with Geo-alignment/GeoPose? w3c/geolocation#130, by @rjksmith.
-
"request a position" uses "current setting object" from parallel steps. w3c/geolocation#126, by @Ms2ger.
-
"current settings object's relevant global object" is not defined w3c/geolocation#125, by @Ms2ger.
-
-
2 issues closed.
-
"request a position" uses "current setting object" from parallel steps. w3c/geolocation#126.
-
"current settings object's relevant global object" is not defined w3c/geolocation#125.
-
-
2 issues received 3 new comments.
-
"request a position" uses "current setting object" from parallel steps. w3c/geolocation#126 (1 comment by @marcoscaceres)
-
3 pull requests opened.
-
Editorial: fix 'in parallel' usage w3c/geolocation#129, by @marcoscaceres.
-
Editorial: use [=this=] to get global w3c/geolocation#128, by @marcoscaceres.
-
Editorial: retire Marcos as Editor w3c/geolocation#127, by @marcoscaceres.
-
-
3 pull requests merged.
-
Editorial: fix 'in parallel' usage w3c/geolocation#129.
-
Editorial: use [=this=] to get global w3c/geolocation#128.
-
Editorial: retire Marcos as Editor w3c/geolocation#127.
-
-
3 pull requests received 10 new comments.
w3c/battery
-
1 issue opened.
-
Use of "current global object" is confusing w3c/battery#54, by @Ms2ger.
-
-
1 issue received 3 new comments.
-
add more discussion of sec and priv analysis; split sections w3c/battery#28 (3 comments by @anssiko, @m32b64)
-
w3c/sensors
-
2 pull requests opened.
-
Initialize a sensor object: Improve notation and terms being referenced. w3c/sensors#440, by @rakuco.
-
initialize a sensor object: Explicitly require |options| to be a SensorOptions w3c/sensors#439, by @rakuco.
-
-
2 pull requests merged.
-
1 pull request received 6 new comments.
-
initialize a sensor object: Explicitly require |options| to be a SensorOptions w3c/sensors#439 (6 comments by @kenchris, @rakuco, @reillyeon)
-
w3c/contact-picker
-
2 issues opened.
-
Prepare for W3C FPWD w3c/contact-picker#50, by @marcoscaceres.
-
Call for Consensus: publish Contact Picker API as First Public Working Draft w3c/contact-picker#49, by @marcoscaceres.
-
-
2 issues closed.
-
Move repo to W3C w3c/contact-picker#46.
-
TPAC 2022 status report w3c/contact-picker#48.
-
-
3 issues received 5 new comments.
-
1 pull request opened.
-
Use FPWD template for spec w3c/contact-picker#51, by @rayankans.
-
-
1 pull request received 3 new comments.
w3c/deviceorientation
-
1 pull request opened.
-
Improve syntax highlighting w3c/deviceorientation#104, by @tomayac.
-
-
1 pull request merged.
-
Improve syntax highlighting w3c/deviceorientation#104.
-
-
1 pull request received 1 new comment.
w3c/device-posture
-
1 pull request received 7 new comments.
w3c/das-wg
-
1 issue received 2 new comments.
-
2 pull requests opened.
-
Geo to completed w3c/das-wg#60, by @anssiko.
-
Add Geolocation API REC w3c/das-wg#59, by @anssiko.
-
-
2 pull requests merged.
-
Geo to completed w3c/das-wg#60.
-
Add Geolocation API REC w3c/das-wg#59.
-
-
1 pull request received 1 new comment.
TR publications
-
4 documents published.
-
Generic Sensor API published as a Candidate Recommendation Draft. History of Generic Sensor API
-
Ambient Light Sensor published 3 times as a Working Draft. History of Ambient Light Sensor
-
GitHub
w3c/ambient-light
-
1 issue closed.
-
Consider making granularity of the data normative w3c/ambient-light#63.
-
-
2 issues received 4 new comments.
-
2 pull requests opened.
-
Fix use cases typo w3c/ambient-light#81, by @anssiko.
-
Update use cases section with iProov's. w3c/ambient-light#80, by @rakuco.
-
-
3 pull requests merged.
-
Fix use cases typo w3c/ambient-light#81.
-
editorial: Add reading quantization and threshold check algorithms. w3c/ambient-light#77.
-
Update use cases section with iProov's. w3c/ambient-light#80.
-
-
3 pull requests received 8 new comments.
-
editorial: Add reading quantization and threshold check algorithms. w3c/ambient-light#77 (5 comments by @anssiko, @sandandsnow)
-
w3c/compute-pressure
-
3 issues opened.
-
Observer first update w3c/compute-pressure#121, by @arskama.
-
Use-case: Memory stalls w3c/compute-pressure#120, by @kenchris.
-
Use-case: optimize for long battery life w3c/compute-pressure#119, by @kenchris.
-
-
2 issues closed.
-
Observer first update w3c/compute-pressure#121.
-
Integration with screen share and media capture w3c/compute-pressure#82.
-
-
2 issues received 3 new comments.
-
1 pull request opened.
-
Hook up new media capture hooks w3c/compute-pressure#118, by @kenchris.
-
-
1 pull request merged.
-
Hook up new media capture hooks w3c/compute-pressure#118.
-
w3c/das-charter
-
1 issue received 1 new comment.
w3c/sensors
-
1 pull request merged.
-
1 pull request received 3 new comments.
-
Declare quantization and threshold check algorithms for extension to the spec w3c/sensors#429 (3 comments by @anssiko, @rakuco, @sandandsnow)
-
w3c/battery
-
1 issue received 1 new comment.
w3c/screen-wake-lock
-
1 issue received 1 new comment.
-
Control screen brightness 🔆 review feedback w3c/screen-wake-lock#335 (1 comment by @beaufortfrancois)
-
-
1 pull request opened.
-
Update requestFullscreen section w3c/screen-wake-lock#344, by @beaufortfrancois.
-
-
1 pull request merged.
-
Update requestFullscreen section w3c/screen-wake-lock#344.
-
-
1 pull request received 1 new comment.
Participants
-
1 participant left.
-
Jorge Coronel (Google LLC) left.
-
GitHub
w3c/ambient-light
-
1 issue received 17 new comments.
-
Add camera permission requirement to spec? w3c/ambient-light#79 (17 comments by @lknik, @rakuco, @reillyeon, @willmorgan)
-
-
1 pull request received 3 new comments.
-
editorial: Add reading quantization and threshold check algorithms. w3c/ambient-light#77 (3 comments by @lknik, @rakuco)
-
w3c/contact-picker
-
1 issue opened.
-
TPAC 2022 status report w3c/contact-picker#48, by @LJWatson.
-
w3c/screen-wake-lock
-
1 issue received 5 new comments.
-
Control screen brightness 🔆 review feedback w3c/screen-wake-lock#335 (5 comments by @beaufortfrancois, @eligrey, @Genbuchan, @tomayac, @willmorgan)
-
-
1 pull request opened.
-
Updating WebKit review request link w3c/screen-wake-lock#343, by @beaufortfrancois.
-
-
1 pull request merged.
-
Updating WebKit review request link w3c/screen-wake-lock#343.
-
-
1 pull request received 2 new comments.
-
Updating WebKit review request link w3c/screen-wake-lock#343 (2 comments by @beaufortfrancois, @kenchris)
-
w3c/geolocation
-
2 issues received 2 new comments.
-
Problem when granted temporal acces to geolocation in Firefox w3c/geolocation#117 (1 comment by @Cyver0)
-
w3c/battery
-
1 issue received 1 new comment.
TR publications
-
3 documents published.
-
Generic Sensor API published twice as a Candidate Recommendation Draft. History of Generic Sensor API
-
DeviceOrientation Event Specification published as a Working Draft. History of DeviceOrientation Event Specification
-
GitHub
w3c/ambient-light
-
1 issue opened.
-
Add camera permission requirement to spec? w3c/ambient-light#79, by @rakuco.
-
-
1 issue received 6 new comments.
-
1 pull request received 9 new comments.
-
editorial: Add reading quantization and threshold check algorithms. w3c/ambient-light#77 (9 comments by @anssiko, @rakuco, @reillyeon)
-
w3c/screen-wake-lock
-
2 issues opened.
-
Clarify use cases in Screen Brightness API explainer w3c/screen-wake-lock#341, by @beaufortfrancois.
-
exclude brightness from API w3c/screen-wake-lock#340, by @tamb.
-
-
1 issue closed.
-
exclude brightness from API w3c/screen-wake-lock#340.
-
-
3 issues received 28 new comments.
-
Control screen brightness 🔆 review feedback w3c/screen-wake-lock#335 (19 comments by @anssiko, @beaufortfrancois, @eligrey, @jwheare, @marcoscaceres, @willmorgan)
-
Clarify use cases in Screen Brightness API explainer w3c/screen-wake-lock#341 (8 comments by @anssiko, @beaufortfrancois, @eligrey, @willmorgan)
-
-
1 pull request opened.
-
Add iproov.com to the list of interested partners w3c/screen-wake-lock#342, by @beaufortfrancois.
-
-
1 pull request merged.
-
Add iproov.com to the list of interested partners w3c/screen-wake-lock#342.
-
-
1 pull request received 2 new comments.
-
Add iproov.com to the list of interested partners w3c/screen-wake-lock#342 (2 comments by @beaufortfrancois, @willmorgan)
-
w3c/das-wg
-
1 issue opened.
-
Devices and Sensors WG - TPAC 2022 agenda w3c/das-wg#56, by @anssiko.
-
-
1 issue closed.
-
1 issue received 1 new comment.
-
Devices and Sensors WG - Screen Wake Lock Brightness follow-up w3c/das-wg#51 (1 comment by @anssiko)
-
w3c/geolocation
-
1 issue closed.
-
Transition to Proposed Recommendation w3c/geolocation#121.
-
-
1 issue received 1 new comment.
w3c/compute-pressure
-
6 issues opened.
-
Add "resource-contention" or "contention" as a contributing factor w3c/compute-pressure#117, by @kenchris.
-
Consider adding averages w3c/compute-pressure#116, by @kenchris.
-
Consider how or whether to handle runtime errors w3c/compute-pressure#115, by @kenchris.
-
Consider using AbortSignal in observe w3c/compute-pressure#114, by @kenchris.
-
What version Chrome can support the new PressureObserver interface? w3c/compute-pressure#113, by @Tang0770.
-
Change frequency to samplerate w3c/compute-pressure#112, by @kenchris.
-
-
2 issues closed.
-
Optionally get called back at a constant interval w3c/compute-pressure#109.
-
Change frequency to samplerate w3c/compute-pressure#112.
-
-
4 issues received 8 new comments.
-
What version Chrome can support the new PressureObserver interface? w3c/compute-pressure#113 (3 comments by @kenchris, @Tang0770)
-
Optionally get called back at a constant interval w3c/compute-pressure#109 (3 comments by @kenchris)
-
w3c/deviceorientation
-
1 issue closed.
-
Automatic publishing broken due to Specberus errors w3c/deviceorientation#100.
-
-
1 issue received 5 new comments.
-
Automatic publishing broken due to Specberus errors w3c/deviceorientation#100 (5 comments by @deniak, @reillyeon, @xfq)
-
-
2 pull requests opened.
-
s/user agent/user agents/ in compassneedscalibration description. w3c/deviceorientation#103, by @rakuco.
-
Align with DOM phrasing on firing events w3c/deviceorientation#102, by @dontcallmedom.
-
-
2 pull requests merged.
-
s/user agent/user agents/ in compassneedscalibration description. w3c/deviceorientation#103.
-
Align with DOM phrasing on firing events w3c/deviceorientation#102.
-
w3c/sensors
-
2 pull requests opened.
-
Revert "Temporarily disable links inside embedded SVG to allow CI to work." w3c/sensors#438, by @rakuco.
-
Temporarily disable links inside embedded SVG to allow CI to work. w3c/sensors#437, by @rakuco.
-
-
2 pull requests merged.
-
Temporarily disable links inside embedded SVG to allow CI to work. w3c/sensors#437.
-
2 pull requests received 6 new comments.
-
Declare quantization and threshold check algorithms for extension to the spec w3c/sensors#429 (5 comments by @anssiko, @rakuco)
-
Temporarily disable links inside embedded SVG to allow CI to work. w3c/sensors#437 (1 comment by @rakuco)
-
w3c/vibration
-
1 issue closed.
-
Require user activation for navigator.vibrate w3c/vibration#29.
-
-
1 pull request opened.
-
Clean up `respecConfig` a bit. w3c/vibration#31, by @rakuco.
-
-
2 pull requests merged.
-
Clean up `respecConfig` a bit. w3c/vibration#31.
-
Require sticky activation to perform vibrate w3c/vibration#30.
-
-
1 pull request received 3 new comments.
TR publications
-
2 documents published.
-
Generic Sensor API published as a Candidate Recommendation Draft. History of Generic Sensor API
-
Ambient Light Sensor published as a Working Draft. History of Ambient Light Sensor
-
Participants
-
1 participant left.
-
Sergio Garcia Murillo (CoSMo Software Consulting Pte Ltd) left.
-
GitHub
w3c/compute-pressure
-
7 issues opened.
-
Permission policy doesn't support workers yet w3c/compute-pressure#110, by @kenchris.
-
Optionally get called back at a constant interval w3c/compute-pressure#109, by @kenchris.
-
iFrame support w3c/compute-pressure#108, by @kenchris.
-
redefinition of "requested sampling frequency" to "requested reporting frequency" w3c/compute-pressure#106, by @arskama.
-
Unloading of workers (and hence Platform Collector) w3c/compute-pressure#104, by @kenchris.
-
Figure out whether to use agents or global object w3c/compute-pressure#103, by @kenchris.
-
Handle focus/active-non-active change w3c/compute-pressure#102, by @kenchris.
-
-
7 issues closed.
-
iFrame support w3c/compute-pressure#108.
-
redefinition of "requested sampling frequency" to "requested reporting frequency" w3c/compute-pressure#106.
-
Unloading of workers (and hence Platform Collector) w3c/compute-pressure#104.
-
Handle focus/active-non-active change w3c/compute-pressure#102.
-
Figure out whether to use agents or global object w3c/compute-pressure#103.
-
Handle unloading of the document w3c/compute-pressure#95.
-
Move Victor Costan to "former editor" w3c/compute-pressure#101.
-
-
4 issues received 13 new comments.
-
Unloading of workers (and hence Platform Collector) w3c/compute-pressure#104 (5 comments by @kenchris, @rakuco)
-
3 pull requests opened.
-
Make sure CP works in iframes w3c/compute-pressure#111, by @kenchris.
-
Rewording of requested frequency w3c/compute-pressure#107, by @arskama.
-
Multiple changes to fix activation and deactivation of platform collector w3c/compute-pressure#105, by @kenchris.
-
-
3 pull requests merged.
-
Make sure CP works in iframes w3c/compute-pressure#111.
-
Rewording of requested frequency w3c/compute-pressure#107.
-
Multiple changes to fix activation and deactivation of platform collector w3c/compute-pressure#105.
-
-
1 pull request received 1 new comment.
-
Multiple changes to fix activation and deactivation of platform collector w3c/compute-pressure#105 (1 comment by @arskama)
-
w3c/sensors
-
2 issues opened.
-
Currently focused area needs a top-level browsing context w3c/sensors#436, by @kenchris.
-
Current browsing context doesn't exist in workers w3c/sensors#435, by @kenchris.
-
-
1 pull request merged.
-
Reword the "Conditions to expose sensor readings" section w3c/sensors#434.
-
-
1 pull request received 2 new comments.
-
Reword the "Conditions to expose sensor readings" section w3c/sensors#434 (2 comments by @anssiko, @rakuco)
-
w3c/vibration
-
1 issue closed.
-
2 issues received 8 new comments.
-
Require user activation for navigator.vibrate w3c/vibration#29 (7 comments by @anssiko, @johannhof, @pshaughn, @rakuco)
-
api.Navigator.vibrate - Throwing intervention error of vibration after user already interacted with UI. w3c/vibration#25 (1 comment by @anssiko)
-
-
1 pull request opened.
-
Require sticky activation to perform vibrate w3c/vibration#30, by @anssiko.
-
-
1 pull request received 12 new comments.
-
Require sticky activation to perform vibrate w3c/vibration#30 (12 comments by @anssiko, @johannhof, @rakuco, @xfq)
-
w3c/screen-wake-lock
-
1 issue opened.
-
Propose high level control flow for JS-style brightness APIs w3c/screen-wake-lock#339, by @willmorgan.
-
-
1 issue closed.
-
Propose high level control flow for JS-style brightness APIs w3c/screen-wake-lock#339.
-
-
2 issues received 16 new comments.
-
Control screen brightness 🔆 review feedback w3c/screen-wake-lock#335 (15 comments by @anssiko, @beaufortfrancois, @marcoscaceres, @reillyeon, @willmorgan)
-
Propose high level control flow for JS-style brightness APIs w3c/screen-wake-lock#339 (1 comment by @willmorgan)
-
-
3 pull requests opened.
-
Add security considerations section w3c/screen-wake-lock#338, by @beaufortfrancois.
-
Add WebKit review request w3c/screen-wake-lock#337, by @anssiko.
-
Add Mozilla feedback, link to general review feedback w3c/screen-wake-lock#336, by @willmorgan.
-
-
3 pull requests merged.
-
Add security considerations section w3c/screen-wake-lock#338.
-
Add WebKit review request w3c/screen-wake-lock#337.
-
Add Mozilla feedback, link to general review feedback w3c/screen-wake-lock#336.
-
-
2 pull requests received 13 new comments.
-
Add security considerations section w3c/screen-wake-lock#338 (12 comments by @anssiko, @beaufortfrancois, @willmorgan)
-
Add Mozilla feedback, link to general review feedback w3c/screen-wake-lock#336 (1 comment by @w3cbot)
-
w3c/ambient-light
-
1 pull request opened.
-
editorial: Use Web IDL's definition conventions for getters. w3c/ambient-light#78, by @rakuco.
-
-
1 pull request merged.
-
editorial: Use Web IDL's definition conventions for getters. w3c/ambient-light#78.
-
w3c/das-wg
-
1 pull request opened.
-
Remove hard-coded milestones w3c/das-wg#55, by @anssiko.
-
-
1 pull request merged.
-
Remove hard-coded milestones w3c/das-wg#55.
-
TR publications
-
2 documents published.
-
Geolocation API published as a Proposed Recommendation. History of Geolocation API
-
Generic Sensor API published as a Candidate Recommendation Draft. History of Generic Sensor API
-
Participants
-
1 participant joined.
-
chengwei hsieh (Google LLC) joined.
-
-
2 participants left.
-
Marcos Caceres (W3C) left.
-
Joshue O'Connor (W3C) left.
-
GitHub
w3c/vibration
-
1 issue opened.
-
Require user activation for navigator.vibrate w3c/vibration#29, by @johannhof.
-
-
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 @johannhof)
-
w3c/screen-wake-lock
-
1 issue opened.
-
Control screen brightness 🔆 review feedback w3c/screen-wake-lock#335, by @anssiko.
-
-
1 issue received 1 new comment.
-
1 pull request received 2 new comments.
-
Add brightness-mode-explainer.md. w3c/screen-wake-lock#334 (2 comments by @anssiko, @beaufortfrancois)
-
w3c/compute-pressure
-
2 issues opened.
-
Move Victor Costan to "former editor" w3c/compute-pressure#101, by @inexorabletash.
-
"Queue a ComputePressureObserver Task" should use [=queue a global task=] w3c/compute-pressure#98, by @rakuco.
-
-
2 issues closed.
-
"Queue a ComputePressureObserver Task" should use [=queue a global task=] w3c/compute-pressure#98.
-
Integration with picture-in-picture w3c/compute-pressure#83.
-
-
3 issues received 3 new comments.
-
"Queue a ComputePressureObserver Task" should use [=queue a global task=] w3c/compute-pressure#98 (1 comment by @kenchris)
-
2 pull requests opened.
-
Queue a global task w3c/compute-pressure#100, by @kenchris.
-
Remove Compute as part of the objects w3c/compute-pressure#99, by @kenchris.
-
-
1 pull request merged.
-
Queue a global task w3c/compute-pressure#100.
-
-
1 pull request closed.
-
Remove Compute as part of the objects w3c/compute-pressure#99.
-
-
1 pull request received 1 new comment.
w3c/sensors
-
1 issue closed.
-
Replace usage of "responsible document" w3c/sensors#432.
-
-
1 pull request opened.
-
Reword the "Conditions to expose sensor readings" section w3c/sensors#434, by @rakuco.
-
-
1 pull request merged.
-
Stop referring to the "responsible document" concept. w3c/sensors#433.
-
-
2 pull requests received 5 new comments.
-
Stop referring to the "responsible document" concept. w3c/sensors#433 (4 comments by @anssiko, @miketaylr, @rakuco)
-
w3c/das-wg
-
1 pull request opened.
-
Add Geolocation API PR w3c/das-wg#54, by @anssiko.
-
-
1 pull request merged.
-
Add Geolocation API PR w3c/das-wg#54.
-
TR publications
-
5 documents published.
-
Generic Sensor API published as a Candidate Recommendation Draft. History of Generic Sensor API
-
Geolocation API published 3 times as a Candidate Recommendation Draft. History of Geolocation API
-
Geolocation Sensor published as a Working Draft. History of Geolocation Sensor
-
GitHub
w3c/html-media-capture
-
1 issue received 3 new comments.
w3c/sensors
-
1 issue opened.
-
Replace usage of "responsible document" w3c/sensors#432, by @miketaylr.
-
-
1 pull request opened.
-
Stop referring to the "responsible document" concept. w3c/sensors#433, by @rakuco.
-
-
1 pull request merged.
-
Improve SensorErrorEvent description. w3c/sensors#430.
-
-
2 pull requests received 5 new comments.
-
Stop referring to the "responsible document" concept. w3c/sensors#433 (3 comments by @miketaylr, @rakuco)
-
w3c/compute-pressure
-
14 issues opened.
-
Modernize spec text w3c/compute-pressure#96, by @inexorabletash.
-
Handle unloading of the document w3c/compute-pressure#95, by @kenchris.
-
Clarify better what supported means with regard to the ComputePressureSource enum w3c/compute-pressure#91, by @arskama.
-
Reconsider when to skip events w3c/compute-pressure#89, by @kenchris.
-
Don't pass in options in the callback w3c/compute-pressure#88, by @kenchris.
-
Consider time instead of timestamp w3c/compute-pressure#87, by @kenchris.
-
on unobserve(source), remove from records list only records assiociated with source w3c/compute-pressure#85, by @arskama.
-
Integration with picture-in-picture w3c/compute-pressure#83, by @kenchris.
-
Integration with screen share and media capture w3c/compute-pressure#82, by @kenchris.
-
Security and privacy review tracker w3c/compute-pressure#79, by @anssiko.
-
Add timestamp to the ComputePressureRecord w3c/compute-pressure#73, by @kenchris.
-
Handle dropped entries w3c/compute-pressure#72, by @kenchris.
-
Append ComputePressureRecord to QueuedRecords only when pressure state changes. w3c/compute-pressure#71, by @wangw-1991.
-
The ComputePressureRecord should contain source w3c/compute-pressure#70, by @kenchris.
-
-
16 issues closed.
-
Modernize spec text w3c/compute-pressure#96.
-
Clarify better what supported means with regard to the ComputePressureSource enum w3c/compute-pressure#91.
-
Consider time instead of timestamp w3c/compute-pressure#87.
-
Don't pass in options in the callback w3c/compute-pressure#88.
-
Reconsider when to skip events w3c/compute-pressure#89.
-
API design: Handling critical pressure w3c/compute-pressure#40.
-
Allow the API to work in the background (with limitations) w3c/compute-pressure#16.
-
on unobserve(source), remove from records list only records assiociated with source w3c/compute-pressure#85.
-
Add timestamp to the ComputePressureRecord w3c/compute-pressure#73.
-
Additional high-level information regarding the cause of the pressure w3c/compute-pressure#37.
-
Handle dropped entries w3c/compute-pressure#72.
-
Append ComputePressureRecord to QueuedRecords only when pressure state changes. w3c/compute-pressure#71.
-
The ComputePressureRecord should contain source w3c/compute-pressure#70.
-
Should "Notify Compute Pressure Observers" take target types into consideration? w3c/compute-pressure#66.
-
Unclear how a sample makes its way from a platform collector to a ComputePressureUpdateCallback w3c/compute-pressure#65.
-
Add example(s) showing usage of `observer` in callbacks w3c/compute-pressure#64.
-
-
1 issue reopened.
-
Unclear how a sample makes its way from a platform collector to a ComputePressureUpdateCallback w3c/compute-pressure#65, by @kenchris.
-
-
14 issues received 34 new comments.
-
Should "Notify Compute Pressure Observers" take target types into consideration? w3c/compute-pressure#66 (11 comments by @kenchris, @rakuco)
-
Integration with picture-in-picture w3c/compute-pressure#83 (3 comments by @beaufortfrancois, @kenchris)
-
Unclear how a sample makes its way from a platform collector to a ComputePressureUpdateCallback w3c/compute-pressure#65 (3 comments by @kenchris, @rakuco)
-
Clarify better what supported means with regard to the ComputePressureSource enum w3c/compute-pressure#91 (1 comment by @kenchris)
-
Allow the API to work in the background (with limitations) w3c/compute-pressure#16 (1 comment by @kenchris)
-
-
16 pull requests opened.
-
Use modern prose, closes #96 w3c/compute-pressure#97, by @kenchris.
-
Clarify what supporting a source type means w3c/compute-pressure#94, by @kenchris.
-
s/timestamp/time/ attribute w3c/compute-pressure#93, by @kenchris.
-
fix #91: fix error type w3c/compute-pressure#92, by @arskama.
-
change type of supportedSources to ComputePressureSource w3c/compute-pressure#90, by @arskama.
-
fix unobserve() algorithm w3c/compute-pressure#86, by @arskama.
-
Allow the user to request a sampling frequency w3c/compute-pressure#84, by @kenchris.
-
Add a timestamp to the record w3c/compute-pressure#81, by @kenchris.
-
Only deliver readings to active and focused docs, or their children w3c/compute-pressure#80, by @kenchris.
-
Introduce factors w3c/compute-pressure#78, by @kenchris.
-
fix typo from fix#71 w3c/compute-pressure#76, by @arskama.
-
s/Target/Source and expose source as part of the record w3c/compute-pressure#74, by @kenchris.
-
Fix additional comments from Raphael w3c/compute-pressure#69, by @kenchris.
-
Add callback observer example w3c/compute-pressure#68, by @kenchris.
-
-
15 pull requests merged.
-
Use modern prose, closes #96 w3c/compute-pressure#97.
-
Clarify what supporting a source type means w3c/compute-pressure#94.
-
s/timestamp/time/ attribute w3c/compute-pressure#93.
-
change type of supportedSources to ComputePressureSource w3c/compute-pressure#90.
-
fix unobserve() algorithm w3c/compute-pressure#86.
-
Allow the user to request a sampling frequency w3c/compute-pressure#84.
-
Add a timestamp to the record w3c/compute-pressure#81.
-
Only deliver readings to active and focused docs, or their children w3c/compute-pressure#80.
-
Introduce factors w3c/compute-pressure#78.
-
Fix #72 w3c/compute-pressure#77.
-
fix typo from fix#71 w3c/compute-pressure#76.
-
Fix #71 w3c/compute-pressure#75.
-
s/Target/Source and expose source as part of the record w3c/compute-pressure#74.
-
Fix additional comments from Raphael w3c/compute-pressure#69.
-
Add callback observer example w3c/compute-pressure#68.
-
-
1 pull request closed.
-
fix #91: fix error type w3c/compute-pressure#92.
-
-
6 pull requests received 13 new comments.
-
Only deliver readings to active and focused docs, or their children w3c/compute-pressure#80 (1 comment by @kenchris)
w3c/screen-wake-lock
-
1 pull request received 5 new comments.
-
Add brightness-mode-explainer.md. w3c/screen-wake-lock#334 (5 comments by @beaufortfrancois, @rakuco)
-
w3c/device-posture
-
1 issue opened.
-
Replace usage of "responsible document" w3c/device-posture#101, by @miketaylr.
-
-
2 pull requests opened.
-
Editorial: use associated Document in place of responsible document w3c/device-posture#102, by @miketaylr.
-
Remove Folded Over from Device Posture w3c/device-posture#100, by @supo2co.
-
-
1 pull request received 1 new comment.
w3c/geolocation
-
1 issue received 11 new comments.
-
Transition to Proposed Recommendation w3c/geolocation#121 (11 comments by @anssiko, @marcoscaceres, @reillyeon, @xfq)
-
-
1 pull request opened.
-
Editorial: use associated Document in place of responsible document w3c/geolocation#124, by @miketaylr.
-
-
1 pull request merged.
-
Editorial: use associated Document in place of responsible document w3c/geolocation#124.
-
w3c/battery
-
1 pull request received 4 new comments.
-
Add [SecureContext] to BatteryManager and the Navigator partial interface. w3c/battery#51 (4 comments by @anssiko, @lknik, @sandandsnow)
-
w3c/das-charter
-
1 pull request merged.
-
Fix Compute Pressure API URLs w3c/das-charter#121.
-
-
1 pull request received 1 new comment.
TR publications
-
5 documents published.
-
Geolocation API published as a Candidate Recommendation Snapshot. History of Geolocation API
-
Geolocation API published as a Candidate Recommendation Draft. History of Geolocation API
-
Geolocation API published as a Working Draft. History of Geolocation API
-
Battery Status API published twice as a Working Draft. History of Battery Status API
-
GitHub
w3c/compute-pressure
-
14 issues opened.
-
Should "Notify Compute Pressure Observers" take target types into consideration? w3c/compute-pressure#66, by @rakuco.
-
Unclear how a sample makes its way from a platform collector to a ComputePressureUpdateCallback w3c/compute-pressure#65, by @rakuco.
-
Add example(s) showing usage of `observer` in callbacks w3c/compute-pressure#64, by @rakuco.
-
Add missing examples for requestPermission() w3c/compute-pressure#61, by @beaufortfrancois.
-
Nit w3c/compute-pressure#60, by @beaufortfrancois.
-
Throw NotAllowedError when permission is prompt w3c/compute-pressure#59, by @beaufortfrancois.
-
Spec: add the proper hooks and explanation on how to map from hardware states to high level states w3c/compute-pressure#46, by @kenchris.
-
Make an example with takeRecords() w3c/compute-pressure#45, by @arskama.
-
How to handle user permission w3c/compute-pressure#44, by @kenchris.
-
Spec: add examples for disconnect and unobserve w3c/compute-pressure#43, by @kenchris.
-
Spec: Add examples for takeRecords() w3c/compute-pressure#42, by @kenchris.
-
API design: Handling critical pressure w3c/compute-pressure#40, by @kenchris.
-
Additional high-level information regarding the cause of the pressure w3c/compute-pressure#37, by @anssiko.
-
System shows 100% consumption but browser CPU Utilization doesnt w3c/compute-pressure#35, by @altanai.
-
-
19 issues closed.
-
Spec: add the proper hooks and explanation on how to map from hardware states to high level states w3c/compute-pressure#46.
-
Add missing examples for requestPermission() w3c/compute-pressure#61.
-
Nit w3c/compute-pressure#60.
-
Throw NotAllowedError when permission is prompt w3c/compute-pressure#59.
-
How to handle user permission w3c/compute-pressure#44.
-
Make points in section "Minimizing information exposure" refer to relevant spec sections w3c/compute-pressure#19.
-
ComputePressureObserver ownership w3c/compute-pressure#3.
-
Support the API in DedicatedWorker w3c/compute-pressure#15.
-
High-level metrics to improve web developer ergonomics w3c/compute-pressure#24.
-
How do you handle multiple ComputePressureObserver? w3c/compute-pressure#2.
-
System shows 100% consumption but browser CPU Utilization doesnt w3c/compute-pressure#35.
-
Spec: Add examples for takeRecords() w3c/compute-pressure#42.
-
Spec: add examples for disconnect and unobserve w3c/compute-pressure#43.
-
Add algos for quantification AKA bucketing w3c/compute-pressure#20.
-
Support querying method w3c/compute-pressure#27.
-
Explain trimming the quantization scheme w3c/compute-pressure#7.
-
Quantization clarification - how are threshold values handled? w3c/compute-pressure#6.
-
Make an example with takeRecords() w3c/compute-pressure#45.
-
Don't call callback if values didn't change w3c/compute-pressure#17.
-
-
15 issues received 29 new comments.
-
High-level metrics to improve web developer ergonomics w3c/compute-pressure#24 (5 comments by @anssiko, @kenchris)
-
System shows 100% consumption but browser CPU Utilization doesnt w3c/compute-pressure#35 (3 comments by @arskama, @kenchris)
-
Throw NotAllowedError when permission is prompt w3c/compute-pressure#59 (2 comments by @beaufortfrancois, @kenchris)
-
Spec: add the proper hooks and explanation on how to map from hardware states to high level states w3c/compute-pressure#46 (1 comment by @kenchris)
-
Should "Notify Compute Pressure Observers" take target types into consideration? w3c/compute-pressure#66 (1 comment by @kenchris)
-
Quantization clarification - how are threshold values handled? w3c/compute-pressure#6 (1 comment by @kenchris)
-
-
24 pull requests opened.
-
Call the right algorithm w3c/compute-pressure#67, by @kenchris.
-
Add examples for permission w3c/compute-pressure#63, by @kenchris.
-
Fix #59 and #60 w3c/compute-pressure#62, by @kenchris.
-
Support permissions w3c/compute-pressure#58, by @kenchris.
-
Fix #19 and clean up frequency description w3c/compute-pressure#57, by @kenchris.
-
Fix life cycle by introducing registered observer lists w3c/compute-pressure#56, by @kenchris.
-
Support workers w3c/compute-pressure#55, by @kenchris.
-
Refer to self-assessment from privacy section w3c/compute-pressure#54, by @kenchris.
-
Improve examples and s/entry/record/ given it is called takeRecords() w3c/compute-pressure#53, by @kenchris.
-
Add GitHub links w3c/compute-pressure#52, by @kenchris.
-
Update Security and Privacy Self Assessment w3c/compute-pressure#51, by @kenchris.
-
Document takeRecords w3c/compute-pressure#50, by @kenchris.
-
adding examples for disconnect and unobserve. w3c/compute-pressure#49, by @arskama.
-
Fix grammar w3c/compute-pressure#48, by @kenchris.
-
Update pr-preview for respec w3c/compute-pressure#47, by @anssiko.
-
Update spec after move to higher level states w3c/compute-pressure#41, by @kenchris.
-
Update main explainer w3c/compute-pressure#39, by @anssiko.
-
Work on new explainer w3c/compute-pressure#38, by @kenchris.
-
Update design considerations, API flow w3c/compute-pressure#36, by @anssiko.
-
Add a pointer to the high-level states proposal w3c/compute-pressure#34, by @anssiko.
-
Update dialogue w3c/compute-pressure#33, by @anssiko.
-
Update Calculate, Buckets, (Other) Advantages sections w3c/compute-pressure#32, by @anssiko.
-
Update Measuring section w3c/compute-pressure#31, by @anssiko.
-
Update Throttling section w3c/compute-pressure#30, by @anssiko.
-
-
24 pull requests merged.
-
Call the right algorithm w3c/compute-pressure#67.
-
Add examples for permission w3c/compute-pressure#63.
-
Fix #59 and #60 w3c/compute-pressure#62.
-
Support permissions w3c/compute-pressure#58.
-
Fix #19 and clean up frequency description w3c/compute-pressure#57.
-
Fix life cycle by introducing registered observer lists w3c/compute-pressure#56.
-
Support workers w3c/compute-pressure#55.
-
Refer to self-assessment from privacy section w3c/compute-pressure#54.
-
Improve examples and s/entry/record/ given it is called takeRecords() w3c/compute-pressure#53.
-
Add GitHub links w3c/compute-pressure#52.
-
adding examples for disconnect and unobserve. w3c/compute-pressure#49.
-
Update Security and Privacy Self Assessment w3c/compute-pressure#51.
-
Document takeRecords w3c/compute-pressure#50.
-
Update pr-preview for respec w3c/compute-pressure#47.
-
Fix grammar w3c/compute-pressure#48.
-
Update spec after move to higher level states w3c/compute-pressure#41.
-
Update main explainer w3c/compute-pressure#39.
-
Work on new explainer w3c/compute-pressure#38.
-
Update design considerations, API flow w3c/compute-pressure#36.
-
Add a pointer to the high-level states proposal w3c/compute-pressure#34.
-
Update dialogue w3c/compute-pressure#33.
-
Update Calculate, Buckets, (Other) Advantages sections w3c/compute-pressure#32.
-
Update Measuring section w3c/compute-pressure#31.
-
Update Throttling section w3c/compute-pressure#30.
-
-
6 pull requests received 111 new comments.
-
Update spec after move to higher level states w3c/compute-pressure#41 (68 comments by @anssiko, @arskama, @beaufortfrancois, @kenchris)
-
adding examples for disconnect and unobserve. w3c/compute-pressure#49 (31 comments by @arskama, @beaufortfrancois, @kenchris)
-
Fix life cycle by introducing registered observer lists w3c/compute-pressure#56 (1 comment by @darktears)
-
w3c/ambient-light
-
1 pull request received 10 new comments.
-
editorial: Add reading quantization and threshold check algorithms. w3c/ambient-light#77 (10 comments by @anssiko, @lknik, @sandandsnow)
-
w3c/geolocation
-
3 issues opened.
-
Support floorLevel on GeolocationCoordinates? w3c/geolocation#122, by @marcoscaceres.
-
Transition to Proposed Recommendation w3c/geolocation#121, by @marcoscaceres.
-
Investigate test failures to exit CR w3c/geolocation#120, by @marcoscaceres.
-
-
1 issue closed.
-
Investigate test failures to exit CR w3c/geolocation#120.
-
-
3 issues received 14 new comments.
-
Investigate test failures to exit CR w3c/geolocation#120 (11 comments by @marcoscaceres, @rakuco, @reillyeon)
-
How to specify desired accuracy / resolution of data? w3c/geolocation#49 (2 comments by @marcoscaceres, @samuelweiler)
-
w3c/battery
-
1 issue opened.
-
Explore a high-level API w3c/battery#52, by @anssiko.
-
-
1 issue closed.
-
Assess compatibility risk of using [SecureContext] w3c/battery#15.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Make Raphael a co-editor w3c/battery#53, by @anssiko.
-
-
2 pull requests merged.
-
Make Raphael a co-editor w3c/battery#53.
-
-
1 pull request received 2 new comments.
-
Add [SecureContext] to BatteryManager and the Navigator partial interface. w3c/battery#51 (2 comments by @anssiko, @rakuco)
-
w3c/das-wg
-
1 issue closed.
-
Devices and Sensors WG - TPAC 2021 agenda w3c/das-wg#47.
-
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
Add Geolocation API CR w3c/das-wg#53, by @anssiko.
-
Refresh for the new year w3c/das-wg#52, by @anssiko.
-
-
2 pull requests merged.
-
Add Geolocation API CR w3c/das-wg#53.
-
Refresh for the new year w3c/das-wg#52.
-
w3c/das-charter
-
1 pull request received 2 new comments.
w3c/screen-wake-lock
-
1 pull request received 2 new comments.
-
Add brightness-mode-explainer.md. w3c/screen-wake-lock#334 (2 comments by @beaufortfrancois, @rakuco)
-
w3c/device-posture
-
1 issue received 3 new comments.
-
logos are preventing auto-publish w3c/device-posture#90 (3 comments by @anssiko, @diekus, @marcoscaceres)
-
TR publications
-
1 document published.
-
Geolocation API published as a Working Draft. History of Geolocation API
-
Participants
-
1 participant left.
-
Frank Werner (Software AG) left.
-
-
1 organization left.
-
Software AG left.
-
GitHub
w3c/geolocation
-
1 issue opened.
-
Problem when granted temporal acces to geolocation in Firefox w3c/geolocation#117, by @elC0mpa.
-
-
4 issues closed.
-
List of active times is gone w3c/geolocation#113.
-
"Queue a task" / "in parallel" usage appears wrong w3c/geolocation#114.
-
Section 6: Non-normative but containing implementation requirements? w3c/geolocation#56.
-
Problem when granted temporal acces to geolocation in Firefox w3c/geolocation#117.
-
-
3 issues received 6 new comments.
-
Problem when granted temporal acces to geolocation in Firefox w3c/geolocation#117 (3 comments by @elC0mpa, @reillyeon)
-
How to specify desired accuracy / resolution of data? w3c/geolocation#49 (2 comments by @marcoscaceres, @pes10k)
-
Section 6: Non-normative but containing implementation requirements? w3c/geolocation#56 (1 comment by @marcoscaceres)
-
-
4 pull requests opened.
-
Editorial: acknowledge Reilly Grant as co-editor w3c/geolocation#119, by @marcoscaceres.
-
fix "Queue a task" / "in parallel" usage w3c/geolocation#118, by @marcoscaceres.
-
Editorial: fix "Queue a task" / "in parallel" usage w3c/geolocation#116, by @marcoscaceres.
-
Editorial: split Privacy and Security considerations w3c/geolocation#115, by @marcoscaceres.
-
-
3 pull requests merged.
-
Editorial: acknowledge Reilly Grant as co-editor w3c/geolocation#119.
-
fix "Queue a task" / "in parallel" usage w3c/geolocation#118.
-
Editorial: split Privacy and Security considerations w3c/geolocation#115.
-
-
1 pull request closed.
-
Editorial: fix "Queue a task" / "in parallel" usage w3c/geolocation#116.
-
-
2 pull requests received 16 new comments.
-
fix "Queue a task" / "in parallel" usage w3c/geolocation#118 (11 comments by @marcoscaceres, @reillyeon)
-
Editorial: fix "Queue a task" / "in parallel" usage w3c/geolocation#116 (5 comments by @marcoscaceres, @reillyeon)
-
w3c/device-posture
-
1 issue opened.
-
CSS Spanning outdated w3c/device-posture#99, by @lauramorinigo.
-
-
2 issues closed.
-
Naming of this spec w3c/device-posture#93.
-
Fold Angle fingerprinting concerns and its usefulness w3c/device-posture#45.
-
-
1 issue reopened.
-
Do developers want to identify when a device is being used with a pen / drawing posture? w3c/device-posture#96, by @lauramorinigo.
-
-
4 issues received 11 new comments.
-
Do developers want to identify when a device is being used with a pen / drawing posture? w3c/device-posture#96 (5 comments by @darktears, @voxpelli)
-
Adding fold position to identify orientation instead of identify device model w3c/device-posture#63 (3 comments by @darktears, @lauramorinigo)
-
w3c/battery
-
1 issue received 4 new comments.
-
1 pull request opened.
-
Add [SecureContext] to BatteryManager and the Navigator partial interface. w3c/battery#51, by @rakuco.
-
-
1 pull request received 1 new comment.
-
Add [SecureContext] to BatteryManager and the Navigator partial interface. w3c/battery#51 (1 comment by @anssiko)
-
w3c/compute-pressure
-
9 issues opened.
-
Support querying method w3c/compute-pressure#27, by @kenchris.
-
High-level metrics to improve web developer ergonomics w3c/compute-pressure#24, by @anssiko.
-
Follow the *Observer pattern more closely w3c/compute-pressure#21, by @kenchris.
-
Add algos for quantification AKA bucketing w3c/compute-pressure#20, by @kenchris.
-
Make points in section "Minimizing information exposure" refer to relevant spec sections w3c/compute-pressure#19, by @kenchris.
-
Don't call callback if values didn't change w3c/compute-pressure#17, by @kenchris.
-
Allow the API to work in the background (with limitations) w3c/compute-pressure#16, by @kenchris.
-
Support the API in DedicatedWorker w3c/compute-pressure#15, by @kenchris.
-
Zoom needs this API for the Zoom PWA & Web Client w3c/compute-pressure#14, by @fideltian.
-
-
1 issue closed.
-
Follow the *Observer pattern more closely w3c/compute-pressure#21.
-
-
6 issues received 17 new comments.
-
High-level metrics to improve web developer ergonomics w3c/compute-pressure#24 (7 comments by @anssiko, @fideltian, @kenchris)
-
Don't call callback if values didn't change w3c/compute-pressure#17 (2 comments by @arskama, @kenchris)
-
Allow the API to work in the background (with limitations) w3c/compute-pressure#16 (2 comments by @fideltian, @kenchris)
-
Zoom needs this API for the Zoom PWA & Web Client w3c/compute-pressure#14 (2 comments by @fideltian, @kenchris)
-
-
8 pull requests opened.
-
Adding supportedTargetTypes attribute w3c/compute-pressure#29, by @arskama.
-
Add explainer introduction w3c/compute-pressure#28, by @anssiko.
-
update example with new API w3c/compute-pressure#26, by @arskama.
-
Follow observer pattern more closely w3c/compute-pressure#25, by @kenchris.
-
small aesthetic changes in "note on feature detection" section w3c/compute-pressure#23, by @arskama.
-
note on feature detection. w3c/compute-pressure#22, by @arskama.
-
Add in Concepts: sampling frequency and reporting frequency w3c/compute-pressure#18, by @arskama.
-
Add CPU utilization aggregation and normalization. w3c/compute-pressure#13, by @arskama.
-
-
8 pull requests merged.
-
Adding supportedTargetTypes attribute w3c/compute-pressure#29.
-
Add explainer introduction w3c/compute-pressure#28.
-
update example with new API w3c/compute-pressure#26.
-
Follow observer pattern more closely w3c/compute-pressure#25.
-
small aesthetic changes in "note on feature detection" section w3c/compute-pressure#23.
-
note on feature detection. w3c/compute-pressure#22.
-
Add in Concepts: sampling frequency and reporting frequency w3c/compute-pressure#18.
-
Add CPU utilization aggregation and normalization. w3c/compute-pressure#13.
-
-
2 pull requests received 10 new comments.
-
Add in Concepts: sampling frequency and reporting frequency w3c/compute-pressure#18 (5 comments by @kenchris)
w3c/deviceorientation
-
1 issue closed.
-
Set up automatic Bikeshed compilation w3c/deviceorientation#67.
-
-
1 issue received 1 new comment.
w3c/screen-wake-lock
-
1 issue received 4 new comments.
-
Need maximum screen brightness mode w3c/screen-wake-lock#129 (4 comments by @anssiko, @svgeesus, @willmorgan)
-
-
1 pull request merged.
-
Add brightness-mode-explainer.md. w3c/screen-wake-lock#334.
-
-
1 pull request received 84 new comments.
-
Add brightness-mode-explainer.md. w3c/screen-wake-lock#334 (84 comments by @anssiko, @beaufortfrancois, @kenchris, @marcoscaceres, @rakuco, @reillyeon, @tomayac, @willmorgan)
-
w3c/sensors
-
1 issue received 1 new comment.