Devices and Sensors Working Group - Activity in 2024
No matches.
TR publications
-
1 document published.
-
Compute Pressure Level 1 published as a Working Draft. History of Compute Pressure Level 1
-
Participants
-
1 participant left.
-
Raphael Kubo da Costa (Intel Corporation) left.
-
GitHub
w3c/geolocation
-
2 issues opened.
-
Republish as a REC -> CR w3c/geolocation#180, by @marcoscaceres.
-
`AbortSignal` integration w3c/geolocation#179, by @jimmywarting.
-
-
2 issues received 4 new comments.
-
1 pull request opened.
-
Editorial: remove markers and ins/dels w3c/geolocation#181, by @marcoscaceres.
-
-
1 pull request received 2 new comments.
w3c/compute-pressure
-
1 issue received 2 new comments.
-
1 pull request opened.
-
[CRS/202412] changes section from FPWD w3c/compute-pressure#306, by @himorin.
-
-
1 pull request merged.
-
[CRS/202412] changes section from FPWD w3c/compute-pressure#306.
-
-
1 pull request received 3 new comments.
w3c/deviceorientation
-
1 pull request received 1 new comment.
TR publications
-
9 documents published.
-
Vibration API published as a Candidate Recommendation Snapshot. History of Vibration API
-
Device Posture API published as a Candidate Recommendation Snapshot. History of Device Posture API
-
Device Orientation and Motion published as a Candidate Recommendation Snapshot. History of Device Orientation and Motion
-
Vibration API published as a Candidate Recommendation Draft. History of Vibration API
-
Compute Pressure Level 1 published twice as a Working Draft. History of Compute Pressure Level 1
-
Device Posture API published 3 times as a Working Draft. History of Device Posture API
-
Participants
-
1 participant joined.
-
Natasha Gaitonde (Microsoft Corporation) joined.
-
-
1 participant left.
-
Dzung Tran (Intel Corporation) left.
-
GitHub
w3c/vibration
-
1 issue opened.
-
The user must be able to disable use of the Vibration API w3c/vibration#50, by @matatk.
-
-
2 issues closed.
-
Wide review tracker w3c/vibration#39.
-
Accessibility Checklist w3c/vibration#37.
-
-
4 issues received 8 new comments.
-
Structuring the security considerations section w3c/vibration#49 (4 comments by @anssiko, @simoneonofri)
-
The user must be able to disable use of the Vibration API w3c/vibration#50 (2 comments by @anssiko, @matatk)
-
-
2 pull requests opened.
-
Enable auto-publication of CRD to /TR w3c/vibration#52, by @anssiko.
-
Update specification name to Vibration API w3c/vibration#51, by @anssiko.
-
-
2 pull requests merged.
-
Update specification name to Vibration API w3c/vibration#51.
-
Enable auto-publication of CRD to /TR w3c/vibration#52.
-
-
2 pull requests received 6 new comments.
w3c/compute-pressure
-
1 issue opened.
-
single value enum and API pattern w3c/compute-pressure#304, by @dontcallmedom.
-
-
4 issues closed.
-
single value enum and API pattern w3c/compute-pressure#304.
-
Permission policy needs to be checked when owner set changes w3c/compute-pressure#243.
-
"Rate-limiting change notifications" section is confusing w3c/compute-pressure#291.
-
Adding a "estimatedOwnContribution" attribute to PressureRecord w3c/compute-pressure#297.
-
-
3 issues received 5 new comments.
-
single value enum and API pattern w3c/compute-pressure#304 (2 comments by @dontcallmedom, @kenchris)
-
Does compute pressure reflect OS-level speed limit changes due to throttling? w3c/compute-pressure#228 (1 comment by @arskama)
-
-
7 pull requests opened.
-
Add automation support for ownContributionEstimate w3c/compute-pressure#305, by @kenchris.
-
Turn issue into note, as workers have their own policy container w3c/compute-pressure#303, by @kenchris.
-
Remove the limiting of rate as it is replace by obfuscation w3c/compute-pressure#302, by @kenchris.
-
Fix idl bug w3c/compute-pressure#301, by @kenchris.
-
Move at-risk to experimental w3c/compute-pressure#300, by @kenchris.
-
Make ownContributionEstimate experimental w3c/compute-pressure#299, by @kenchris.
-
Add support for ownContributionEstimate w3c/compute-pressure#298, by @kenchris.
-
-
6 pull requests merged.
-
Turn issue into note, as workers have their own policy container w3c/compute-pressure#303.
-
Remove the limiting of rate as it is replace by obfuscation w3c/compute-pressure#302.
-
Fix idl bug w3c/compute-pressure#301.
-
Move at-risk to experimental w3c/compute-pressure#300.
-
Make ownContributionEstimate experimental w3c/compute-pressure#299.
-
Add support for ownContributionEstimate w3c/compute-pressure#298.
-
-
1 pull request closed.
-
Add source "cpu-same-origin" w3c/compute-pressure#289.
-
-
5 pull requests received 11 new comments.
-
Add support for ownContributionEstimate w3c/compute-pressure#298 (3 comments by @arskama, @darktears, @kenchris)
-
Turn issue into note, as workers have their own policy container w3c/compute-pressure#303 (1 comment by @arskama)
-
Remove the limiting of rate as it is replace by obfuscation w3c/compute-pressure#302 (1 comment by @arskama)
w3c/das-wg
-
2 pull requests opened.
-
Update roadmap publication milestones w3c/das-wg#73, by @anssiko.
-
Add group-webapps-das-chairs list to comms page w3c/das-wg#72, by @anssiko.
-
-
2 pull requests merged.
-
Update roadmap publication milestones w3c/das-wg#73.
-
Add group-webapps-das-chairs list to comms page w3c/das-wg#72.
-
-
1 pull request received 1 new comment.
w3c/device-posture
-
1 issue opened.
-
Put text about fingerprinting in the Security Considerations Section to point one in privacy considerations w3c/device-posture#167, by @himorin.
-
-
2 issues closed.
-
Wide review tracker w3c/device-posture#146.
-
2 issues received 3 new comments.
-
Put text about fingerprinting in the Security Considerations Section to point one in privacy considerations w3c/device-posture#167 (1 comment by @simoneonofri)
-
4 pull requests opened.
-
switch echidna from WD to CRD w3c/device-posture#170, by @himorin.
-
Address review comments from the CR request. w3c/device-posture#168, by @darktears.
-
fix for Tidy document #57 w3c/device-posture#165, by @himorin.
-
[CRS/202411] added list of changes w3c/device-posture#164, by @himorin.
-
-
3 pull requests merged.
-
Address review comments from the CR request. w3c/device-posture#168.
-
fix for Tidy document #57 w3c/device-posture#165.
-
[CRS/202411] added list of changes w3c/device-posture#164.
-
-
3 pull requests received 9 new comments.
-
[CRS/202411] added list of changes w3c/device-posture#164 (5 comments by @anssiko, @darktears, @himorin)
-
Address review comments from the CR request. w3c/device-posture#168 (3 comments by @darktears, @himorin, @simoneonofri)
-
w3c/deviceorientation
-
1 pull request opened.
-
switch echidna from WD to CRD w3c/deviceorientation#189, by @himorin.
-
TR publications
-
10 documents published.
-
Accelerometer published twice as a Candidate Recommendation Draft. History of Accelerometer
-
Gyroscope published as a Candidate Recommendation Draft. History of Gyroscope
-
Device Posture API published twice as a Working Draft. History of Device Posture API
-
Battery Status API published as a Working Draft. History of Battery Status API
-
Compute Pressure Level 1 published as a Working Draft. History of Compute Pressure Level 1
-
Device Orientation and Motion published as a Working Draft. History of Device Orientation and Motion
-
Screen Wake Lock API published as a Working Draft. History of Screen Wake Lock API
-
Magnetometer published as a Working Draft. History of Magnetometer
-
GitHub
w3c/vibration
-
3 issues opened.
-
Structuring the security considerations section w3c/vibration#49, by @simoneonofri.
-
Rate limits to prevent excessive use w3c/vibration#48, by @anssiko.
-
Create an explainer w3c/vibration#45, by @anssiko.
-
-
2 issues closed.
-
Updating privacy considerations - recovery of two identifiers w3c/vibration#12.
-
Internationalization Checklist w3c/vibration#38.
-
-
4 issues received 9 new comments.
-
Updating privacy considerations - recovery of two identifiers w3c/vibration#12 (2 comments by @himorin, @lknik)
-
2 pull requests opened.
-
Update Security and privacy considerations w3c/vibration#47, by @anssiko.
-
Define 'max length' and 'max duration' normatively w3c/vibration#46, by @anssiko.
-
-
3 pull requests merged.
-
Update Security and privacy considerations w3c/vibration#47.
-
Define 'max length' and 'max duration' normatively w3c/vibration#46.
-
Update spec metadata and add Changes section w3c/vibration#44.
-
-
2 pull requests received 5 new comments.
-
Define 'max length' and 'max duration' normatively w3c/vibration#46 (3 comments by @anssiko, @reillyeon)
-
w3c/device-posture
-
1 issue closed.
-
Should Device Posture API be exposed to iframes (JS or CSS) w3c/device-posture#111.
-
-
2 issues received 11 new comments.
-
Should Device Posture API be exposed to iframes (JS or CSS) w3c/device-posture#111 (9 comments by @anssiko, @darktears, @Psychpsyo, @tomayac)
-
-
2 pull requests opened.
-
Make the tables prettier by using the default style. w3c/device-posture#163, by @darktears.
-
Remove inline issue reference w3c/device-posture#162, by @anssiko.
-
-
2 pull requests merged.
-
Make the tables prettier by using the default style. w3c/device-posture#163.
-
Remove inline issue reference w3c/device-posture#162.
-
w3c/compute-pressure
-
1 issue opened.
-
Adding a "estimatedOwnContribution" attribute to PressureRecord w3c/compute-pressure#297, by @arskama.
-
-
1 pull request opened.
-
Retire as editor w3c/compute-pressure#296, by @rakuco.
-
-
1 pull request merged.
-
Retire as editor w3c/compute-pressure#296.
-
w3c/contact-picker
-
1 issue closed.
-
Matching ContactAddress fields to autofill attributes w3c/contact-picker#71.
-
-
2 issues received 3 new comments.
-
Matching ContactAddress fields to autofill attributes w3c/contact-picker#71 (2 comments by @jcayzac, @rsolomakhin)
-
w3c/screen-wake-lock
-
1 pull request opened.
-
Retire as editor w3c/screen-wake-lock#375, by @rakuco.
-
-
1 pull request merged.
-
Retire as editor w3c/screen-wake-lock#375.
-
-
1 pull request received 1 new comment.
w3c/deviceorientation
-
1 pull request opened.
-
Retire as editor w3c/deviceorientation#188, by @rakuco.
-
-
1 pull request merged.
-
Retire as editor w3c/deviceorientation#188.
-
w3c/battery
-
1 pull request opened.
-
Retire as editor w3c/battery#68, by @rakuco.
-
-
1 pull request merged.
-
Retire as editor w3c/battery#68.
-
w3c/das-wg
-
1 pull request opened.
-
Updated roadmap for styles w3c/das-wg#71, by @himorin.
-
-
1 pull request merged.
-
Updated roadmap for styles w3c/das-wg#71.
-
w3c/geolocation
-
1 issue received 3 new comments.
-
Support geolocation (especially geofencing) in the "background" w3c/geolocation#214 (3 comments by @anssiko, @Bessonov, @Lucho-git)
-
w3c/accelerometer
-
1 issue closed.
-
define normative privacy mitigation w3c/accelerometer#57.
-
-
2 pull requests opened.
-
Add Accelerometer reading quantization algorithm w3c/accelerometer#82, by @anssiko.
-
Fix "accelerometer" feature name references w3c/accelerometer#81, by @anssiko.
-
-
2 pull requests merged.
-
Add Accelerometer reading quantization algorithm w3c/accelerometer#82.
-
Update permissions integration reference w3c/accelerometer#80.
-
-
1 pull request closed.
-
Fix "accelerometer" feature name references w3c/accelerometer#81.
-
-
2 pull requests received 3 new comments.
-
Add Accelerometer reading quantization algorithm w3c/accelerometer#82 (2 comments by @anssiko, @reillyeon)
-
w3c/magnetometer
-
1 pull request opened.
-
Update permission name and feature name references w3c/magnetometer#75, by @anssiko.
-
-
1 pull request merged.
-
Update permission name and feature name references w3c/magnetometer#75.
-
w3c/gyroscope
-
1 pull request opened.
-
Update permission name and feature name references w3c/gyroscope#63, by @anssiko.
-
-
1 pull request merged.
-
Update permission name and feature name references w3c/gyroscope#63.
-
TR publications
-
5 documents published.
-
Geolocation published as a Recommendation. History of Geolocation
-
Compute Pressure Level 1 published twice as a Working Draft. History of Compute Pressure Level 1
-
Device Posture API published twice as a Working Draft. History of Device Posture API
-
Past meetings
Participants
-
1 participant joined.
-
Sharath Chandra Ramakrishnan (University of Illinois) joined.
-
-
1 participant left.
-
Juha Vainio (Intel Corporation) left.
-
-
1 organization joined.
-
University of Illinois joined.
-
GitHub
w3c/compute-pressure
-
3 issues opened.
-
Metabug: Raising Specification to CR maturity level. w3c/compute-pressure#295, by @arskama.
-
Tag "thermals" source as "at_risk" in specification w3c/compute-pressure#294, by @arskama.
-
"Rate-limiting change notifications" section is confusing w3c/compute-pressure#291, by @rakuco.
-
-
3 issues closed.
-
Tag "thermals" source as "at_risk" in specification w3c/compute-pressure#294.
-
"Current pressure state" definition and cardinality are confusing w3c/compute-pressure#281.
-
Use-case: provide a battery draining rate indication for application w3c/compute-pressure#126.
-
-
1 issue reopened.
-
Wide review tracker w3c/compute-pressure#177, by @anssiko.
-
-
5 issues received 14 new comments.
-
"Rate-limiting change notifications" section is confusing w3c/compute-pressure#291 (4 comments by @arskama, @kenchris, @rakuco)
-
Does compute pressure reflect OS-level speed limit changes due to throttling? w3c/compute-pressure#228 (3 comments by @arskama, @brycepj)
-
Tag "thermals" source as "at_risk" in specification w3c/compute-pressure#294 (1 comment by @arskama)
-
Use-case: provide a battery draining rate indication for application w3c/compute-pressure#126 (1 comment by @arskama)
-
2 pull requests opened.
-
Make thermal pressure source at-risk w3c/compute-pressure#293, by @kenchris.
-
Fix #281: Get rid of the global current pressure state w3c/compute-pressure#292, by @kenchris.
-
-
2 pull requests merged.
-
Make thermal pressure source at-risk w3c/compute-pressure#293.
-
Fix #281: Get rid of the global current pressure state w3c/compute-pressure#292.
-
-
2 pull requests received 4 new comments.
-
Fix #281: Get rid of the global current pressure state w3c/compute-pressure#292 (3 comments by @kenchris, @rakuco)
-
w3c/das-wg
-
1 issue received 2 new comments.
-
1 pull request opened.
-
use the new W3C style for the DAS website w3c/das-wg#70, by @deniak.
-
-
2 pull requests merged.
-
Remove api.w3.org API key that is no longer required w3c/das-wg#67.
-
use the new W3C style for the DAS website w3c/das-wg#70.
-
-
1 pull request received 1 new comment.
w3c/device-posture
-
2 issues closed.
-
Internationalization checklist w3c/device-posture#148.
-
Device posture and direction interaction w3c/device-posture#151.
-
-
3 issues received 3 new comments.
-
Should Device Posture API be exposed to iframes (JS or CSS) w3c/device-posture#111 (1 comment by @Psychpsyo)
-
3 pull requests opened.
-
Grammar: change "a hands-free" to "a hands-free experience" w3c/device-posture#161, by @Psychpsyo.
-
Add feedback from i18n W3C review. w3c/device-posture#160, by @darktears.
-
Update test suite and implementation report headers w3c/device-posture#159, by @anssiko.
-
-
3 pull requests merged.
-
Grammar: change "a hands-free" to "a hands-free experience" w3c/device-posture#161.
-
Add feedback from i18n W3C review. w3c/device-posture#160.
-
Update test suite and implementation report headers w3c/device-posture#159.
-
-
2 pull requests received 5 new comments.
-
Grammar: change "a hands-free" to "a hands-free experience" w3c/device-posture#161 (2 comments by @rakuco, @w3cbot)
w3c/accelerometer
-
1 issue closed.
-
device calibration of accelerometers may reveal precise hardware fingerprint w3c/accelerometer#54.
-
-
3 issues received 3 new comments.
-
device calibration of accelerometers may reveal precise hardware fingerprint w3c/accelerometer#54 (1 comment by @reillyeon)
-
Disable Accelerometer use while Vibration API is in use w3c/accelerometer#69 (1 comment by @reillyeon)
-
-
1 pull request opened.
-
Update permissions integration reference w3c/accelerometer#80, by @anssiko.
-
-
1 pull request received 1 new comment.
w3c/gyroscope
-
1 issue received 1 new comment.
w3c/sensors
-
2 issues received 4 new comments.
w3c/screen-wake-lock
-
3 issues received 6 new comments.
-
Require transient activation to request lock w3c/screen-wake-lock#350 (3 comments by @reillyeon, @smaug----)
-
Distinguish exceptions on .request() w3c/screen-wake-lock#352 (2 comments by @reillyeon, @smaug----)
-
w3c/geolocation
-
2 issues opened.
-
Why are you closing w3c/geolocation#177, by @ghost.
-
Why can't my device location show. w3c/geolocation#176, by @ghost.
-
-
2 issues closed.
-
Why are you closing w3c/geolocation#177.
-
Why can't my device location show. w3c/geolocation#176.
-
-
2 issues received 7 new comments.
-
Support geolocation (especially geofencing) in the "background" w3c/geolocation#214 (6 comments by @clshortfuse, @James-E-A, @marknelissen, @paulo-assoc, @scovillo)
-
-
1 pull request opened.
-
chore: fix purple box marker w3c/geolocation#175, by @anssiko.
-
-
1 pull request merged.
-
chore: fix purple box marker w3c/geolocation#175.
-
-
1 pull request received 1 new comment.
-
w3c/geolocation#178 (1 comment by @ghost)
-
w3c/vibration
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Update spec metadata and add Changes section w3c/vibration#44, by @anssiko.
-
-
1 pull request merged.
-
turn page-visibility-2 into WHATWG/HTML w3c/vibration#41.
-
-
2 pull requests received 6 new comments.
w3c/contact-picker
-
1 issue opened.
-
Missing tasks in parallel steps in Contact Picker API w3c/contact-picker#78, by @dontcallmedom-bot.
-
TR publications
-
3 documents published.
-
Geolocation published 3 times as a Recommendation. History of Geolocation
-
GitHub
w3c/vibration
-
3 issues received 3 new comments.
w3c/geolocation
-
1 issue opened.
-
Promisify `getCurrentPosition()` w3c/geolocation#174, by @lukewarlow.
-
-
1 issue closed.
-
2 issues received 7 new comments.
-
Promisify `getCurrentPosition()` w3c/geolocation#174 (5 comments by @lukewarlow, @mkruisselbrink, @reillyeon)
-
`GeolocationCoordinates.toJSON()` - Should the spec cover how to handle `NaN` headings? w3c/geolocation#171 (2 comments by @anssiko, @marcoscaceres)
-
-
2 pull requests opened.
-
Correction: Use null instead of NaN when stationary w3c/geolocation#173, by @reillyeon.
-
Editorial: Update use of WebIDL "invoke a callback function" w3c/geolocation#172, by @jeremyroman.
-
-
2 pull requests merged.
-
Correction: Use null instead of NaN when stationary w3c/geolocation#173.
-
Editorial: Update use of WebIDL "invoke a callback function" w3c/geolocation#172.
-
-
1 pull request received 2 new comments.
-
Editorial: Update use of WebIDL "invoke a callback function" w3c/geolocation#172 (2 comments by @jeremyroman)
-
w3c/device-posture
-
1 issue closed.
-
Comparison to other fingerprinting surface is incorrect w3c/device-posture#153.
-
-
1 issue received 1 new comment.
-
Comparison to other fingerprinting surface is incorrect w3c/device-posture#153 (1 comment by @pes10k)
-
TR publications
-
4 documents published.
-
Geolocation published as a Recommendation. History of Geolocation
-
Device Posture API published twice as a Working Draft. History of Device Posture API
-
Contact Picker API published as a Working Draft. History of Contact Picker API
-
GitHub
w3c/device-posture
-
3 issues opened.
-
Rate limiting does not seem related to privacy w3c/device-posture#154, by @pes10k.
-
Comparison to other fingerprinting surface is incorrect w3c/device-posture#153, by @pes10k.
-
Clarify that `null` is never exposed to the page w3c/device-posture#152, by @pes10k.
-
-
2 issues closed.
-
Rate limiting does not seem related to privacy w3c/device-posture#154.
-
Clarify that `null` is never exposed to the page w3c/device-posture#152.
-
-
4 issues received 4 new comments.
-
Comparison to other fingerprinting surface is incorrect w3c/device-posture#153 (1 comment by @darktears)
-
-
3 pull requests opened.
-
Fix typo. w3c/device-posture#158, by @darktears.
-
editorial: Reorganize internal slots into different sections w3c/device-posture#156, by @rakuco.
-
Remove the rate limiting section per PING review. w3c/device-posture#155, by @darktears.
-
-
3 pull requests merged.
-
Fix typo. w3c/device-posture#158.
-
Remove the rate limiting section per PING review. w3c/device-posture#155.
-
editorial: Reorganize internal slots into different sections w3c/device-posture#156.
-
-
3 pull requests received 5 new comments.
-
Remove the rate limiting section per PING review. w3c/device-posture#155 (3 comments by @darktears, @LaszloGombos, @rakuco)
-
editorial: Reorganize internal slots into different sections w3c/device-posture#156 (1 comment by @darktears)
-
w3c/compute-pressure
-
1 issue opened.
-
Usecase: 100% pressure, main thread blocked entirely. PressureObserver never fires an event w3c/compute-pressure#290, by @Meai.
-
w3c/vibration
-
2 issues opened.
-
Misc non-privacy concerns with the API w3c/vibration#43, by @pes10k.
-
Integration with permissions API w3c/vibration#42, by @pes10k.
-
-
1 pull request opened.
-
turn page-visibility-2 into WHATWG/HTML w3c/vibration#41, by @himorin.
-
-
1 pull request received 1 new comment.
w3c/geolocation
-
1 issue opened.
-
`GeolocationCoordinates.toJSON()` - Should the spec cover how to handle `NaN` headings? w3c/geolocation#171, by @ezzatron.
-
-
2 issues received 10 new comments.
-
`GeolocationCoordinates.toJSON()` - Should the spec cover how to handle `NaN` headings? w3c/geolocation#171 (8 comments by @ezzatron, @marcoscaceres, @reillyeon, @saschanaz)
-
Support geolocation (especially geofencing) in the "background" w3c/geolocation#214 (2 comments by @Lucho-git, @sedubois)
-
-
1 pull request opened.
-
Add test automation support via Web Driver w3c/geolocation#170, by @marcoscaceres.
-
-
1 pull request received 10 new comments.
-
Add test automation support via Web Driver w3c/geolocation#170 (10 comments by @marcoscaceres, @reillyeon)
-
w3c/contact-picker
-
1 pull request opened.
-
Add create a `ContactAddress` from user-provided input w3c/contact-picker#77, by @marcoscaceres.
-
-
1 pull request merged.
-
Add create a `ContactAddress` from user-provided input w3c/contact-picker#77.
-
-
1 pull request received 1 new comment.
-
Add create a `ContactAddress` from user-provided input w3c/contact-picker#77 (1 comment by @marcoscaceres)
-
w3c/deviceorientation
-
1 pull request opened.
-
Add document fully active checks w3c/deviceorientation#187, by @marcoscaceres.
-
-
1 pull request received 10 new comments.
-
Add document fully active checks w3c/deviceorientation#187 (10 comments by @marcoscaceres, @reillyeon)
-
TR publications
-
13 documents published.
-
Geolocation published 4 times as a Recommendation. History of Geolocation
-
Accelerometer published as a Candidate Recommendation Draft. History of Accelerometer
-
Contact Picker API published as a Working Draft. History of Contact Picker API
-
Compute Pressure Level 1 published 5 times as a Working Draft. History of Compute Pressure Level 1
-
Geolocation Sensor published as a Working Draft. History of Geolocation Sensor
-
Device Posture API published as a Working Draft. History of Device Posture API
-
GitHub
w3c/geolocation
-
3 issues opened.
-
How do I add new geotarget locations to Google Ads? w3c/geolocation#169, by @wagneraquino88.
-
Update implementation report w3c/geolocation#163, by @marcoscaceres.
-
Define the units of `accuracy` w3c/geolocation#160, by @reillyeon.
-
-
7 issues closed.
-
How do I add new geotarget locations to Google Ads? w3c/geolocation#169.
-
Update implementation report w3c/geolocation#163.
-
Position data isn't passed into 'new GeolocationPosition' w3c/geolocation#137.
-
repo name nit: it'd be nice if this were simply w3c/geolocation w3c/geolocation#154.
-
Define the units of `accuracy` w3c/geolocation#160.
-
/TR/ missing from latest published version for ED w3c/geolocation#155.
-
Non-secure context check vanished from the spec w3c/geolocation#156.
-
-
3 issues received 4 new comments.
-
repo name nit: it'd be nice if this were simply w3c/geolocation w3c/geolocation#154 (2 comments by @himorin, @marcoscaceres)
-
-
9 pull requests opened.
-
removed revisionTypes w3c/geolocation#168, by @himorin.
-
Added ipr to gh-action w3c/geolocation#167, by @himorin.
-
link fix for ipr w3c/geolocation#166, by @himorin.
-
chore: rewrite implementation report w3c/geolocation#165, by @marcoscaceres.
-
Editorial: rename spec to Geolocation w3c/geolocation#164, by @marcoscaceres.
-
Addition: Define units for accuracy w3c/geolocation#162, by @reillyeon.
-
Editorial: Minor corrections prior to republication w3c/geolocation#161, by @reillyeon.
-
minor text fix, for pubrules w3c/geolocation#159, by @himorin.
-
Disable /TR/ publication for errata.html w3c/geolocation#158, by @himorin.
-
-
11 pull requests merged.
-
link fix for ipr w3c/geolocation#166.
-
Added ipr to gh-action w3c/geolocation#167.
-
removed revisionTypes w3c/geolocation#168.
-
chore: rewrite implementation report w3c/geolocation#165.
-
Editorial: rename spec to Geolocation w3c/geolocation#164.
-
Addition: Define units for accuracy w3c/geolocation#162.
-
Editorial: Minor corrections prior to republication w3c/geolocation#161.
-
minor text fix, for pubrules w3c/geolocation#159.
-
Disable /TR/ publication for errata.html w3c/geolocation#158.
-
Correction: check for non-secure contexts w3c/geolocation#157.
-
-
6 pull requests received 28 new comments.
-
Correction: Update acquisition algorithm to define data types and handle cached positions w3c/geolocation#153 (18 comments by @jyasskin, @marcoscaceres, @reillyeon)
-
Disable /TR/ publication for errata.html w3c/geolocation#158 (5 comments by @himorin, @marcoscaceres, @sidvishnoi)
-
w3c/vibration
-
5 issues opened.
-
[DRAFT] TAG review request w3c/vibration#40, by @anssiko.
-
Wide review tracker w3c/vibration#39, by @anssiko.
-
Internationalization Checklist w3c/vibration#38, by @anssiko.
-
Accessibility Checklist w3c/vibration#37, by @anssiko.
-
Security and Privacy Self-review w3c/vibration#36, by @anssiko.
-
-
1 issue closed.
-
[DRAFT] TAG review request w3c/vibration#40.
-
-
7 issues received 54 new comments.
-
Update implementation report w3c/vibration#33 (36 comments by @anssiko, @egirard, @himorin, @marcoscaceres, @reillyeon, @saschanaz, @scheib, @siusin)
-
w3c/das-wg
-
1 issue opened.
-
Devices and Sensors WG - TPAC 2024 agenda w3c/das-wg#69, by @anssiko.
-
w3c/compute-pressure
-
6 issues opened.
-
automation: Consider adding WebDriver BiDi actions in addition to the WebDriver Classic endpoints w3c/compute-pressure#288, by @rakuco.
-
automation: Pressure types supported in WebDriver are the same as what PressureObserver.knownSources returns w3c/compute-pressure#286, by @rakuco.
-
automation: Decide whether shared workers should be supported w3c/compute-pressure#285, by @rakuco.
-
Add WebDriver support w3c/compute-pressure#282, by @rakuco.
-
"Current pressure state" definition and cardinality are confusing w3c/compute-pressure#281, by @rakuco.
-
Properly determine bfcache integration strategy w3c/compute-pressure#275, by @rakuco.
-
-
2 issues closed.
-
Add WebDriver support w3c/compute-pressure#282.
-
Is PressureRecord.time a timestamp or a time that is relative to timeOrigin? w3c/compute-pressure#257.
-
-
2 issues received 4 new comments.
-
Properly determine bfcache integration strategy w3c/compute-pressure#275 (3 comments by @kenchris, @rakuco)
-
-
9 pull requests opened.
-
Add source "cpu-same-origin" w3c/compute-pressure#289, by @arskama.
-
Add Raphael Kubo da Costa as editor w3c/compute-pressure#287, by @arskama.
-
Add an Automation section with WebDriver support to the spec w3c/compute-pressure#284, by @rakuco.
-
Make PressureObserver.observe() and data delivery algorithm less vague w3c/compute-pressure#283, by @rakuco.
-
data delivery: Set `timestamp` as an "unsafe shared current time" w3c/compute-pressure#280, by @rakuco.
-
data delivery: Use right time-related variable in passes rate test check w3c/compute-pressure#279, by @rakuco.
-
editorial: Use more precise algorithmic steps in unobserve() and disconnect() w3c/compute-pressure#278, by @rakuco.
-
editorial: fully active checks: Refer to specific registered observer list w3c/compute-pressure#277, by @rakuco.
-
Rework handling of fully active status w3c/compute-pressure#276, by @rakuco.
-
-
9 pull requests merged.
-
Add Raphael Kubo da Costa as editor w3c/compute-pressure#287.
-
Add an Automation section with WebDriver support to the spec w3c/compute-pressure#284.
-
Make PressureObserver.observe() and data delivery algorithm less vague w3c/compute-pressure#283.
-
data delivery: Set `timestamp` as an "unsafe shared current time" w3c/compute-pressure#280.
-
data delivery: Use right time-related variable in passes rate test check w3c/compute-pressure#279.
-
timestamp: Redefine timestamp in Data delivery w3c/compute-pressure#274.
-
editorial: Use more precise algorithmic steps in unobserve() and disconnect() w3c/compute-pressure#278.
-
editorial: fully active checks: Refer to specific registered observer list w3c/compute-pressure#277.
-
Rework handling of fully active status w3c/compute-pressure#276.
-
-
1 pull request closed.
-
Automation section and WebDriver support w3c/compute-pressure#265.
-
-
9 pull requests received 99 new comments.
-
Automation section and WebDriver support w3c/compute-pressure#265 (69 comments by @arskama, @kenchris, @rakuco)
-
timestamp: Redefine timestamp in Data delivery w3c/compute-pressure#274 (8 comments by @arskama, @rakuco)
-
Add an Automation section with WebDriver support to the spec w3c/compute-pressure#284 (6 comments by @OrKoN, @rakuco)
-
Add Raphael Kubo da Costa as editor w3c/compute-pressure#287 (5 comments by @anssiko, @himorin, @kenchris, @rakuco)
-
Make PressureObserver.observe() and data delivery algorithm less vague w3c/compute-pressure#283 (4 comments by @arskama, @rakuco)
-
data delivery: Use right time-related variable in passes rate test check w3c/compute-pressure#279 (2 comments by @arskama, @kenchris)
-
data delivery: Set `timestamp` as an "unsafe shared current time" w3c/compute-pressure#280 (2 comments by @arskama, @rakuco)
-
editorial: Use more precise algorithmic steps in unobserve() and disconnect() w3c/compute-pressure#278 (2 comments by @kenchris, @rakuco)
-
w3c/device-posture
-
1 issue opened.
-
Device posture and direction interaction w3c/device-posture#151, by @aphillips.
-
-
1 issue closed.
-
Accessibility checklist w3c/device-posture#147.
-
-
1 issue reopened.
-
Internationalization checklist w3c/device-posture#148, by @darktears.
-
-
3 issues received 10 new comments.
-
1 pull request opened.
-
Add two new comments from the accessibility review. w3c/device-posture#149, by @darktears.
-
-
1 pull request merged.
-
Add two new comments from the accessibility review. w3c/device-posture#149.
-
-
1 pull request received 1 new comment.
-
Add two new comments from the accessibility review. w3c/device-posture#149 (1 comment by @darktears)
-
w3c/deviceorientation
-
5 issues received 5 new comments.
-
Guidance needed: how to acquire compass headings in a future-compatible manner? w3c/deviceorientation#137 (1 comment by @reillyeon)
-
fire an orientation event need to use the dictionary w3c/deviceorientation#184 (1 comment by @reillyeon)
-
-
1 pull request closed.
-
Make DeviceMotionEventInit members nullable with null default w3c/deviceorientation#141.
-
-
1 pull request received 1 new comment.
-
Make DeviceMotionEventInit members nullable with null default w3c/deviceorientation#141 (1 comment by @reillyeon)
-
w3c/accelerometer
-
1 pull request opened.
-
Amend PNG image fallback code w3c/accelerometer#78, by @tidoust.
-
-
1 pull request merged.
-
Amend PNG image fallback code w3c/accelerometer#78.
-
w3c/battery
-
1 issue received 3 new comments.
-
Add an explicit use cases and requirements section w3c/battery#25 (3 comments by @anssiko, @marcoscaceres)
-
TR publications
-
12 documents published.
-
Device Posture API published as a Working Draft. History of Device Posture API
-
Screen Wake Lock API published as a Working Draft. History of Screen Wake Lock API
-
Battery Status API published as a Working Draft. History of Battery Status API
-
Magnetometer published as a Working Draft. History of Magnetometer
-
Device Orientation and Motion published 7 times as a Working Draft. History of Device Orientation and Motion
-
Compute Pressure Level 1 published as a Working Draft. History of Compute Pressure Level 1
-
GitHub
w3c/device-posture
-
3 issues opened.
-
Internationalization checklist w3c/device-posture#148, by @darktears.
-
Accessibility checklist w3c/device-posture#147, by @darktears.
-
Wide review tracker w3c/device-posture#146, by @anssiko.
-
-
3 issues received 8 new comments.
-
1 pull request opened.
-
Update Privacy considerations w3c/device-posture#145, by @anssiko.
-
-
1 pull request merged.
-
Update Privacy considerations w3c/device-posture#145.
-
-
1 pull request received 1 new comment.
w3c/compute-pressure
-
1 issue opened.
-
"Valid source type" check in PressureObserver.observe() needs more details w3c/compute-pressure#273, by @rakuco.
-
-
2 issues received 4 new comments.
-
Is PressureRecord.time a timestamp or a time that is relative to timeOrigin? w3c/compute-pressure#257 (1 comment by @yoavweiss)
-
3 pull requests opened.
-
timestamp: Redefine timestamp in Data delivery w3c/compute-pressure#274, by @arskama.
-
editorial: Fix typo ("know" -> "known") w3c/compute-pressure#272, by @rakuco.
-
editorial: Add an appendix with the list of terms used and referenced w3c/compute-pressure#271, by @rakuco.
-
-
2 pull requests merged.
-
editorial: Fix typo ("know" -> "known") w3c/compute-pressure#272.
-
editorial: Add an appendix with the list of terms used and referenced w3c/compute-pressure#271.
-
-
2 pull requests received 62 new comments.
-
Automation section and WebDriver support w3c/compute-pressure#265 (61 comments by @arskama, @JuhaVainio, @kenchris, @rakuco)
-
w3c/screen-wake-lock
-
1 issue opened.
-
Inconsistency when testing on Chrome in iOS using the Home Screen app feature (shortcut) w3c/screen-wake-lock#374, by @pandyama.
-
-
1 issue closed.
-
Inconsistency when testing on Chrome in iOS using the Home Screen app feature (shortcut) w3c/screen-wake-lock#374.
-
-
1 issue received 4 new comments.
-
Inconsistency when testing on Chrome in iOS using the Home Screen app feature (shortcut) w3c/screen-wake-lock#374 (4 comments by @marcoscaceres, @pandyama, @reillyeon, @tomayac)
-
-
1 pull request merged.
-
Add doc is fully active check w3c/screen-wake-lock#367.
-
-
1 pull request received 1 new comment.
w3c/geolocation
-
3 issues opened.
-
Non-secure context check vanished from the spec w3c/geolocation#156, by @marcoscaceres.
-
/TR/ missing from latest published version for ED w3c/geolocation#155, by @himorin.
-
repo name nit: it'd be nice if this were simply w3c/geolocation w3c/geolocation#154, by @hober.
-
-
5 issues received 15 new comments.
-
Support geolocation (especially geofencing) in the "background" w3c/geolocation#214 (7 comments by @adamjimenez, @anssiko, @hilburger, @jzijp, @phil-w, @vsychov)
-
repo name nit: it'd be nice if this were simply w3c/geolocation w3c/geolocation#154 (5 comments by @himorin, @marcoscaceres)
-
Support floorLevel on GeolocationCoordinates? w3c/geolocation#122 (1 comment by @navv-christofer-flores)
-
-
2 pull requests opened.
-
Correction: check for non-secure contexts w3c/geolocation#157, by @marcoscaceres.
-
Correction: Update acquisition algorithm to define data types and handle cached positions w3c/geolocation#153, by @marcoscaceres.
-
-
2 pull requests merged.
-
docs: show new .toJSON() capability w3c/geolocation#151.
-
chore: enable dark mode w3c/geolocation#152.
-
-
2 pull requests received 9 new comments.
-
Correction: Update acquisition algorithm to define data types and handle cached positions w3c/geolocation#153 (8 comments by @jyasskin, @marcoscaceres)
-
w3c/vibration
-
2 issues opened.
-
Obsolete this Rec w3c/vibration#34, by @marcoscaceres.
-
Update implementation report w3c/vibration#33, by @reillyeon.
-
-
1 issue closed.
-
Obsolete this Rec w3c/vibration#34.
-
-
1 issue reopened.
-
Update implementation report w3c/vibration#33, by @reillyeon.
-
-
2 issues received 20 new comments.
-
Update implementation report w3c/vibration#33 (18 comments by @anssiko, @marcoscaceres, @plehegar, @reillyeon)
-
-
1 pull request opened.
-
Update test suite and implementation report w3c/vibration#35, by @anssiko.
-
-
1 pull request merged.
-
Update test suite and implementation report w3c/vibration#35.
-
w3c/battery
-
3 issues opened.
-
Implementation report out of date w3c/battery#65, by @marcoscaceres.
-
Are there new use cases for battery API? w3c/battery#64, by @marcoscaceres.
-
Mark spec as w3c/battery#63, by @marcoscaceres.
-
-
2 issues closed.
-
Implementation report out of date w3c/battery#65.
-
Mark spec as w3c/battery#63.
-
-
4 issues reopened.
-
Are there new use cases for battery API? w3c/battery#64, by @marcoscaceres.
-
Are there new use cases for battery API? w3c/battery#64, by @marcoscaceres.
-
Are there new use cases for battery API? w3c/battery#64, by @marcoscaceres.
-
Are there new use cases for battery API? w3c/battery#64, by @marcoscaceres.
-
-
3 issues received 43 new comments.
-
Are there new use cases for battery API? w3c/battery#64 (29 comments by @anssiko, @cwilso, @marcoscaceres, @reillyeon)
-
Add an explicit use cases and requirements section w3c/battery#25 (11 comments by @anssiko, @marcoscaceres, @reillyeon, @tomayac)
-
-
2 pull requests opened.
-
Update Mounir's status w3c/battery#67, by @anssiko.
-
Update implementation report URI w3c/battery#66, by @anssiko.
-
-
2 pull requests merged.
-
Update Mounir's status w3c/battery#67.
-
Update implementation report URI w3c/battery#66.
-
w3c/deviceorientation
-
8 issues opened.
-
Goodies from Accelerometer, Motion, Orientation, Gyro specs to bring over w3c/deviceorientation#186, by @marcoscaceres.
-
How reliable is interval? w3c/deviceorientation#185, by @marcoscaceres.
-
fire an orientation event need to use the dictionary w3c/deviceorientation#184, by @marcoscaceres.
-
Combined permission request is problematic w3c/deviceorientation#183, by @marcoscaceres.
-
Alternative orientation representations? w3c/deviceorientation#182, by @marcoscaceres.
-
Fully active checks w3c/deviceorientation#181, by @marcoscaceres.
-
Abstract away underlying sensors w3c/deviceorientation#180, by @marcoscaceres.
-
Do we really need 3 permissions policies? w3c/deviceorientation#162, by @marcoscaceres.
-
-
1 issue closed.
-
Accessibility Checklist w3c/deviceorientation#131.
-
-
8 issues received 26 new comments.
-
Do we really need 3 permissions policies? w3c/deviceorientation#162 (7 comments by @anssiko, @marcoscaceres, @reillyeon)
-
Combined permission request is problematic w3c/deviceorientation#183 (5 comments by @marcoscaceres, @reillyeon)
-
How to check when permission is denied? w3c/deviceorientation#148 (3 comments by @marcoscaceres, @reillyeon)
-
Alternative orientation representations? w3c/deviceorientation#182 (3 comments by @anssiko, @marcoscaceres)
-
Abstract away underlying sensors w3c/deviceorientation#180 (2 comments by @marcoscaceres, @reillyeon)
-
Guidance needed: how to acquire compass headings in a future-compatible manner? w3c/deviceorientation#137 (1 comment by @marcoscaceres)
-
-
25 pull requests opened.
-
chore: fix link in CONTRIBUTING.md w3c/deviceorientation#179, by @marcoscaceres.
-
chore: Update README.md w3c/deviceorientation#178, by @marcoscaceres.
-
Editorial: simplify parse orientation data reading algo w3c/deviceorientation#177, by @marcoscaceres.
-
Editorial: use bikeshed shorthands for devicemotion firing steps w3c/deviceorientation#176, by @marcoscaceres.
-
Editorial: use bikeshed shorthands in requestPermission() algorithm w3c/deviceorientation#175, by @marcoscaceres.
-
Editorial: more bikeshed shorthand usage w3c/deviceorientation#174, by @marcoscaceres.
-
Editorial: simplify "significant change in orientation" algorithm w3c/deviceorientation#173, by @marcoscaceres.
-
Editorial: use more bikeshed shorthands w3c/deviceorientation#172, by @marcoscaceres.
-
Editorial: cleanup fire an orientation event algorithm w3c/deviceorientation#171, by @marcoscaceres.
-
Editorial: cleanup requestPermission() algorithm w3c/deviceorientation#170, by @marcoscaceres.
-
Editorial: rewrite abstract w3c/deviceorientation#169, by @marcoscaceres.
-
Editorial: change spec title w3c/deviceorientation#168, by @marcoscaceres.
-
Editorial: use bikeshed shorthands for task source section w3c/deviceorientation#167, by @marcoscaceres.
-
Chore: enable markdown shorthands in index.bs w3c/deviceorientation#166, by @marcoscaceres.
-
Editorial: rewrite permissions section w3c/deviceorientation#165, by @marcoscaceres.
-
Editorial: fix allowlist 'self' cross reference w3c/deviceorientation#164, by @marcoscaceres.
-
Editorial: small fixup to Device Motion section w3c/deviceorientation#163, by @marcoscaceres.
-
Editorial: drop Changes section w3c/deviceorientation#161, by @marcoscaceres.
-
Editorial: contextualize x, y, z in model a bit more w3c/deviceorientation#160, by @marcoscaceres.
-
Editorial: drop Use cases and Requirements section w3c/deviceorientation#159, by @marcoscaceres.
-
Editorial: rework scope w3c/deviceorientation#158, by @marcoscaceres.
-
Editorial: fixup/modernize examples w3c/deviceorientation#157, by @marcoscaceres.
-
Editorial: reword the Introduction section w3c/deviceorientation#156, by @marcoscaceres.
-
Editorial: automatically generate the conformance section w3c/deviceorientation#155, by @marcoscaceres.
-
Editorial: update status text and acknowledgments w3c/deviceorientation#154, by @marcoscaceres.
-
-
24 pull requests merged.
-
Editorial: use bikeshed shorthands for devicemotion firing steps w3c/deviceorientation#176.
-
Editorial: simplify parse orientation data reading algo w3c/deviceorientation#177.
-
chore: Update README.md w3c/deviceorientation#178.
-
Editorial: simplify "significant change in orientation" algorithm w3c/deviceorientation#173.
-
Editorial: update status text and acknowledgments w3c/deviceorientation#154.
-
Editorial: use bikeshed shorthands in requestPermission() algorithm w3c/deviceorientation#175.
-
chore: fix link in CONTRIBUTING.md w3c/deviceorientation#179.
-
Editorial: use more bikeshed shorthands w3c/deviceorientation#172.
-
Editorial: more bikeshed shorthand usage w3c/deviceorientation#174.
-
Editorial: cleanup fire an orientation event algorithm w3c/deviceorientation#171.
-
Editorial: cleanup requestPermission() algorithm w3c/deviceorientation#170.
-
Editorial: rewrite permissions section w3c/deviceorientation#165.
-
Editorial: small fixup to Device Motion section w3c/deviceorientation#163.
-
Editorial: contextualize x, y, z in model a bit more w3c/deviceorientation#160.
-
Editorial: automatically generate the conformance section w3c/deviceorientation#155.
-
Editorial: drop Use cases and Requirements section w3c/deviceorientation#159.
-
Editorial: change spec title w3c/deviceorientation#168.
-
Editorial: rewrite abstract w3c/deviceorientation#169.
-
Editorial: rework scope w3c/deviceorientation#158.
-
Editorial: reword the Introduction section w3c/deviceorientation#156.
-
Editorial: use bikeshed shorthands for task source section w3c/deviceorientation#167.
-
Editorial: fixup/modernize examples w3c/deviceorientation#157.
-
Editorial: fix allowlist 'self' cross reference w3c/deviceorientation#164.
-
Chore: enable markdown shorthands in index.bs w3c/deviceorientation#166.
-
-
1 pull request closed.
-
Editorial: drop Changes section w3c/deviceorientation#161.
-
-
1 pull request reopened.
-
Editorial: update status text and acknowledgments w3c/deviceorientation#154, by @himorin.
-
-
13 pull requests received 61 new comments.
-
Editorial: update status text and acknowledgments w3c/deviceorientation#154 (21 comments by @anssiko, @himorin, @marcoscaceres, @reillyeon)
-
Editorial: rewrite permissions section w3c/deviceorientation#165 (8 comments by @himorin, @marcoscaceres, @reillyeon)
-
Editorial: use bikeshed shorthands for devicemotion firing steps w3c/deviceorientation#176 (7 comments by @marcoscaceres, @reillyeon)
-
Make DeviceMotionEventInit members nullable with null default w3c/deviceorientation#141 (3 comments by @annevk, @marcoscaceres)
-
Chore: enable markdown shorthands in index.bs w3c/deviceorientation#166 (3 comments by @himorin, @marcoscaceres, @reillyeon)
-
Editorial: small fixup to Device Motion section w3c/deviceorientation#163 (3 comments by @marcoscaceres, @reillyeon)
-
Editorial: contextualize x, y, z in model a bit more w3c/deviceorientation#160 (3 comments by @marcoscaceres, @reillyeon)
-
Editorial: drop Changes section w3c/deviceorientation#161 (3 comments by @anssiko, @himorin, @reillyeon)
-
Editorial: simplify "significant change in orientation" algorithm w3c/deviceorientation#173 (2 comments by @reillyeon)
-
Editorial: automatically generate the conformance section w3c/deviceorientation#155 (2 comments by @marcoscaceres, @rakuco)
-
w3c/gyroscope
-
1 issue opened.
-
Broken references in Gyroscope w3c/gyroscope#62, by @dontcallmedom-bot.
-
-
1 issue received 5 new comments.
-
Broken references in Gyroscope w3c/gyroscope#62 (5 comments by @anssiko, @marcoscaceres, @reillyeon)
-
w3c/magnetometer
-
1 issue opened.
-
"magnetometer" permission redefined w3c/magnetometer#73, by @reillyeon.
-
-
1 issue closed.
-
"magnetometer" permission redefined w3c/magnetometer#73.
-
-
1 pull request opened.
-
Update "magnetometer" permission reference w3c/magnetometer#74, by @anssiko.
-
-
1 pull request merged.
-
Update "magnetometer" permission reference w3c/magnetometer#74.
-
-
1 pull request received 4 new comments.
TR publications
-
7 documents published.
-
Contact Picker API published as a Working Draft. History of Contact Picker API
-
Compute Pressure Level 1 published 3 times as a Working Draft. History of Compute Pressure Level 1
-
DeviceOrientation Event Specification published as a Working Draft. History of DeviceOrientation Event Specification
-
Screen Wake Lock API published as a Working Draft. History of Screen Wake Lock API
-
Device Posture API published as a Working Draft. History of Device Posture API
-
GitHub
w3c/contact-picker
-
2 pull requests merged.
-
Editorial: Add Security Considerations w3c/contact-picker#75.
-
Use navigables + transient activation w3c/contact-picker#76.
-
w3c/geolocation
-
3 issues opened.
-
Set up process and markers for updating the Proposed Edited Recommendation w3c/geolocation#148, by @marcoscaceres.
-
A means to test the API via Web Driver w3c/geolocation#146, by @marcoscaceres.
-
Add support for converting Geolocation Position+Coordinates to JSON (object) w3c/geolocation#145, by @marcoscaceres.
-
-
5 issues closed.
-
Support floorLevel on GeolocationCoordinates? w3c/geolocation#122.
-
Define "geographic coordinates" w3c/geolocation#136.
-
Set up process and markers for updating the Proposed Edited Recommendation w3c/geolocation#148.
-
Add support for converting Geolocation Position+Coordinates to JSON (object) w3c/geolocation#145.
-
What does "decimal degrees" mean? w3c/geolocation#135.
-
-
7 issues received 29 new comments.
-
Support geolocation (especially geofencing) in the "background" w3c/geolocation#214 (10 comments by @Bessonov, @clshortfuse, @dlilga, @evancaldwell, @fabyeah, @hilburger, @jlfy738, @mfulton26, @reillyeon)
-
A means to test the API via Web Driver w3c/geolocation#146 (9 comments by @marcoscaceres, @reillyeon)
-
Add support for converting Geolocation Position+Coordinates to JSON (object) w3c/geolocation#145 (4 comments by @marcoscaceres, @reillyeon)
-
Set up process and markers for updating the Proposed Edited Recommendation w3c/geolocation#148 (2 comments by @marcoscaceres, @saschanaz)
-
-
4 pull requests opened.
-
chore: enable dark mode w3c/geolocation#152, by @marcoscaceres.
-
docs: show new .toJSON() capability w3c/geolocation#151, by @marcoscaceres.
-
chore: put in updatable rec infra w3c/geolocation#149, by @marcoscaceres.
-
Addition: expose .toJSON() on GeolocationCoordinates + GeolocationPosition w3c/geolocation#147, by @marcoscaceres.
-
-
5 pull requests merged.
-
chore: put in updatable rec infra w3c/geolocation#149.
-
Addition: expose .toJSON() on GeolocationCoordinates + GeolocationPosition w3c/geolocation#147.
-
Correction: Clarify units and reference geodetic system for latitude and longitude w3c/geolocation#138.
-
chore: bring Marcos out of retirement w3c/geolocation#143.
-
Added webapps as group w3c/geolocation#144.
-
-
1 pull request closed.
-
Add `[SecureContext]` tags to the interfaces w3c/geolocation#142.
-
-
5 pull requests received 19 new comments.
-
Addition: expose .toJSON() on GeolocationCoordinates + GeolocationPosition w3c/geolocation#147 (9 comments by @marcoscaceres, @reillyeon, @saschanaz)
-
Correction: Clarify units and reference geodetic system for latitude and longitude w3c/geolocation#138 (3 comments by @marcoscaceres)
-
docs: show new .toJSON() capability w3c/geolocation#151 (2 comments by @hamishwillee, @marcoscaceres)
-
w3c/compute-pressure
-
8 issues opened.
-
supportedSources should not have [SameObject] w3c/compute-pressure#269, by @rakuco.
-
Bikeshed the source name for per-process w3c/compute-pressure#267, by @kenchris.
-
Clarify what supportedSources() should expose. w3c/compute-pressure#266, by @arskama.
-
Move source to options w3c/compute-pressure#262, by @kenchris.
-
Move Options to observe? w3c/compute-pressure#259, by @kenchris.
-
Get rid of the promise returned by observe w3c/compute-pressure#258, by @kenchris.
-
Is PressureRecord.time a timestamp or a time that is relative to timeOrigin? w3c/compute-pressure#257, by @Elchi3.
-
PressureObserver options object: constructor vs observe method w3c/compute-pressure#256, by @Elchi3.
-
-
7 issues closed.
-
Clarify what supportedSources() should expose. w3c/compute-pressure#266.
-
Consider how or whether to handle runtime errors w3c/compute-pressure#115.
-
Consider using AbortSignal in observe w3c/compute-pressure#114.
-
Get rid of the promise returned by observe w3c/compute-pressure#258.
-
Move source to options w3c/compute-pressure#262.
-
PressureObserver options object: constructor vs observe method w3c/compute-pressure#256.
-
Move Options to observe? w3c/compute-pressure#259.
-
-
1 issue reopened.
-
Is PressureRecord.time a timestamp or a time that is relative to timeOrigin? w3c/compute-pressure#257, by @rakuco.
-
-
13 issues received 64 new comments.
-
Is PressureRecord.time a timestamp or a time that is relative to timeOrigin? w3c/compute-pressure#257 (19 comments by @arskama, @Elchi3, @kenchris, @rakuco, @yoavweiss)
-
Get rid of the promise returned by observe w3c/compute-pressure#258 (10 comments by @Elchi3, @kenchris, @rakuco)
-
supportedSources should not have [SameObject] w3c/compute-pressure#269 (7 comments by @foolip, @kenchris, @rakuco)
-
Move source to options w3c/compute-pressure#262 (7 comments by @Elchi3, @kenchris, @rakuco, @tomayac)
-
Clarify what supportedSources() should expose. w3c/compute-pressure#266 (5 comments by @arskama, @Elchi3, @kenchris, @rakuco)
-
Determine the behavior when calling unobserve/disconnect method before the promise returned by observe method is settled w3c/compute-pressure#164 (5 comments by @arskama, @Elchi3, @kenchris)
-
PressureObserver options object: constructor vs observe method w3c/compute-pressure#256 (3 comments by @arskama, @Elchi3, @kenchris)
-
Bikeshed the source name for per-process w3c/compute-pressure#267 (2 comments by @Elchi3, @kenchris)
-
-
7 pull requests opened.
-
Give Florian credits for his feedback w3c/compute-pressure#270, by @kenchris.
-
Rename supportedSources to knownSources w3c/compute-pressure#268, by @kenchris.
-
Automation section and WebDriver support w3c/compute-pressure#265, by @kenchris.
-
Don't return a promise w3c/compute-pressure#264, by @kenchris.
-
Associate sample interval with source w3c/compute-pressure#263, by @kenchris.
-
Move options to observe() w3c/compute-pressure#261, by @kenchris.
-
Fix documentation: Options to observe method w3c/compute-pressure#260, by @arskama.
-
-
5 pull requests merged.
-
Rename supportedSources to knownSources w3c/compute-pressure#268.
-
Give Florian credits for his feedback w3c/compute-pressure#270.
-
Associate sample interval with source w3c/compute-pressure#263.
-
Fix documentation: Options to observe method w3c/compute-pressure#260.
-
Move options to observe() w3c/compute-pressure#261.
-
-
1 pull request closed.
-
Don't return a promise w3c/compute-pressure#264.
-
-
1 pull request reopened.
-
Automation section and WebDriver support w3c/compute-pressure#265, by @kenchris.
-
-
6 pull requests received 35 new comments.
-
Automation section and WebDriver support w3c/compute-pressure#265 (15 comments by @arskama, @JuhaVainio, @kenchris, @rakuco)
-
Rename supportedSources to knownSources w3c/compute-pressure#268 (6 comments by @arskama, @kenchris, @rakuco)
-
Associate sample interval with source w3c/compute-pressure#263 (6 comments by @arskama, @kenchris, @rakuco)
-
Fix documentation: Options to observe method w3c/compute-pressure#260 (2 comments by @arskama, @kenchris)
-
w3c/screen-wake-lock
-
1 issue opened.
-
Add more visibility tests w3c/screen-wake-lock#373, by @marcoscaceres.
-
-
2 issues received 6 new comments.
-
Need maximum screen brightness mode w3c/screen-wake-lock#129 (5 comments by @anssiko, @max-keviv, @tomayac)
-
-
1 pull request closed.
-
Fix the build w3c/screen-wake-lock#372.
-
-
1 pull request reopened.
-
Require transient activation w3c/screen-wake-lock#351, by @marcoscaceres.
-
-
3 pull requests received 16 new comments.
-
Add doc is fully active check w3c/screen-wake-lock#367 (10 comments by @marcoscaceres, @rakuco, @reillyeon)
-
w3c/deviceorientation
-
2 issues closed.
-
"Status of this document" section needs to reflect join deliverable status w3c/deviceorientation#145.
-
Fix the build w3c/deviceorientation#151.
-
-
3 issues received 4 new comments.
-
How to check when permission is denied? w3c/deviceorientation#148 (2 comments by @marcoscaceres, @reillyeon)
-
"Status of this document" section needs to reflect join deliverable status w3c/deviceorientation#145 (1 comment by @anssiko)
-
-
1 pull request merged.
-
chore: add Marcos to editorial team w3c/deviceorientation#146.
-
-
2 pull requests closed.
-
Fix the build and update status w3c/deviceorientation#153.
-
Chore auto-publish.yml: update WG decision URL w3c/deviceorientation#152.
-
-
3 pull requests received 8 new comments.
-
automation: Adapt to Generic Sensor changes to stash provided readings w3c/deviceorientation#147 (5 comments by @rakuco, @reillyeon)
-
Chore auto-publish.yml: update WG decision URL w3c/deviceorientation#152 (1 comment by @marcoscaceres)
-
w3c/device-posture
-
1 pull request opened.
-
Remove the extremely unstable wording from the spec because it's quite stable so far. w3c/device-posture#143, by @darktears.
-
-
1 pull request merged.
-
Remove the extremely unstable wording from the spec because it's quite stable so far. w3c/device-posture#143.
-
-
1 pull request received 1 new comment.
-
Remove the extremely unstable wording from the spec because it's quite stable so far. w3c/device-posture#143 (1 comment by @darktears)
-
TR publications
-
14 documents published.
-
Device Posture API published 10 times as a Working Draft. History of Device Posture API
-
Compute Pressure Level 1 published twice as a Working Draft. History of Compute Pressure Level 1
-
DeviceOrientation Event Specification published twice as a Working Draft. History of DeviceOrientation Event Specification
-
Participants
-
1 participant left.
-
Ovidio Ruiz-Henríquez (Google LLC) left.
-
GitHub
w3c/geolocation
-
1 issue received 6 new comments.
-
Support geolocation (especially geofencing) in the "background" w3c/geolocation#214 (6 comments by @anssiko, @evancaldwell, @jlannoy, @kavdev, @leonelvsc)
-
-
2 pull requests opened.
-
Added webapps as group w3c/geolocation#144, by @himorin.
-
chore: bring Marcos out of retirement w3c/geolocation#143, by @marcoscaceres.
-
-
1 pull request received 1 new comment.
w3c/deviceorientation
-
3 issues opened.
-
Fix the build w3c/deviceorientation#151, by @anssiko.
-
How to check when permission is denied? w3c/deviceorientation#148, by @anssiko.
-
"Status of this document" section needs to reflect join deliverable status w3c/deviceorientation#145, by @reillyeon.
-
-
1 issue closed.
-
Wide review tracker w3c/deviceorientation#130.
-
-
6 issues received 17 new comments.
-
"Status of this document" section needs to reflect join deliverable status w3c/deviceorientation#145 (7 comments by @anssiko, @himorin, @marcoscaceres, @siusin)
-
DeviceMotionEvent atttributes can't be null per current IDL w3c/deviceorientation#91 (4 comments by @annevk, @reillyeon, @saschanaz)
-
How to check when permission is denied? w3c/deviceorientation#148 (2 comments by @rakuco, @reillyeon)
-
-
9 pull requests opened.
-
Fix the build and update status w3c/deviceorientation#153, by @anssiko.
-
Chore auto-publish.yml: update WG decision URL w3c/deviceorientation#152, by @marcoscaceres.
-
Add Accessibility considerations w3c/deviceorientation#150, by @anssiko.
-
editorial: Identify at risk features and their causes w3c/deviceorientation#149, by @reillyeon.
-
automation: Adapt to Generic Sensor changes to stash provided readings w3c/deviceorientation#147, by @rakuco.
-
chore: add Marcos to editorial team w3c/deviceorientation#146, by @marcoscaceres.
-
Add an inline issue for the maximum sampling frequency cap w3c/deviceorientation#144, by @anssiko.
-
Create PULL_REQUEST_TEMPLATE.md w3c/deviceorientation#143, by @reillyeon.
-
Update status of this document w3c/deviceorientation#142, by @anssiko.
-
-
5 pull requests merged.
-
editorial: Identify at risk features and their causes w3c/deviceorientation#149.
-
Add Accessibility considerations w3c/deviceorientation#150.
-
Update status of this document w3c/deviceorientation#142.
-
Add an inline issue for the maximum sampling frequency cap w3c/deviceorientation#144.
-
Create PULL_REQUEST_TEMPLATE.md w3c/deviceorientation#143.
-
-
6 pull requests received 46 new comments.
-
Add Accessibility considerations w3c/deviceorientation#150 (19 comments by @anssiko, @kenchris, @matatk, @rakuco)
-
Update status of this document w3c/deviceorientation#142 (18 comments by @anssiko, @himorin, @marcoscaceres, @reillyeon)
-
editorial: Identify at risk features and their causes w3c/deviceorientation#149 (3 comments by @himorin, @reillyeon)
-
Chore auto-publish.yml: update WG decision URL w3c/deviceorientation#152 (2 comments by @himorin, @marcoscaceres)
-
automation: Adapt to Generic Sensor changes to stash provided readings w3c/deviceorientation#147 (2 comments by @rakuco, @reillyeon)
-
Add an inline issue for the maximum sampling frequency cap w3c/deviceorientation#144 (2 comments by @anssiko, @reillyeon)
-
w3c/screen-wake-lock
-
3 pull requests opened.
-
Fix the build w3c/screen-wake-lock#372, by @anssiko.
-
Added webapps as group w3c/screen-wake-lock#371, by @himorin.
-
chore: bring Marcos out of retirement w3c/screen-wake-lock#370, by @marcoscaceres.
-
-
2 pull requests merged.
-
Added webapps as group w3c/screen-wake-lock#371.
-
chore: bring Marcos out of retirement w3c/screen-wake-lock#370.
-
-
2 pull requests received 5 new comments.
-
chore: bring Marcos out of retirement w3c/screen-wake-lock#370 (3 comments by @himorin, @marcoscaceres, @rakuco)
-
w3c/device-posture
-
3 issues opened.
-
Spec should specify a testing interface w3c/device-posture#140, by @rakuco.
-
Dependencies section should be removed w3c/device-posture#135, by @rakuco.
-
Should Device Posture API be exposed to iframes (JS or CSS) w3c/device-posture#111, by @darktears.
-
-
15 issues closed.
-
Spec should specify a testing interface w3c/device-posture#140.
-
Links from sec/priv sections back to normative mitigations? w3c/device-posture#53.
-
Dependencies section should be removed w3c/device-posture#135.
-
Requesting Accessibility Considerations section w3c/device-posture#70.
-
Linking to plural forms w3c/device-posture#77.
-
logos are preventing auto-publish w3c/device-posture#90.
-
Use Navigables instead of browsing contexts w3c/device-posture#104.
-
Heads up: refs to `pagevisibility` about to be removed w3c/device-posture#95.
-
Do developers want to identify when a device is being used with a pen / drawing posture? w3c/device-posture#96.
-
CSS Spanning outdated w3c/device-posture#99.
-
We need to add more examples in the explainer w3c/device-posture#79.
-
Fetching the posture type should be async? w3c/device-posture#78.
-
Adding fold position to identify orientation instead of identify device model w3c/device-posture#63.
-
Supporting asymmetric shaped displays w3c/device-posture#37.
-
-
8 issues received 10 new comments.
-
Should Device Posture API be exposed to iframes (JS or CSS) w3c/device-posture#111 (3 comments by @darktears, @kenchris, @reillyeon)
-
Links from sec/priv sections back to normative mitigations? w3c/device-posture#53 (1 comment by @darktears)
-
Adding fold position to identify orientation instead of identify device model w3c/device-posture#63 (1 comment by @darktears)
-
Support for single/multi-Screen folds, off-center folds, and multiple folds in a single Screen. w3c/device-posture#38 (1 comment by @darktears)
-
-
23 pull requests opened.
-
Add automation support via WebDriver w3c/device-posture#141, by @JuhaVainio.
-
More work on the privacy section. w3c/device-posture#138, by @darktears.
-
Remove the dependencies section. w3c/device-posture#136, by @darktears.
-
Use xref to quote specs rather than data-cite. w3c/device-posture#134, by @darktears.
-
Improve the privacy section. w3c/device-posture#132, by @darktears.
-
Few fixes for the accessibility section w3c/device-posture#130, by @darktears.
-
device posture change steps: Refer to disallowRecursion by name in calls w3c/device-posture#128, by @rakuco.
-
Add accessibility section w3c/device-posture#127, by @darktears.
-
Fix Document references. w3c/device-posture#125, by @darktears.
-
Fix code sample error. w3c/device-posture#123, by @darktears.
-
Fix ReSpec warning on device-posture Media Query w3c/device-posture#122, by @darktears.
-
Remove additional logos to keep consistent with other W3C specs. w3c/device-posture#121, by @darktears.
-
Modernize algorithms in "Algorithm" section w3c/device-posture#120, by @rakuco.
-
editorial: Use navigables, not browsing contexts, in CSS media feature w3c/device-posture#119, by @rakuco.
-
editorial: Reference the "visibility state" definition in S&P considerations w3c/device-posture#118, by @rakuco.
-
editorial: Do not define Navigator, just reference it w3c/device-posture#117, by @rakuco.
-
editorial: Do not define Navigator, just reference it w3c/device-posture#116, by @rakuco.
-
Update explainer. w3c/device-posture#115, by @darktears.
-
Remove the policy control part from the spec. w3c/device-posture#114, by @darktears.
-
Add Policy Control section in the specification. w3c/device-posture#112, by @darktears.
-
Add the security-privacy-self-assessment for Origin Trial w3c/device-posture#110, by @darktears.
-
Add a new co-editor w3c/device-posture#109, by @anssiko.
-
Update old code in the spec. w3c/device-posture#108, by @darktears.
-
-
22 pull requests merged.
-
Add automation support via WebDriver w3c/device-posture#141.
-
More work on the privacy section. w3c/device-posture#138.
-
Remove the dependencies section. w3c/device-posture#136.
-
Use xref to quote specs rather than data-cite. w3c/device-posture#134.
-
Improve the privacy section. w3c/device-posture#132.
-
Few fixes for the accessibility section w3c/device-posture#130.
-
Add accessibility section w3c/device-posture#127.
-
device posture change steps: Refer to disallowRecursion by name in calls w3c/device-posture#128.
-
Fix Document references. w3c/device-posture#125.
-
Fix ReSpec warning on device-posture Media Query w3c/device-posture#122.
-
Fix code sample error. w3c/device-posture#123.
-
Remove additional logos to keep consistent with other W3C specs. w3c/device-posture#121.
-
Modernize algorithms in "Algorithm" section w3c/device-posture#120.
-
editorial: Reference the "visibility state" definition in S&P considerations w3c/device-posture#118.
-
editorial: Do not define Navigator, just reference it w3c/device-posture#117.
-
editorial: Use navigables, not browsing contexts, in CSS media feature w3c/device-posture#119.
-
Update explainer. w3c/device-posture#115.
-
Remove the policy control part from the spec. w3c/device-posture#114.
-
Add the security-privacy-self-assessment for Origin Trial w3c/device-posture#110.
-
Add Policy Control section in the specification. w3c/device-posture#112.
-
Update old code in the spec. w3c/device-posture#108.
-
Add a new co-editor w3c/device-posture#109.
-
-
1 pull request closed.
-
editorial: Do not define Navigator, just reference it w3c/device-posture#116.
-
-
11 pull requests received 71 new comments.
-
Add the security-privacy-self-assessment for Origin Trial w3c/device-posture#110 (17 comments by @darktears, @kenchris)
-
Use xref to quote specs rather than data-cite. w3c/device-posture#134 (2 comments by @darktears, @rakuco)
-
Fix ReSpec warning on device-posture Media Query w3c/device-posture#122 (2 comments by @darktears, @kenchris)
-
Remove additional logos to keep consistent with other W3C specs. w3c/device-posture#121 (1 comment by @darktears)
w3c/compute-pressure
-
1 issue opened.
-
Sampling interval instead of sampling rate w3c/compute-pressure#253, by @foolip.
-
-
1 issue closed.
-
Sampling interval instead of sampling rate w3c/compute-pressure#253.
-
-
2 issues received 9 new comments.
-
Sampling interval instead of sampling rate w3c/compute-pressure#253 (8 comments by @andreasbovens, @foolip, @kenchris, @miketaylr, @rakuco, @tomayac)
-
-
4 pull requests opened.
-
Updating documentation from sampleRate to sampleInterval. w3c/compute-pressure#255, by @arskama.
-
Change sampleRate to sampleInterval w3c/compute-pressure#254, by @kenchris.
-
Expand discussion about timing vs external pressure w3c/compute-pressure#252, by @kenchris.
-
Add info about another attack type w3c/compute-pressure#251, by @kenchris.
-
-
4 pull requests merged.
-
Updating documentation from sampleRate to sampleInterval. w3c/compute-pressure#255.
-
Change sampleRate to sampleInterval w3c/compute-pressure#254.
-
Expand discussion about timing vs external pressure w3c/compute-pressure#252.
-
Add info about another attack type w3c/compute-pressure#251.
-
-
3 pull requests received 38 new comments.
-
Change sampleRate to sampleInterval w3c/compute-pressure#254 (25 comments by @arskama, @foolip, @kenchris, @rakuco)
-
Add info about another attack type w3c/compute-pressure#251 (8 comments by @anssiko, @arskama, @kenchris)
-
Expand discussion about timing vs external pressure w3c/compute-pressure#252 (5 comments by @arskama, @kenchris)
-
w3c/sensors
-
1 issue closed.
-
Currently focused area needs a top-level browsing context w3c/sensors#436.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
automation: Save readings set when no sensors are active w3c/sensors#487, by @rakuco.
-
Lifecycle
-
1 charter started.
-
Chartered until 28 February 2026.
-
TR publications
-
7 documents published.
-
Generic Sensor API published 3 times as a Candidate Recommendation Draft. History of Generic Sensor API
-
Contact Picker API published twice as a Working Draft. History of Contact Picker API
-
DeviceOrientation Event Specification published twice as a Working Draft. History of DeviceOrientation Event Specification
-
Past meetings
GitHub
w3c/deviceorientation
-
7 issues closed.
-
Malicious use of the phone's Gyroscope w3c/deviceorientation#30.
-
Add way of getting current orientation w3c/deviceorientation#11.
-
DeviceOrientationEvent.absolute's value when data cannot be obtained w3c/deviceorientation#119.
-
Security/privacy consideration: cross-origin linkage w3c/deviceorientation#33.
-
Need to define the DeviceMotionEvent constructor w3c/deviceorientation#83.
-
requestPermission() and event handling clarification w3c/deviceorientation#74.
-
Internationalization Checklist w3c/deviceorientation#132.
-
-
13 issues received 28 new comments.
-
DeviceMotionEvent atttributes can't be null per current IDL w3c/deviceorientation#91 (5 comments by @annevk, @anssiko, @reillyeon)
-
Behavior when event data cannot be provided is underspecified w3c/deviceorientation#118 (2 comments by @anssiko, @reillyeon)
-
Security/privacy consideration: cross-origin linkage w3c/deviceorientation#33 (2 comments by @rakuco)
-
Need to define the DeviceMotionEvent constructor w3c/deviceorientation#83 (2 comments by @rakuco, @reillyeon)
-
Guidance needed: how to acquire compass headings in a future-compatible manner? w3c/deviceorientation#137 (1 comment by @anssiko)
-
requestPermission() and event handling clarification w3c/deviceorientation#74 (1 comment by @rakuco)
-
Same origin S&P requirement conflicts with Permissions Policy integration w3c/deviceorientation#133 (1 comment by @rakuco)
-
4 pull requests opened.
-
Make DeviceMotionEventInit members nullable with null default w3c/deviceorientation#141, by @reillyeon.
-
Check visibility state in algorithms that fire events w3c/deviceorientation#140, by @rakuco.
-
DeviceOrientationEvent: Define absolute's value on error w3c/deviceorientation#139, by @rakuco.
-
changes: Mention #136 in the Permissions Policy integration item w3c/deviceorientation#138, by @rakuco.
-
-
3 pull requests merged.
-
DeviceOrientationEvent: Define absolute's value on error w3c/deviceorientation#139.
-
Check visibility state in algorithms that fire events w3c/deviceorientation#140.
-
changes: Mention #136 in the Permissions Policy integration item w3c/deviceorientation#138.
-
-
3 pull requests received 9 new comments.
-
DeviceOrientationEvent: Define absolute's value on error w3c/deviceorientation#139 (6 comments by @rakuco, @reillyeon)
-
Replace same-origin Security & Privacy requirement with Permissions Policy one w3c/deviceorientation#136 (2 comments by @anssiko, @rakuco)
-
Make DeviceMotionEventInit members nullable with null default w3c/deviceorientation#141 (1 comment by @annevk)
-
w3c/sensors
-
3 issues opened.
-
Broken references in Generic Sensor API w3c/sensors#486, by @dontcallmedom-bot.
-
'Requested sampling frequency' automation concept is confusing w3c/sensors#484, by @rakuco.
-
"Connect to sensor" does not take fusion sensors into consideration w3c/sensors#479, by @rakuco.
-
-
2 issues received 2 new comments.
-
"Connect to sensor" does not take fusion sensors into consideration w3c/sensors#479 (1 comment by @rakuco)
-
5 pull requests opened.
-
editorial: Fix requestedSamplingFrequency's description w3c/sensors#485, by @rakuco.
-
Make current origin and focused area's origin check more precise w3c/sensors#483, by @rakuco.
-
Remove note about sharing data between platform sensors w3c/sensors#482, by @rakuco.
-
Request sensor access: Access "sensor permission names" correctly w3c/sensors#481, by @rakuco.
-
Sensor.timestamp: Account for "get value from latest reading" returning null w3c/sensors#480, by @rakuco.
-
-
6 pull requests merged.
-
Add an informative background article w3c/sensors#458.
-
editorial: Fix requestedSamplingFrequency's description w3c/sensors#485.
-
Make current origin and focused area's origin check more precise w3c/sensors#483.
-
Remove note about sharing data between platform sensors w3c/sensors#482.
-
Request sensor access: Access "sensor permission names" correctly w3c/sensors#481.
-
-
1 pull request closed.
-
Fix up the focused area restrictions. w3c/sensors#403.
-
-
1 pull request received 1 new comment.
w3c/contact-picker
-
4 issues reopened.
-
Add payerGivenName + payerFamilyName to PaymentAddress w3c/contact-picker#69, by @ianbjacobs.
-
Add latitude and longitude to ContactAddress interface? w3c/contact-picker#72, by @ianbjacobs.
-
Matching ContactAddress fields to autofill attributes w3c/contact-picker#71, by @ianbjacobs.
-
Add phonetic name as one of `ContactAddress` properties w3c/contact-picker#70, by @ianbjacobs.
-
-
4 issues received 6 new comments.
-
Add payerGivenName + payerFamilyName to PaymentAddress w3c/contact-picker#69 (3 comments by @HolgerJeromin, @ianbjacobs)
-
Add latitude and longitude to ContactAddress interface? w3c/contact-picker#72 (1 comment by @ianbjacobs)
-
Matching ContactAddress fields to autofill attributes w3c/contact-picker#71 (1 comment by @ianbjacobs)
-
Add phonetic name as one of `ContactAddress` properties w3c/contact-picker#70 (1 comment by @ianbjacobs)
-
-
5 pull requests opened.
-
Use navigables + transient activation w3c/contact-picker#76, by @marcoscaceres.
-
Editorial: Add Security Considerations w3c/contact-picker#75, by @marcoscaceres.
-
chore: export defs needed by Payment Request API w3c/contact-picker#74, by @marcoscaceres.
-
chore: export defs needed by Payment Request w3c/contact-picker#73, by @marcoscaceres.
-
Add '[SecureContext]` tags to the interface w3c/contact-picker#68, by @OnkarRuikar.
-
-
2 pull requests merged.
-
chore: export defs needed by Payment Request API w3c/contact-picker#74.
-
Add '[SecureContext]` tags to the interface w3c/contact-picker#68.
-
-
1 pull request closed.
-
chore: export defs needed by Payment Request w3c/contact-picker#73.
-
-
3 pull requests received 8 new comments.
-
Add '[SecureContext]` tags to the interface w3c/contact-picker#68 (6 comments by @marcoscaceres, @w3cbot)
-
chore: export defs needed by Payment Request API w3c/contact-picker#74 (1 comment by @marcoscaceres)
-
w3c/compute-pressure
-
1 issue opened.
-
Combine Compute Pressure API with WebRTC features w3c/compute-pressure#250, by @MatanYemini.
-
-
2 issues received 2 new comments.
-
Energy measurement: Track energy consumption for a tab w3c/compute-pressure#249 (1 comment by @MatanYemini)
w3c/geolocation
-
1 pull request opened.
-
Add `[SecureContext]` tags to the interfaces w3c/geolocation#142, by @OnkarRuikar.
-
w3c/screen-wake-lock
-
1 issue received 2 new comments.
-
Clarify use cases in Screen Brightness API explainer w3c/screen-wake-lock#341 (2 comments by @marcoscaceres, @willmorgan)
-
TR publications
-
20 documents published.
-
Generic Sensor API published as a Candidate Recommendation Draft. History of Generic Sensor API
-
Accelerometer published 3 times as a Candidate Recommendation Draft. History of Accelerometer
-
Gyroscope published 3 times as a Candidate Recommendation Draft. History of Gyroscope
-
DeviceOrientation Event Specification published 6 times as a Working Draft. History of DeviceOrientation Event Specification
-
Ambient Light Sensor published twice as a Working Draft. History of Ambient Light Sensor
-
Orientation Sensor published twice as a Working Draft. History of Orientation 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
-
Magnetometer published as a Working Draft. History of Magnetometer
-
GitHub
w3c/deviceorientation
-
5 issues opened.
-
Guidance needed: how to acquire compass headings in a future-compatible manner? w3c/deviceorientation#137, by @juj.
-
Same origin S&P requirement conflicts with Permissions Policy integration w3c/deviceorientation#133, by @rakuco.
-
Internationalization Checklist w3c/deviceorientation#132, by @anssiko.
-
Accessibility Checklist w3c/deviceorientation#131, by @anssiko.
-
Wide review tracker w3c/deviceorientation#130, by @anssiko.
-
-
2 issues closed.
-
Same origin S&P requirement conflicts with Permissions Policy integration w3c/deviceorientation#133.
-
Add automation support using WebDriver w3c/deviceorientation#122.
-
-
3 issues received 14 new comments.
-
Wide review tracker w3c/deviceorientation#130 (10 comments by @anssiko, @himorin, @rakuco, @reillyeon)
-
Same origin S&P requirement conflicts with Permissions Policy integration w3c/deviceorientation#133 (2 comments by @rakuco, @reillyeon)
-
-
5 pull requests opened.
-
Replace same-origin Security & Privacy requirement with Permissions Policy one w3c/deviceorientation#136, by @rakuco.
-
Security & Privacy Questionnaire: Mention Permissions Policy integration w3c/deviceorientation#135, by @rakuco.
-
editorial: Fix grammar and missing words in Permissions Policy note w3c/deviceorientation#134, by @rakuco.
-
Make requestPermission()'s behavior more backwards-compatible w3c/deviceorientation#129, by @rakuco.
-
Update w3c.json w3c/deviceorientation#128, by @himorin.
-
-
7 pull requests merged.
-
Replace same-origin Security & Privacy requirement with Permissions Policy one w3c/deviceorientation#136.
-
Security & Privacy Questionnaire: Mention Permissions Policy integration w3c/deviceorientation#135.
-
editorial: Fix grammar and missing words in Permissions Policy note w3c/deviceorientation#134.
-
Add Security and Privacy Self-Review Questionnaire w3c/deviceorientation#126.
-
Make requestPermission()'s behavior more backwards-compatible w3c/deviceorientation#129.
-
Update w3c.json w3c/deviceorientation#128.
-
Add automation support via WebDriver w3c/deviceorientation#124.
-
-
4 pull requests received 21 new comments.
-
Add Security and Privacy Self-Review Questionnaire w3c/deviceorientation#126 (11 comments by @anssiko, @lknik, @toreini)
-
Make requestPermission()'s behavior more backwards-compatible w3c/deviceorientation#129 (6 comments by @kenchris, @rakuco)
-
Security & Privacy Questionnaire: Mention Permissions Policy integration w3c/deviceorientation#135 (1 comment by @reillyeon)
-
w3c/screen-wake-lock
-
2 issues received 3 new comments.
-
Clarify use cases in Screen Brightness API explainer w3c/screen-wake-lock#341 (1 comment by @willmorgan)
-
1 pull request opened.
-
Update w3c.json w3c/screen-wake-lock#369, by @himorin.
-
-
1 pull request merged.
-
Update w3c.json w3c/screen-wake-lock#369.
-
-
1 pull request closed.
-
Remove redundant check w3c/screen-wake-lock#368.
-
-
2 pull requests received 2 new comments.
w3c/sensors
-
1 issue opened.
-
1 issue received 2 new comments.
-
automation: Reading updates without active Sensor instances should be stashed, not discarded w3c/sensors#478 (2 comments by @rakuco, @reillyeon)
-
-
2 pull requests opened.
-
Remove the "parse quaternion reading" algorithm w3c/sensors#477, by @rakuco.
-
Update w3c.json w3c/sensors#476, by @himorin.
-
-
2 pull requests merged.
-
Remove the "parse quaternion reading" algorithm w3c/sensors#477.
-
Update w3c.json w3c/sensors#476.
-
-
1 pull request received 4 new comments.
-
Remove the "parse quaternion reading" algorithm w3c/sensors#477 (4 comments by @anssiko, @himorin, @rakuco)
-
w3c/ambient-light
-
1 issue received 6 new comments.
-
Security and privacy considerations for Ambient Light Events w3c/ambient-light#8 (6 comments by @anssiko, @chaals, @fhirsch, @lknik)
-
-
2 pull requests opened.
-
Add a new reference to Security and Privacy Considerations w3c/ambient-light#90, by @anssiko.
-
Update w3c.json w3c/ambient-light#89, by @himorin.
-
-
2 pull requests merged.
-
Add a new reference to Security and Privacy Considerations w3c/ambient-light#90.
-
Update w3c.json w3c/ambient-light#89.
-
-
1 pull request received 1 new comment.
-
Add a new reference to Security and Privacy Considerations w3c/ambient-light#90 (1 comment by @anssiko)
-
w3c/orientation-sensor
-
1 pull request opened.
-
Update w3c.json w3c/orientation-sensor#84, by @himorin.
-
-
2 pull requests merged.
-
Automation: integrate with Device Orientation API's Automation section w3c/orientation-sensor#83.
-
Update w3c.json w3c/orientation-sensor#84.
-
-
1 pull request received 3 new comments.
-
Automation: integrate with Device Orientation API's Automation section w3c/orientation-sensor#83 (3 comments by @rakuco, @reillyeon)
-
w3c/compute-pressure
-
1 issue opened.
-
Energy measurement: Track energy consumption for a tab w3c/compute-pressure#249, by @arskama.
-
-
1 pull request opened.
-
Update OT token w3c/compute-pressure#248, by @kenchris.
-
-
1 pull request merged.
-
Update OT token w3c/compute-pressure#248.
-
-
1 pull request received 1 new comment.
w3c/system-wake-lock
-
1 pull request opened.
-
Update w3c.json w3c/system-wake-lock#15, by @himorin.
-
-
1 pull request merged.
-
Update w3c.json w3c/system-wake-lock#15.
-
w3c/wake-lock
-
1 pull request opened.
-
Update w3c.json w3c/wake-lock#3, by @himorin.
-
-
1 pull request merged.
-
Update w3c.json w3c/wake-lock#3.
-
w3c/device-posture
-
1 pull request opened.
-
Update w3c.json w3c/device-posture#107, by @himorin.
-
-
1 pull request merged.
-
Update w3c.json w3c/device-posture#107.
-
-
1 pull request received 1 new comment.
-
w3c/device-posture#106 (1 comment by @w3cbot)
-
w3c/geolocation
-
1 pull request opened.
-
Update w3c.json w3c/geolocation#141, by @himorin.
-
-
1 pull request merged.
-
Update w3c.json w3c/geolocation#141.
-
w3c/gyroscope
-
3 pull requests opened.
-
editorial: Use "gyroscope virtual sensor type" dfn from DEVICE-ORIENTATION w3c/gyroscope#61, by @rakuco.
-
Update w3c.json w3c/gyroscope#60, by @himorin.
-
editorial: Use permissions and permissions-policy dfn's from DEVICE-ORIENTATION w3c/gyroscope#59, by @rakuco.
-
-
3 pull requests merged.
-
Update w3c.json w3c/gyroscope#60.
-
1 pull request received 2 new comments.
-
editorial: Use permissions and permissions-policy dfn's from DEVICE-ORIENTATION w3c/gyroscope#59 (2 comments by @anssiko, @rakuco)
-
w3c/accelerometer
-
3 pull requests opened.
-
editorial: Use some virtual sensor type dfns from DEVICE-ORIENTATION w3c/accelerometer#77, by @rakuco.
-
Update w3c.json w3c/accelerometer#76, by @himorin.
-
editorial: Use permissions and permissions-policy dfn's from DEVICE-ORIENTATION w3c/accelerometer#75, by @rakuco.
-
-
3 pull requests merged.
-
editorial: Use some virtual sensor type dfns from DEVICE-ORIENTATION w3c/accelerometer#77.
-
Update w3c.json w3c/accelerometer#76.
-
editorial: Use permissions and permissions-policy dfn's from DEVICE-ORIENTATION w3c/accelerometer#75.
-
w3c/battery
-
4 pull requests opened.
-
editorial: Fix ReSpec errors to make CI pass again w3c/battery#61, by @rakuco.
-
editorial: Adjust references in Permissions Policy section w3c/battery#60, by @rakuco.
-
editorial: Remove permissions policy-related note in getBattery() w3c/battery#59, by @rakuco.
-
Update w3c.json w3c/battery#58, by @himorin.
-
-
2 pull requests merged.
-
Update w3c.json w3c/battery#58.
-
editorial: Fix ReSpec errors to make CI pass again w3c/battery#61.
-
-
2 pull requests closed.
-
editorial: Adjust references in Permissions Policy section w3c/battery#60.
-
-
3 pull requests received 5 new comments.
-
editorial: Remove permissions policy-related note in getBattery() w3c/battery#59 (1 comment by @rakuco)
w3c/das-charter
-
1 pull request opened.
-
Update w3c.json w3c/das-charter#131, by @himorin.
-
-
1 pull request merged.
-
Update w3c.json w3c/das-charter#131.
-
w3c/das-wg
-
1 pull request opened.
-
Update w3c.json w3c/das-wg#68, by @himorin.
-
-
1 pull request merged.
-
Update w3c.json w3c/das-wg#68.
-
w3c/proximity
-
1 pull request opened.
-
Update w3c.json w3c/proximity#60, by @himorin.
-
-
1 pull request merged.
-
Update w3c.json w3c/proximity#60.
-
w3c/vibration
-
1 pull request opened.
-
Update w3c.json w3c/vibration#32, by @himorin.
-
-
1 pull request merged.
-
Update w3c.json w3c/vibration#32.
-
w3c/html-media-capture
-
1 pull request opened.
-
Update w3c.json w3c/html-media-capture#42, by @himorin.
-
-
1 pull request merged.
-
Update w3c.json w3c/html-media-capture#42.
-
w3c/magnetometer
-
1 pull request opened.
-
Update w3c.json w3c/magnetometer#72, by @himorin.
-
-
1 pull request merged.
-
Update w3c.json w3c/magnetometer#72.
-
w3c/motion-sensors
-
1 pull request opened.
-
Update w3c.json w3c/motion-sensors#34, by @himorin.
-
-
1 pull request merged.
-
Update w3c.json w3c/motion-sensors#34.
-
-
1 pull request received 2 new comments.