Devices and Sensors Working Group - Activity in 2017
No matches.
TR publications
-
2 documents published.
-
Wake Lock API published as a Candidate Recommendation Snapshot. History of Wake Lock API
-
Wake Lock API published as a Working Draft. History of Wake Lock API
-
GitHub
w3c/geolocation
-
1 issue opened.
-
Only allow to ask for location on user interaction w3c/geolocation#16, by @jimmywarting.
-
w3c/contact-picker
-
1 issue opened.
-
ContactAddress 'region' inconsistencies w3c/contact-picker#65, by @TSMatthews.
-
-
1 issue received 21 new comments.
-
ContactAddress 'region' inconsistencies w3c/contact-picker#65 (21 comments by @adrianba, @marcoscaceres, @oconnortmaster, @rsolomakhin, @sebsg, @TSMatthews)
-
w3c/sensors
-
3 issues opened.
-
Must not expose GC behavior to the web w3c/sensors#337, by @smaug----.
-
Replace smaug---- with his real name in Acknowledgements w3c/sensors#333, by @smaug----.
-
-
3 issues closed.
-
Must not expose GC behavior to the web w3c/sensors#337.
-
Replace smaug---- with his real name in Acknowledgements w3c/sensors#333.
-
-
3 issues received 6 new comments.
-
Investigate possibility of synchronizing coordinate systems w3c/sensors#257 (3 comments by @anssiko, @larsgk)
-
Replace smaug---- with his real name in Acknowledgements w3c/sensors#333 (2 comments by @alexshalamov, @smaug----)
-
-
4 pull requests opened.
-
Sensor must not expose GC behavior w3c/sensors#338, by @pozdnyakov.
-
Update CHANGELOG w3c/sensors#336, by @anssiko.
-
Corrections in the 'reporting frequency' definition w3c/sensors#335, by @pozdnyakov.
-
Replace smaug---- with his real name in Acknowledgements w3c/sensors#334, by @pozdnyakov.
-
-
4 pull requests merged.
-
Sensor must not expose GC behavior w3c/sensors#338.
-
Corrections in the 'reporting frequency' definition w3c/sensors#335.
-
Update CHANGELOG w3c/sensors#336.
-
Replace smaug---- with his real name in Acknowledgements w3c/sensors#334.
-
-
2 pull requests received 5 new comments.
-
Corrections in the 'reporting frequency' definition w3c/sensors#335 (4 comments by @alexshalamov, @pozdnyakov)
-
w3c/das-charter
-
1 issue closed.
-
Adopt Web Share API? w3c/das-charter#57.
-
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
Update Wake Lock API state to CR w3c/das-charter#60, by @anssiko.
-
Update end date of the 2016 charter w3c/das-charter#59, by @xfq.
-
-
2 pull requests merged.
-
Update Wake Lock API state to CR w3c/das-charter#60.
-
Update end date of the 2016 charter w3c/das-charter#59.
-
-
1 pull request closed.
-
Add Web Share API to Deliverables w3c/das-charter#58.
-
-
1 pull request received 14 new comments.
-
Add Web Share API to Deliverables w3c/das-charter#58 (14 comments by @anssiko, @marcoscaceres, @mgiuca, @ylafon)
-
w3c/das-wg
-
3 pull requests opened.
-
Update the draft statuses w3c/das-wg#10, by @xfq.
-
Update the roadmap w3c/das-wg#9, by @anssiko.
-
Fix the names in footer w3c/das-wg#8, by @xfq.
-
-
3 pull requests merged.
-
Update the draft statuses w3c/das-wg#10.
-
Update the roadmap w3c/das-wg#9.
-
Fix the names in footer w3c/das-wg#8.
-
-
2 pull requests received 3 new comments.
w3c/screen-wake-lock
-
2 pull requests opened.
-
Update README.md w3c/screen-wake-lock#123, by @xfq.
-
Update test links w3c/screen-wake-lock#122, by @Honry.
-
-
2 pull requests merged.
-
Update README.md w3c/screen-wake-lock#123.
-
Update test links w3c/screen-wake-lock#122.
-
-
1 pull request received 1 new comment.
w3c/deviceorientation
-
1 issue received 1 new comment.
-
Should the API be exposed only to secure context? w3c/deviceorientation#47 (1 comment by @maximilianmetti)
-
TR publications
-
4 documents published.
-
HTML Media Capture published as a Proposed Recommendation. History of HTML Media Capture
-
Wake Lock API published 3 times as a Working Draft. History of Wake Lock API
-
Participants
-
1 organization joined.
-
Bocoup joined.
-
GitHub
w3c/das-charter
-
1 issue opened.
-
Adopt Web Share API? w3c/das-charter#57, by @anssiko.
-
-
5 issues closed.
-
Define new end date w3c/das-charter#45.
-
Integrate Web Bluetooth? w3c/das-charter#28.
-
Integrate WebUSB w3c/das-charter#30.
-
Add milestone table w3c/das-charter#34.
-
Environmental sensors w3c/das-charter#33.
-
-
7 issues received 9 new comments.
-
4 pull requests opened.
-
Add Web Share API to Deliverables w3c/das-charter#58, by @anssiko.
-
Update HTML Media Capture state to PR w3c/das-charter#56, by @anssiko.
-
List changes in the table w3c/das-charter#55, by @xfq.
-
Add end date w3c/das-charter#54, by @xfq.
-
-
3 pull requests merged.
-
List changes in the table w3c/das-charter#55.
-
Update HTML Media Capture state to PR w3c/das-charter#56.
-
Add end date w3c/das-charter#54.
-
-
3 pull requests received 6 new comments.
w3c/deviceorientation
-
2 issues opened.
-
Should the API be exposed only to secure context? w3c/deviceorientation#47, by @alexshalamov.
-
Security and privacy section must be normative w3c/deviceorientation#46, by @alexshalamov.
-
-
1 issue closed.
-
Add [Exposed] to all interfaces w3c/deviceorientation#45.
-
-
2 pull requests opened.
-
Make security and privacy normative w3c/deviceorientation#49, by @alexshalamov.
-
Use [Exposed=Window] extended attribute w3c/deviceorientation#48, by @alexshalamov.
-
-
1 pull request merged.
-
Use [Exposed=Window] extended attribute w3c/deviceorientation#48.
-
-
2 pull requests received 5 new comments.
-
Make security and privacy normative w3c/deviceorientation#49 (3 comments by @alexshalamov, @anssiko, @dontcallmedom)
-
Use [Exposed=Window] extended attribute w3c/deviceorientation#48 (2 comments by @alexshalamov, @marcoscaceres)
-
w3c/sensors
-
3 issues opened.
-
Model should define multiple PermissionNames for fusion sensor types w3c/sensors#330, by @pozdnyakov.
-
Investigate possibility of exposing sensor data using shared buffer w3c/sensors#327, by @alexshalamov.
-
When to use the new GeolocationSensor API w3c/sensors#325, by @MeritBased.
-
-
4 issues closed.
-
Relation to Feature Policy w3c/sensors#133.
-
Model should define multiple PermissionNames for fusion sensor types w3c/sensors#330.
-
Editorial - 6.2 w3c/sensors#321.
-
When to use the new GeolocationSensor API w3c/sensors#325.
-
-
6 issues received 11 new comments.
-
Investigate possibility of exposing sensor data using shared buffer w3c/sensors#327 (2 comments by @anssiko)
-
4 pull requests opened.
-
Model allows multiple PermissionNames w3c/sensors#331, by @pozdnyakov.
-
Add a missing definit article w3c/sensors#329, by @pozdnyakov.
-
Add Feature Policy integration w3c/sensors#328, by @pozdnyakov.
-
Update Rick Waldron affiliation w3c/sensors#326, by @rwaldron.
-
-
3 pull requests merged.
-
Add Feature Policy integration w3c/sensors#328.
-
Model allows multiple PermissionNames w3c/sensors#331.
-
Add a missing definit article w3c/sensors#329.
-
-
3 pull requests received 27 new comments.
-
Add Feature Policy integration w3c/sensors#328 (22 comments by @alexshalamov, @anssiko, @Honry, @pozdnyakov)
-
w3c/geolocation
-
1 issue opened.
-
Consider adding Position.floorLevel w3c/geolocation#15, by @plehegar.
-
-
3 issues closed.
-
Add CONTRIBUTING file w3c/geolocation#5.
-
Multiple specs per repo is problematic. w3c/geolocation#7.
-
IDL is wrong w3c/geolocation#9.
-
-
3 issues received 4 new comments.
-
Disable geolocation by default in cross-origin iframes w3c/geolocation#10 (2 comments by @raymeskhoury, @robert-gogolan)
-
-
1 pull request closed.
-
First draft of use cases, simplified geofencing proposal. w3c/geolocation#1.
-
-
1 pull request received 1 new comment.
-
First draft of use cases, simplified geofencing proposal. w3c/geolocation#1 (1 comment by @plehegar)
-
w3c/screen-wake-lock
-
1 issue opened.
-
"SecurityError" DOMException w3c/screen-wake-lock#113, by @Honry.
-
-
4 issues closed.
-
Update security and privacy considerations w3c/screen-wake-lock#78.
-
Book reader usecase not well supported w3c/screen-wake-lock#56.
-
"SecurityError" DOMException w3c/screen-wake-lock#113.
-
new type: location? w3c/screen-wake-lock#98.
-
-
5 issues received 21 new comments.
-
[meta] web-platform-tests w3c/screen-wake-lock#111 (16 comments by @alexshalamov, @andrey-logvinov, @anssiko, @Honry, @marcoscaceres)
-
-
8 pull requests opened.
-
Add implementationReportURI w3c/screen-wake-lock#121, by @anssiko.
-
chore(.travis): simplify auto-pub script w3c/screen-wake-lock#120, by @marcoscaceres.
-
chore: add @Honry as QA Lead w3c/screen-wake-lock#119, by @marcoscaceres.
-
Add link to tests w3c/screen-wake-lock#118, by @Honry.
-
chore: use github config option instead. w3c/screen-wake-lock#117, by @marcoscaceres.
-
chore(.travis): use node lts (#115) w3c/screen-wake-lock#116, by @marcoscaceres.
-
chore(.travis): use node lts w3c/screen-wake-lock#115, by @marcoscaceres.
-
Navigator.getWakeLock() rejects with "SecurityError" w3c/screen-wake-lock#114, by @pozdnyakov.
-
-
6 pull requests merged.
-
Add implementationReportURI w3c/screen-wake-lock#121.
-
chore: add @Honry as QA Lead w3c/screen-wake-lock#119.
-
Add link to tests w3c/screen-wake-lock#118.
-
Navigator.getWakeLock() rejects with "SecurityError" w3c/screen-wake-lock#114.
-
chore(.travis): use node lts (#115) w3c/screen-wake-lock#116.
-
chore(.travis): use node lts w3c/screen-wake-lock#115.
-
-
2 pull requests closed.
-
chore(.travis): simplify auto-pub script w3c/screen-wake-lock#120.
-
chore: use github config option instead. w3c/screen-wake-lock#117.
-
-
5 pull requests received 16 new comments.
-
Navigator.getWakeLock() rejects with "SecurityError" w3c/screen-wake-lock#114 (8 comments by @anssiko, @Honry, @marcoscaceres, @pozdnyakov)
-
chore(.travis): simplify auto-pub script w3c/screen-wake-lock#120 (2 comments by @dontcallmedom, @marcoscaceres)
-
w3c/battery
-
1 issue opened.
-
Assess compatibility risk of using [SecureContext] w3c/battery#15, by @anssiko.
-
-
1 pull request received 1 new comment.
-
Allow use in same-origin children, add Feature Policy integration w3c/battery#13 (1 comment by @foolip)
-
w3c/html-media-capture
-
1 pull request opened.
-
Stage PR snapshot w3c/html-media-capture#21, by @anssiko.
-
-
1 pull request received 2 new comments.
TR publications
-
7 documents published.
-
Accelerometer published as a Working Draft. History of Accelerometer
-
Ambient Light Sensor published as a Working Draft. History of Ambient Light Sensor
-
Generic Sensor API published twice as a Working Draft. History of Generic Sensor API
-
Gyroscope published as a Working Draft. History of Gyroscope
-
Magnetometer published as a Working Draft. History of Magnetometer
-
Orientation Sensor published as a Working Draft. History of Orientation Sensor
-
Participants
-
1 participant left.
-
Maryam Mehrnezhad (W3C Invited Experts) left.
-
GitHub
w3c/html-media-capture
-
3 pull requests opened.
-
Overflow images for a better narrow layout w3c/html-media-capture#20, by @anssiko.
-
Editorial: split image to improve readability on narrow screens w3c/html-media-capture#19, by @anssiko.
-
Ask for tests for normative changes in CONTRIBUTING.md w3c/html-media-capture#18, by @rakuco.
-
-
3 pull requests merged.
-
Overflow images for a better narrow layout w3c/html-media-capture#20.
-
Editorial: split image to improve readability on narrow screens w3c/html-media-capture#19.
-
Ask for tests for normative changes in CONTRIBUTING.md w3c/html-media-capture#18.
-
-
2 pull requests received 5 new comments.
-
Overflow images for a better narrow layout w3c/html-media-capture#20 (3 comments by @anssiko, @dontcallmedom)
-
Ask for tests for normative changes in CONTRIBUTING.md w3c/html-media-capture#18 (2 comments by @anssiko)
-
w3c/vibration
-
3 pull requests opened.
-
Clarify CONTRIBUTING w3c/vibration#21, by @anssiko.
-
Ask for tests for normative changes in CONTRIBUTING.md w3c/vibration#20, by @foolip.
-
Fix ReSpec warnings w3c/vibration#19, by @anssiko.
-
-
3 pull requests merged.
-
Clarify CONTRIBUTING w3c/vibration#21.
-
Ask for tests for normative changes in CONTRIBUTING.md w3c/vibration#20.
-
Fix ReSpec warnings w3c/vibration#19.
-
-
2 pull requests received 12 new comments.
-
Ask for tests for normative changes in CONTRIBUTING.md w3c/vibration#20 (11 comments by @anssiko, @foolip, @gsnedders, @Honry)
-
w3c/screen-wake-lock
-
1 issue opened.
-
[meta] web-platform-tests w3c/screen-wake-lock#111, by @anssiko.
-
-
1 issue received 10 new comments.
-
[meta] web-platform-tests w3c/screen-wake-lock#111 (10 comments by @anssiko, @Honry, @marcoscaceres)
-
-
1 pull request opened.
-
Add testSuiteURI w3c/screen-wake-lock#112, by @anssiko.
-
-
1 pull request merged.
-
Add testSuiteURI w3c/screen-wake-lock#112.
-
-
1 pull request received 1 new comment.
w3c/sensors
-
8 issues opened.
-
Interface for user-involving calibration? w3c/sensors#324, by @martijnthe.
-
Generic Sensor & Wake Lock API use cases w3c/sensors#323, by @pozdnyakov.
-
Editorial - 6.2 w3c/sensors#321, by @edent.
-
TAG wide review (DRAFT) w3c/sensors#319, by @anssiko.
-
The explicit secure context check is not needed w3c/sensors#314, by @pozdnyakov.
-
Add [SecureContext] to derived interfaces w3c/sensors#313, by @anssiko.
-
[meta] Address remaining TAG review issues w3c/sensors#303, by @alexshalamov.
-
[meta] Wide review tracker w3c/sensors#299, by @anssiko.
-
-
6 issues closed.
-
TAG wide review (DRAFT) w3c/sensors#319.
-
The explicit secure context check is not needed w3c/sensors#314.
-
Add [SecureContext] to derived interfaces w3c/sensors#313.
-
[meta] Address remaining TAG review issues w3c/sensors#303.
-
Sensor.timeStamp could be clarified w3c/sensors#155.
-
Future proofing terminology w3c/sensors#294.
-
-
9 issues received 29 new comments.
-
Add [SecureContext] to derived interfaces w3c/sensors#313 (5 comments by @anssiko, @foolip, @pozdnyakov, @rakuco)
-
[meta] Address remaining TAG review issues w3c/sensors#303 (4 comments by @alexshalamov, @pozdnyakov)
-
Interface for user-involving calibration? w3c/sensors#324 (3 comments by @alexshalamov, @martijnthe)
-
Generic Sensor & Wake Lock API use cases w3c/sensors#323 (3 comments by @andrey-logvinov, @pozdnyakov)
-
20 pull requests opened.
-
Clarify CONTRIBUTING w3c/sensors#322, by @anssiko.
-
CHANGELOG fix w3c/sensors#320, by @anssiko.
-
Add CHANGELOG w3c/sensors#318, by @anssiko.
-
Make markup valid w3c/sensors#317, by @anssiko.
-
Adopt "test as you commit" policy w3c/sensors#316, by @anssiko.
-
Remove the extra secure context check w3c/sensors#315, by @pozdnyakov.
-
Fix Tobie's URL w3c/sensors#312, by @anssiko.
-
Remove an unnecessary note w3c/sensors#311, by @pozdnyakov.
-
Clarify Sensor states w3c/sensors#310, by @pozdnyakov.
-
Use the 'device sensor' term in the Scope section w3c/sensors#309, by @pozdnyakov.
-
Add content to "multiple-sensors" section w3c/sensors#308, by @alexshalamov.
-
Use `DOMException` instead of `Error` in `SensorErrorEvent` w3c/sensors#307, by @pozdnyakov.
-
Fix throw syntax in abstract operations w3c/sensors#306, by @pozdnyakov.
-
Use Permission API in code example w3c/sensors#305, by @alexshalamov.
-
Add a diagram illustrating the Model w3c/sensors#304, by @pozdnyakov.
-
Editorial changes w3c/sensors#302, by @pozdnyakov.
-
Increment Previous Version w3c/sensors#301, by @anssiko.
-
Rework the 'Connect to Sensor' abstract operation w3c/sensors#300, by @pozdnyakov.
-
Drop the inline issue which is already fixed w3c/sensors#298, by @pozdnyakov.
-
Fix Previous Version metadata w3c/sensors#297, by @anssiko.
-
-
23 pull requests merged.
-
Clarify CONTRIBUTING w3c/sensors#322.
-
CHANGELOG fix w3c/sensors#320.
-
Add CHANGELOG w3c/sensors#318.
-
Make markup valid w3c/sensors#317.
-
Remove the extra secure context check w3c/sensors#315.
-
Adopt "test as you commit" policy w3c/sensors#316.
-
Remove an unnecessary note w3c/sensors#311.
-
Use the 'device sensor' term in the Scope section w3c/sensors#309.
-
Clarify Sensor states w3c/sensors#310.
-
Add content to "multiple-sensors" section w3c/sensors#308.
-
Use Permission API in code example w3c/sensors#305.
-
Use `DOMException` instead of `Error` in `SensorErrorEvent` w3c/sensors#307.
-
Fix throw syntax in abstract operations w3c/sensors#306.
-
Add a diagram illustrating the Model w3c/sensors#304.
-
Editorial changes w3c/sensors#302.
-
Increment Previous Version w3c/sensors#301.
-
Rework the 'Connect to Sensor' abstract operation w3c/sensors#300.
-
Drop the inline issue which is already fixed w3c/sensors#298.
-
Fix Previous Version metadata w3c/sensors#297.
-
Add references to usecases note w3c/sensors#293.
-
Introduce the Reading Timestamp concept w3c/sensors#296.
-
-
2 pull requests closed.
-
Fix Tobie's URL w3c/sensors#312.
-
[DO NOT MERGE] Add preliminary interactive diagram. w3c/sensors#232.
-
-
17 pull requests received 46 new comments.
-
Add content to "multiple-sensors" section w3c/sensors#308 (10 comments by @alexshalamov, @anssiko, @pozdnyakov)
-
Rework the 'Connect to Sensor' abstract operation w3c/sensors#300 (5 comments by @alexshalamov, @anssiko, @pozdnyakov)
-
Use the 'device sensor' term in the Scope section w3c/sensors#309 (3 comments by @alexshalamov, @anssiko, @pozdnyakov)
-
Remove nullable member type from SensorOptions.frequency and fix warning w3c/sensors#292 (3 comments by @alexshalamov)
-
w3c/das-wg
-
2 pull requests opened.
-
Add Wake Lock w-p-t and wide review status update w3c/das-wg#7, by @anssiko.
-
Update WD dates w3c/das-wg#6, by @anssiko.
-
-
2 pull requests merged.
-
Add Wake Lock w-p-t and wide review status update w3c/das-wg#7.
-
Update WD dates w3c/das-wg#6.
-
-
2 pull requests received 2 new comments.
w3c/battery
-
1 pull request opened.
-
Adopt 'test as you commit' policy w3c/battery#14, by @anssiko.
-
-
1 pull request merged.
-
Adopt 'test as you commit' policy w3c/battery#14.
-
-
2 pull requests received 16 new comments.
-
Allow use in same-origin children, add Feature Policy integration w3c/battery#13 (14 comments by @anssiko, @clelland, @Honry, @mounirlamouri)
-
w3c/ambient-light
-
1 issue opened.
-
[meta] Address remaining TAG review issues w3c/ambient-light#43, by @alexshalamov.
-
-
1 issue closed.
-
[meta] Address remaining TAG review issues w3c/ambient-light#43.
-
-
1 issue received 1 new comment.
-
4 pull requests opened.
-
Ask for tests for normative changes in CONTRIBUTING.md w3c/ambient-light#47, by @rakuco.
-
The light-level media feature was deferred to Media Queries Level 5 w3c/ambient-light#46, by @anssiko.
-
Add SecureContext extended attribute w3c/ambient-light#45, by @alexshalamov.
-
Add more examples and use Permission API w3c/ambient-light#44, by @alexshalamov.
-
-
4 pull requests merged.
-
Ask for tests for normative changes in CONTRIBUTING.md w3c/ambient-light#47.
-
The light-level media feature was deferred to Media Queries Level 5 w3c/ambient-light#46.
-
Add more examples and use Permission API w3c/ambient-light#44.
-
Add SecureContext extended attribute w3c/ambient-light#45.
-
-
2 pull requests received 5 new comments.
-
Add more examples and use Permission API w3c/ambient-light#44 (4 comments by @alexshalamov, @anssiko)
-
w3c/magnetometer
-
5 issues closed.
-
Privacy implications? w3c/magnetometer#1.
-
Local coordinates could use further detail/examples w3c/magnetometer#19.
-
Provide API to access uncalibrated magnetometer values w3c/magnetometer#16.
-
Shouldn't need Web Service to compute declination w3c/magnetometer#18.
-
Should we expose heading? w3c/magnetometer#14.
-
-
5 issues received 10 new comments.
-
5 pull requests opened.
-
Ask for tests for normative changes in CONTRIBUTING.md w3c/magnetometer#38, by @rakuco.
-
Previous Version bump for WD publication w3c/magnetometer#37, by @anssiko.
-
Add 'mitigation strategies' dfn to metadata w3c/magnetometer#36, by @anssiko.
-
Add [SecureContext] w3c/magnetometer#35, by @anssiko.
-
Fix #1: Expand Security and Privacy Considerations w3c/magnetometer#34, by @anssiko.
-
-
5 pull requests merged.
-
Ask for tests for normative changes in CONTRIBUTING.md w3c/magnetometer#38.
-
Previous Version bump for WD publication w3c/magnetometer#37.
-
Add 'mitigation strategies' dfn to metadata w3c/magnetometer#36.
-
Add [SecureContext] w3c/magnetometer#35.
-
Fix #1: Expand Security and Privacy Considerations w3c/magnetometer#34.
-
w3c/gyroscope
-
3 pull requests opened.
-
Ask for tests for normative changes in CONTRIBUTING.md w3c/gyroscope#26, by @rakuco.
-
Previous Version bump for WD publication w3c/gyroscope#25, by @anssiko.
-
Add [SecureContext] w3c/gyroscope#24, by @pozdnyakov.
-
-
3 pull requests merged.
-
Ask for tests for normative changes in CONTRIBUTING.md w3c/gyroscope#26.
-
Previous Version bump for WD publication w3c/gyroscope#25.
-
Add [SecureContext] w3c/gyroscope#24.
-
w3c/orientation-sensor
-
2 issues closed.
-
Maybe too restrictive: with a size other than four w3c/orientation-sensor#7.
-
Find better references for [QUATERNIONS] and [QUATCONV] w3c/orientation-sensor#25.
-
-
2 issues received 2 new comments.
-
Find better references for [QUATERNIONS] and [QUATCONV] w3c/orientation-sensor#25 (1 comment by @anssiko)
-
5 pull requests opened.
-
Ask for tests for normative changes in CONTRIBUTING.md w3c/orientation-sensor#52, by @rakuco.
-
Previous Version bump for WD publication w3c/orientation-sensor#51, by @anssiko.
-
Add [SecureContext] w3c/orientation-sensor#50, by @pozdnyakov.
-
Add permissions check code examples w3c/orientation-sensor#49, by @pozdnyakov.
-
use secure links w3c/orientation-sensor#48, by @pozdnyakov.
-
-
5 pull requests merged.
-
Ask for tests for normative changes in CONTRIBUTING.md w3c/orientation-sensor#52.
-
Previous Version bump for WD publication w3c/orientation-sensor#51.
-
Add [SecureContext] w3c/orientation-sensor#50.
-
Add permissions check code examples w3c/orientation-sensor#49.
-
use secure links w3c/orientation-sensor#48.
-
-
1 pull request received 3 new comments.
w3c/accelerometer
-
3 pull requests opened.
-
Ask for tests for normative changes in CONTRIBUTING.md w3c/accelerometer#29, by @rakuco.
-
Previous Version bump for WD publication w3c/accelerometer#28, by @anssiko.
-
Add SecureContext extended attribute w3c/accelerometer#27, by @alexshalamov.
-
-
3 pull requests merged.
-
Ask for tests for normative changes in CONTRIBUTING.md w3c/accelerometer#29.
-
Previous Version bump for WD publication w3c/accelerometer#28.
-
Add SecureContext extended attribute w3c/accelerometer#27.
-
w3c/das-charter
-
1 issue opened.
-
Adopt "test as you commit" policy w3c/das-charter#48, by @anssiko.
-
-
2 issues closed.
-
Adopt "test as you commit" policy w3c/das-charter#48.
-
Adapt normative deliverable list to process 2017 requirements w3c/das-charter#35.
-
-
1 issue reopened.
-
Integrate Web Bluetooth? w3c/das-charter#28, by @anssiko.
-
-
2 issues received 12 new comments.
-
Adopt "test as you commit" policy w3c/das-charter#48 (9 comments by @anssiko, @dontcallmedom, @foolip)
-
-
7 pull requests opened.
-
Make end date a placeholder w3c/das-charter#53, by @anssiko.
-
Update WD dates w3c/das-charter#52, by @xfq.
-
Fix #48: Adopt 'test as you commit' policy w3c/das-charter#51, by @anssiko.
-
Adapt deliverable list to new Process requirements w3c/das-charter#50, by @xfq.
-
Update Geolocation Sensor link w3c/das-charter#49, by @anssiko.
-
Rename 'browser context' -> 'browsing context' w3c/das-charter#47, by @anssiko.
-
Update Vibration API reference to the latest w3c/das-charter#46, by @anssiko.
-
-
6 pull requests merged.
-
Make end date a placeholder w3c/das-charter#53.
-
Update WD dates w3c/das-charter#52.
-
Fix #48: Adopt 'test as you commit' policy w3c/das-charter#51.
-
Adapt deliverable list to new Process requirements w3c/das-charter#50.
-
Update Geolocation Sensor link w3c/das-charter#49.
-
Update Vibration API reference to the latest w3c/das-charter#46.
-
-
1 pull request closed.
-
Rename 'browser context' -> 'browsing context' w3c/das-charter#47.
-
-
3 pull requests received 6 new comments.
-
Adapt deliverable list to new Process requirements w3c/das-charter#50 (3 comments by @dontcallmedom, @xfq)
-
Rename 'browser context' -> 'browsing context' w3c/das-charter#47 (2 comments by @anssiko, @dontcallmedom)
-
w3c/proximity
-
1 pull request opened.
-
Add [SecureContext] w3c/proximity#28, by @anssiko.
-
-
1 pull request merged.
-
Add [SecureContext] w3c/proximity#28.
-
w3c/geolocation
-
1 pull request opened.
-
Add Feature Policy integration for the Geolocation API w3c/geolocation#14, by @raymeskhoury.
-
-
1 pull request received 3 new comments.
-
Add Feature Policy integration for the Geolocation API w3c/geolocation#14 (3 comments by @anssiko, @marcoscaceres, @raymeskhoury)
-
TR publications
-
2 documents published.
-
Wake Lock API published as a Working Draft. History of Wake Lock API
-
Media Capture from DOM Elements published as a Working Draft. History of Media Capture from DOM Elements
-
GitHub
w3c/sensors
-
6 issues opened.
-
Future proofing terminology w3c/sensors#294, by @tobie.
-
What's the rationale of moving security checks outside of normative requirements? w3c/sensors#287, by @tobie.
-
bikeshed link errors w3c/sensors#284, by @rwaldron.
-
Undefined values makes GS a pain to work with using TypeScript w3c/sensors#269, by @kenchris.
-
Review Security and Privacy questionnaire w3c/sensors#266, by @alexshalamov.
-
-
17 issues closed.
-
Addressing finger printing concerns for sensor APIs w3c/sensors#69.
-
Security/privacy concerns beyond fingerprinting -- data exfiltration w3c/sensors#182.
-
Should a "suspended" state be added w3c/sensors#223.
-
Missing browsing-context focus/unfocus hooks in HTML spec. w3c/sensors#222.
-
Define algorithm for suspending / resuming activated sensor objects w3c/sensors#227.
-
bikeshed link errors w3c/sensors#284.
-
Undefined values makes GS a pain to work with using TypeScript w3c/sensors#269.
-
Find a clearer name for the sensor concept w3c/sensors#162.
-
Security issues when used in combination with other APIs w3c/sensors#193.
-
granularity of Permission name for concrete/ fusion sensors w3c/sensors#132.
-
Review Security and Privacy questionnaire w3c/sensors#266.
-
Investigate using PWA installed status as indication of user intent w3c/sensors#211.
-
1 issue reopened.
-
Should a "suspended" state be added w3c/sensors#223, by @tobie.
-
-
17 issues received 73 new comments.
-
Undefined values makes GS a pain to work with using TypeScript w3c/sensors#269 (19 comments by @alexshalamov, @kenchris, @pozdnyakov, @rwaldron)
-
Investigate using PWA installed status as indication of user intent w3c/sensors#211 (11 comments by @alexshalamov, @anssiko, @pozdnyakov, @tobie)
-
Security issues when used in combination with other APIs w3c/sensors#193 (9 comments by @anssiko, @dontcallmedom, @lknik, @pozdnyakov)
-
What's the rationale of moving security checks outside of normative requirements? w3c/sensors#287 (8 comments by @alexshalamov, @danbri, @lknik, @pozdnyakov, @tobie)
-
Addressing finger printing concerns for sensor APIs w3c/sensors#69 (3 comments by @alexshalamov, @anssiko)
-
API must allow Web devs to easily create fused sensors in JS with an API consistant with native sensors w3c/sensors#42 (2 comments by @alexshalamov, @anssiko)
-
Security/privacy concerns beyond fingerprinting -- data exfiltration w3c/sensors#182 (2 comments by @alexshalamov, @anssiko)
-
Should the API allow setting both samplingFrequency and reportingFrequency? w3c/sensors#209 (1 comment by @pozdnyakov)
-
Take into account user gestures as an input for security policy enforcement w3c/sensors#196 (1 comment by @alexshalamov)
-
Split security-questionnaire.md into smaller chunks for each concrete sensor API and add Rick's comments w3c/sensors#281 (1 comment by @alexshalamov)
-
-
28 pull requests opened.
-
Introduce the Reading Timestamp concept w3c/sensors#296, by @pozdnyakov.
-
A better name and description for the Sensor.requestedReportingFrequency w3c/sensors#295, by @pozdnyakov.
-
Add references to usecases note w3c/sensors#293, by @alexshalamov.
-
Remove nullable member type from SensorOptions.frequency and fix warning w3c/sensors#292, by @alexshalamov.
-
Editorial fixes to Extensibility section w3c/sensors#291, by @anssiko.
-
Clarify sensor frequency concepts w3c/sensors#290, by @pozdnyakov.
-
Remove a leftover paragraph w3c/sensors#289, by @pozdnyakov.
-
Make 'Conditions to expose sensor readings' must w3c/sensors#288, by @pozdnyakov.
-
Remove duplicate Service Worker inline issue w3c/sensors#286, by @alexshalamov.
-
A small fix in 'Reading change threshold' description w3c/sensors#285, by @pozdnyakov.
-
Fix typo: treshold => threshold w3c/sensors#283, by @alexshalamov.
-
Split security & privacy questionnaire w3c/sensors#282, by @alexshalamov.
-
Introduce "condition to update latest reading" w3c/sensors#280, by @alexshalamov.
-
Introduce Default Sensor concept w3c/sensors#279, by @pozdnyakov.
-
Fix mistypes w3c/sensors#278, by @pozdnyakov.
-
Introduce a Reading Change Treshold concept w3c/sensors#277, by @pozdnyakov.
-
Fix #193: Define extension spec Security & Privacy expectations w3c/sensors#275, by @anssiko.
-
Define sensor.hasReading accessor bound to [[lastEventFiredAt]]. Fixes gh-269 w3c/sensors#274, by @rwaldron.
-
Redefine [=sensor=] concept w3c/sensors#273, by @pozdnyakov.
-
Fix Bikeshed custom header rendering bug w3c/sensors#272, by @anssiko.
-
Polyfill fix w3c/sensors#271, by @anssiko.
-
Answer Security and Privacy self review questionnaire w3c/sensors#270, by @alexshalamov.
-
Update geolocation.js polyfill w3c/sensors#268, by @anssiko.
-
Tie [=latest reading=] map to an origin w3c/sensors#267, by @pozdnyakov.
-
Add information to "Extending the Permission API" section w3c/sensors#265, by @alexshalamov.
-
Use [Exposed=Window] w3c/sensors#264, by @anssiko.
-
Annotate interface with [Exposed] extended attribute w3c/sensors#263, by @dontcallmedom.
-
-
23 pull requests merged.
-
Clarify sensor frequency concepts w3c/sensors#290.
-
Editorial fixes to Extensibility section w3c/sensors#291.
-
Remove a leftover paragraph w3c/sensors#289.
-
Make 'Conditions to expose sensor readings' must w3c/sensors#288.
-
Remove duplicate Service Worker inline issue w3c/sensors#286.
-
Introduce "condition to update latest reading" w3c/sensors#280.
-
A small fix in 'Reading change threshold' description w3c/sensors#285.
-
Introduce Default Sensor concept w3c/sensors#279.
-
Fix typo: treshold => threshold w3c/sensors#283.
-
Split security & privacy questionnaire w3c/sensors#282.
-
Introduce a Reading Change Treshold concept w3c/sensors#277.
-
Fix mistypes w3c/sensors#278.
-
Redefine [=sensor=] concept w3c/sensors#273.
-
Fix typos w3c/sensors#276.
-
Fix #193: Define extension spec Security & Privacy expectations w3c/sensors#275.
-
Add information to "Extending the Permission API" section w3c/sensors#265.
-
Answer Security and Privacy self review questionnaire w3c/sensors#270.
-
Fix Bikeshed custom header rendering bug w3c/sensors#272.
-
Polyfill fix w3c/sensors#271.
-
Tie [=latest reading=] map to an origin w3c/sensors#267.
-
Update geolocation.js polyfill w3c/sensors#268.
-
Use [Exposed=Window] w3c/sensors#264.
-
-
2 pull requests closed.
-
Add 'user triggered activation' as mitigation strategy w3c/sensors#207.
-
Annotate interface with [Exposed] extended attribute w3c/sensors#263.
-
-
19 pull requests received 136 new comments.
-
Add information to "Extending the Permission API" section w3c/sensors#265 (19 comments by @alexshalamov, @fivdi, @pozdnyakov, @rwaldron)
-
Introduce "condition to update latest reading" w3c/sensors#280 (17 comments by @alexshalamov, @anssiko, @pozdnyakov, @rwaldron)
-
Tie [=latest reading=] map to an origin w3c/sensors#267 (10 comments by @alexshalamov, @anssiko, @lknik, @pozdnyakov)
-
Clarify sensor frequency concepts w3c/sensors#290 (9 comments by @alexshalamov, @pozdnyakov, @rwaldron)
-
Make 'Conditions to expose sensor readings' must w3c/sensors#288 (9 comments by @alexshalamov, @anssiko, @pozdnyakov, @tobie)
-
Introduce Default Sensor concept w3c/sensors#279 (9 comments by @alexshalamov, @anssiko, @pozdnyakov)
-
Answer Security and Privacy self review questionnaire w3c/sensors#270 (9 comments by @alexshalamov, @dontcallmedom, @pozdnyakov, @rwaldron)
-
Define sensor.hasReading accessor bound to [[lastEventFiredAt]]. Fixes gh-269 w3c/sensors#274 (7 comments by @anssiko, @pozdnyakov, @rwaldron)
-
Update geolocation.js polyfill w3c/sensors#268 (6 comments by @alexshalamov, @anssiko, @kenchris, @rwaldron)
-
Split security & privacy questionnaire w3c/sensors#282 (3 comments by @alexshalamov, @anssiko, @pozdnyakov)
-
Introduce a Reading Change Treshold concept w3c/sensors#277 (3 comments by @alexshalamov, @anssiko, @pozdnyakov)
-
Fix #193: Define extension spec Security & Privacy expectations w3c/sensors#275 (3 comments by @anssiko, @dontcallmedom)
-
w3c/das-charter
-
5 issues opened.
-
Define new end date w3c/das-charter#45, by @anssiko.
-
"Device and Sensors" or "Devices and Sensors" w3c/das-charter#41, by @anssiko.
-
Network Information API w3c/das-charter#40, by @anssiko.
-
Adapt normative deliverable list to process 2017 requirements w3c/das-charter#35, by @dontcallmedom.
-
Add milestone table w3c/das-charter#34, by @samuelweiler.
-
-
5 issues closed.
-
Network Information API w3c/das-charter#40.
-
"Device and Sensors" or "Devices and Sensors" w3c/das-charter#41.
-
Stop joint work on media capture task force w3c/das-charter#27.
-
Generic-sensor based geolocation API? w3c/das-charter#32.
-
Restart work on DeviceOrientation Event API w3c/das-charter#31.
-
-
5 issues received 8 new comments.
-
Adapt normative deliverable list to process 2017 requirements w3c/das-charter#35 (1 comment by @dontcallmedom)
-
7 pull requests opened.
-
Fix #40: Note Network Information API WICG Draft Report w3c/das-charter#44, by @anssiko.
-
Fix #41: Rename group to 'Devices and Sensors Working Group' w3c/das-charter#43, by @anssiko.
-
More editorial w3c/das-charter#42, by @anssiko.
-
Editorial pass w3c/das-charter#39, by @anssiko.
-
Remove Media Capture Task Force deliverables w3c/das-charter#38, by @dontcallmedom.
-
Add finishing of DeviceOrientation as normative deliverable w3c/das-charter#37, by @dontcallmedom.
-
Add a gelocation sensor deliverable w3c/das-charter#36, by @dontcallmedom.
-
-
7 pull requests merged.
-
Fix #40: Note Network Information API WICG Draft Report w3c/das-charter#44.
-
Fix #41: Rename group to 'Devices and Sensors Working Group' w3c/das-charter#43.
-
More editorial w3c/das-charter#42.
-
Editorial pass w3c/das-charter#39.
-
Remove Media Capture Task Force deliverables w3c/das-charter#38.
-
Add a gelocation sensor deliverable w3c/das-charter#36.
-
Add finishing of DeviceOrientation as normative deliverable w3c/das-charter#37.
-
-
5 pull requests received 13 new comments.
-
Fix #40: Note Network Information API WICG Draft Report w3c/das-charter#44 (2 comments by @anssiko, @dontcallmedom)
-
Add finishing of DeviceOrientation as normative deliverable w3c/das-charter#37 (1 comment by @anssiko)
w3c/accelerometer
-
1 issue opened.
-
Why unrestricted double for acceleration readings? w3c/accelerometer#23, by @dontcallmedom.
-
-
2 issues closed.
-
Add use cases to spec w3c/accelerometer#18.
-
Why unrestricted double for acceleration readings? w3c/accelerometer#23.
-
-
1 issue received 3 new comments.
-
Why unrestricted double for acceleration readings? w3c/accelerometer#23 (3 comments by @alexshalamov, @pozdnyakov)
-
-
4 pull requests opened.
-
Add security-questionnaire.md for Accelerometer sensor w3c/accelerometer#26, by @alexshalamov.
-
Use value getter operation and fix attribute types w3c/accelerometer#25, by @alexshalamov.
-
Define Accelerometer sensor type, clarify latest reading w3c/accelerometer#24, by @anssiko.
-
Use [Exposed=Window] w3c/accelerometer#22, by @anssiko.
-
-
4 pull requests merged.
-
Use value getter operation and fix attribute types w3c/accelerometer#25.
-
Add security-questionnaire.md for Accelerometer sensor w3c/accelerometer#26.
-
Define Accelerometer sensor type, clarify latest reading w3c/accelerometer#24.
-
Use [Exposed=Window] w3c/accelerometer#22.
-
-
1 pull request received 3 new comments.
-
Use value getter operation and fix attribute types w3c/accelerometer#25 (3 comments by @alexshalamov, @anssiko)
-
w3c/magnetometer
-
4 pull requests opened.
-
Use value getter operation and use double as attribute type w3c/magnetometer#33, by @alexshalamov.
-
Add security and privacy questionnaire for Magnetometer w3c/magnetometer#32, by @alexshalamov.
-
Define Magnetometer sensor type, clarify latest reading w3c/magnetometer#31, by @anssiko.
-
Use [Exposed=Window] w3c/magnetometer#30, by @anssiko.
-
-
4 pull requests merged.
-
Use value getter operation and use double as attribute type w3c/magnetometer#33.
-
Add security and privacy questionnaire for Magnetometer w3c/magnetometer#32.
-
Define Magnetometer sensor type, clarify latest reading w3c/magnetometer#31.
-
Use [Exposed=Window] w3c/magnetometer#30.
-
-
2 pull requests received 4 new comments.
-
Add security and privacy questionnaire for Magnetometer w3c/magnetometer#32 (3 comments by @alexshalamov)
-
Use value getter operation and use double as attribute type w3c/magnetometer#33 (1 comment by @alexshalamov)
-
w3c/ambient-light
-
1 issue closed.
-
Exfiltrating data across origins w3c/ambient-light#37.
-
-
4 pull requests opened.
-
Use value getter operation and fix illuminance attribute type w3c/ambient-light#42, by @alexshalamov.
-
Add security and privacy questionnaire for Ambient Light Sensor w3c/ambient-light#41, by @alexshalamov.
-
Define 'Ambient Light Sensor' sensor type w3c/ambient-light#40, by @anssiko.
-
Use [Exposed=Window] w3c/ambient-light#39, by @anssiko.
-
-
5 pull requests merged.
-
Use value getter operation and fix illuminance attribute type w3c/ambient-light#42.
-
Add security and privacy questionnaire for Ambient Light Sensor w3c/ambient-light#41.
-
Define 'Ambient Light Sensor' sensor type w3c/ambient-light#40.
-
Use [Exposed=Window] w3c/ambient-light#39.
-
Fix #37: Add cross-origin leaks, hijacking browsing history w3c/ambient-light#38.
-
-
3 pull requests received 5 new comments.
-
Define 'Ambient Light Sensor' sensor type w3c/ambient-light#40 (2 comments by @anssiko, @pozdnyakov)
-
Fix #37: Add cross-origin leaks, hijacking browsing history w3c/ambient-light#38 (2 comments by @anssiko, @lknik)
-
Use value getter operation and fix illuminance attribute type w3c/ambient-light#42 (1 comment by @anssiko)
-
w3c/proximity
-
5 pull requests opened.
-
Use getter operation for latest reading w3c/proximity#27, by @alexshalamov.
-
Align with Generic Sensor API current state w3c/proximity#26, by @NOtherDev.
-
Add security and privacy questionnaire for Proximity sensor w3c/proximity#25, by @alexshalamov.
-
Define 'Proximity Sensor' sensor type, clarify latest reading w3c/proximity#24, by @anssiko.
-
Use [Exposed=Window] w3c/proximity#23, by @anssiko.
-
-
5 pull requests merged.
-
Add security and privacy questionnaire for Proximity sensor w3c/proximity#25.
-
Use getter operation for latest reading w3c/proximity#27.
-
Align with Generic Sensor API current state w3c/proximity#26.
-
Define 'Proximity Sensor' sensor type, clarify latest reading w3c/proximity#24.
-
Use [Exposed=Window] w3c/proximity#23.
-
-
1 pull request received 1 new comment.
w3c/orientation-sensor
-
1 issue opened.
-
Should OrientationSensor interface provide Euler angles? w3c/orientation-sensor#43, by @alexshalamov.
-
-
1 issue received 1 new comment.
-
Should OrientationSensor interface provide Euler angles? w3c/orientation-sensor#43 (1 comment by @anssiko)
-
-
4 pull requests opened.
-
Add security and privacy questionnaire for Orientation Sensor w3c/orientation-sensor#47, by @alexshalamov.
-
Define Orientation Sensor sensor type, clarify latest reading w3c/orientation-sensor#46, by @anssiko.
-
Update attributes description w3c/orientation-sensor#45, by @pozdnyakov.
-
Use [Exposed=Window] w3c/orientation-sensor#44, by @anssiko.
-
-
4 pull requests merged.
-
Add security and privacy questionnaire for Orientation Sensor w3c/orientation-sensor#47.
-
Define Orientation Sensor sensor type, clarify latest reading w3c/orientation-sensor#46.
-
Update attributes description w3c/orientation-sensor#45.
-
Use [Exposed=Window] w3c/orientation-sensor#44.
-
-
2 pull requests received 3 new comments.
-
Define Orientation Sensor sensor type, clarify latest reading w3c/orientation-sensor#46 (2 comments by @anssiko, @kenchris)
-
w3c/gyroscope
-
5 pull requests opened.
-
Add security and privacy questionnaire for Gyroscope sensor w3c/gyroscope#23, by @alexshalamov.
-
Update attributes description w3c/gyroscope#22, by @pozdnyakov.
-
Define Gyroscope sensor type, clarify latest reading w3c/gyroscope#21, by @anssiko.
-
Define Gyroscope sensor type, clarify latest reading w3c/gyroscope#20, by @anssiko.
-
Use [Exposed=Window] w3c/gyroscope#19, by @anssiko.
-
-
4 pull requests merged.
-
Add security and privacy questionnaire for Gyroscope sensor w3c/gyroscope#23.
-
Update attributes description w3c/gyroscope#22.
-
Define Gyroscope sensor type, clarify latest reading w3c/gyroscope#21.
-
Use [Exposed=Window] w3c/gyroscope#19.
-
-
1 pull request closed.
-
Define Gyroscope sensor type, clarify latest reading w3c/gyroscope#20.
-
-
1 pull request received 1 new comment.
w3c/battery
-
1 pull request received 11 new comments.
-
Allow use in same-origin children, add Feature Policy integration w3c/battery#13 (11 comments by @anssiko, @clelland, @dontcallmedom, @mounirlamouri, @RByers)
-
w3c/das-wg
-
2 pull requests opened.
-
Update the time for subsequent calls w3c/das-wg#5, by @xfq.
-
Remove Media Capture Task Force w3c/das-wg#4, by @xfq.
-
-
2 pull requests merged.
-
Remove Media Capture Task Force w3c/das-wg#4.
-
Update the time for subsequent calls w3c/das-wg#5.
-
w3c/deviceorientation
-
1 issue opened.
-
Add [Exposed] to all interfaces w3c/deviceorientation#45, by @annevk.
-
w3c/screen-wake-lock
-
1 pull request opened.
-
Annotate interfaces with [Exposed] extended attribute w3c/screen-wake-lock#110, by @dontcallmedom.
-
-
1 pull request merged.
-
Annotate interfaces with [Exposed] extended attribute w3c/screen-wake-lock#110.
-
TR publications
-
10 documents published.
-
HTML Media Capture published as a Candidate Recommendation Snapshot. History of HTML Media Capture
-
Wake Lock API published as a Working Draft. History of Wake Lock API
-
Accelerometer published as a Working Draft. History of Accelerometer
-
Ambient Light Sensor published as a Working Draft. History of Ambient Light Sensor
-
Gyroscope published as a Working Draft. History of Gyroscope
-
Magnetometer published as a Working Draft. History of Magnetometer
-
Orientation Sensor published as a Working Draft. History of Orientation Sensor
-
Generic Sensor API published as a Working Draft. History of Generic Sensor API
-
Motion Sensors Explainer published twice as a Note. History of Motion Sensors Explainer
-
Participants
-
1 organization left.
-
360 left.
-
GitHub
w3c/ambient-light
-
1 issue opened.
-
Exfiltrating data across origins w3c/ambient-light#37, by @lknik.
-
-
6 issues closed.
-
Add description for use cases w3c/ambient-light#23.
-
Light-level deferred to Media Queries Level 5 w3c/ambient-light#12.
-
Security and Privacy considerations for ALS w3c/ambient-light#13.
-
Security and privacy considerations for Ambient Light Events w3c/ambient-light#8.
-
Available in workers? w3c/ambient-light#16.
-
What illuminance value should be reported for stopped sensor? w3c/ambient-light#15.
-
-
2 issues reopened.
-
Add description for use cases w3c/ambient-light#23, by @tobie.
-
Add description for use cases w3c/ambient-light#23, by @tobie.
-
-
8 issues received 25 new comments.
-
Ambient Light Sensors to detect RGB colors w3c/ambient-light#9 (2 comments by @alexshalamov, @anssiko)
-
Security and privacy considerations for Ambient Light Events w3c/ambient-light#8 (1 comment by @anssiko)
-
What illuminance value should be reported for stopped sensor? w3c/ambient-light#15 (1 comment by @alexshalamov)
-
7 pull requests opened.
-
Fix #37: Add cross-origin leaks, hijacking browsing history w3c/ambient-light#38, by @anssiko.
-
Fix #23: Move content from Use Cases to Scope w3c/ambient-light#36, by @anssiko.
-
Improve use cases section w3c/ambient-light#35, by @alexshalamov.
-
Fix #23: Clarify use cases further w3c/ambient-light#34, by @anssiko.
-
Fix #13: Expand Security and Privacy Considerations w3c/ambient-light#33, by @anssiko.
-
Fix links to sensor and sensorreading w3c/ambient-light#32, by @xfq.
-
The spec does not use levels w3c/ambient-light#31, by @xfq.
-
-
6 pull requests merged.
-
Fix #23: Move content from Use Cases to Scope w3c/ambient-light#36.
-
Fix #23: Clarify use cases further w3c/ambient-light#34.
-
Improve use cases section w3c/ambient-light#35.
-
Fix #13: Expand Security and Privacy Considerations w3c/ambient-light#33.
-
Fix links to sensor and sensorreading w3c/ambient-light#32.
-
The spec does not use levels w3c/ambient-light#31.
-
-
4 pull requests received 24 new comments.
-
Fix #13: Expand Security and Privacy Considerations w3c/ambient-light#33 (15 comments by @alexshalamov, @anssiko, @lknik)
-
Fix #37: Add cross-origin leaks, hijacking browsing history w3c/ambient-light#38 (5 comments by @alexshalamov, @anssiko, @lknik)
-
w3c/html-media-capture
-
1 issue closed.
-
[meta] Publish a revised Candidate Recommendation w3c/html-media-capture#14.
-
-
1 issue received 14 new comments.
-
[meta] Publish a revised Candidate Recommendation w3c/html-media-capture#14 (14 comments by @anssiko, @dontcallmedom)
-
-
3 pull requests opened.
-
Fix references w3c/html-media-capture#17, by @anssiko.
-
Fix references for CR publication w3c/html-media-capture#16, by @dontcallmedom.
-
Add CR4 snapshot w3c/html-media-capture#15, by @anssiko.
-
-
2 pull requests merged.
-
Fix references w3c/html-media-capture#17.
-
Add CR4 snapshot w3c/html-media-capture#15.
-
-
1 pull request closed.
-
Fix references for CR publication w3c/html-media-capture#16.
-
-
2 pull requests received 3 new comments.
w3c/battery
-
1 issue received 2 new comments.
-
Allow use from within secure context and top-level browsing context only w3c/battery#10 (2 comments by @anssiko, @clelland)
-
-
1 pull request opened.
-
Allow use in same-origin children, add Feature Policy integration w3c/battery#13, by @anssiko.
-
w3c/motion-sensors
-
1 issue opened.
-
Echidna unable to publish Note updates? w3c/motion-sensors#28, by @anssiko.
-
-
1 issue closed.
-
Echidna unable to publish Note updates? w3c/motion-sensors#28.
-
-
1 issue reopened.
-
Echidna unable to publish Note updates? w3c/motion-sensors#28, by @anssiko.
-
-
1 issue received 23 new comments.
-
Echidna unable to publish Note updates? w3c/motion-sensors#28 (23 comments by @alexshalamov, @anssiko, @dontcallmedom, @tripu, @xfq)
-
-
5 pull requests opened.
-
Fix validation errors that block publication, part 2 w3c/motion-sensors#27, by @anssiko.
-
Fix validation errors that block publication w3c/motion-sensors#26, by @anssiko.
-
Add Previous Version metadata w3c/motion-sensors#25, by @anssiko.
-
Add more use-cases w3c/motion-sensors#24, by @alexshalamov.
-
The spec does not use levels w3c/motion-sensors#23, by @xfq.
-
-
5 pull requests merged.
-
Fix validation errors that block publication, part 2 w3c/motion-sensors#27.
-
Fix validation errors that block publication w3c/motion-sensors#26.
-
Add Previous Version metadata w3c/motion-sensors#25.
-
Add more use-cases w3c/motion-sensors#24.
-
The spec does not use levels w3c/motion-sensors#23.
-
-
2 pull requests received 3 new comments.
w3c/sensors
-
3 issues opened.
-
Align sensor lifecycle diagram with normative prose w3c/sensors#261, by @anssiko.
-
Investigate possibility of synchronizing coordinate systems w3c/sensors#257, by @alexshalamov.
-
Stop using "incumbent settings object"? w3c/sensors#253, by @xfq.
-
-
6 issues closed.
-
Align sensor lifecycle diagram with normative prose w3c/sensors#261.
-
w3c.github.io/sensors/usecases.html 404s w3c/sensors#181.
-
Listing threats w3c/sensors#192.
-
Stop using "incumbent settings object"? w3c/sensors#253.
-
What are the event.type strings? w3c/sensors#245.
-
-
3 issues received 6 new comments.
-
Align sensor lifecycle diagram with normative prose w3c/sensors#261 (2 comments by @anssiko, @pozdnyakov)
-
Investigate possibility of synchronizing coordinate systems w3c/sensors#257 (2 comments by @anssiko)
-
-
11 pull requests opened.
-
Fix #261: Rename Error -> onerror in state diagram w3c/sensors#262, by @anssiko.
-
Fix a couple of algorithms with their use of variables w3c/sensors#260, by @dontcallmedom.
-
Use proper reference in [HTML] for task queue w3c/sensors#259, by @dontcallmedom.
-
Fix #253: Stop using incumbent settings object w3c/sensors#258, by @anssiko.
-
Initial improvements for use cases document w3c/sensors#256, by @alexshalamov.
-
Add categorization of security and privacy threats w3c/sensors#255, by @pozdnyakov.
-
Do not use the -ing form for consistency w3c/sensors#254, by @anssiko.
-
Refer to the latest [FEATURE-POLICY] spec w3c/sensors#252, by @anssiko.
-
Fix 'steps to determine the visibility state' dfn link w3c/sensors#251, by @anssiko.
-
Fix a broken link to HTML w3c/sensors#250, by @xfq.
-
Add `Level: none` to the metadata block w3c/sensors#249, by @xfq.
-
-
13 pull requests merged.
-
Fix #261: Rename Error -> onerror in state diagram w3c/sensors#262.
-
Fix a couple of algorithms with their use of variables w3c/sensors#260.
-
Initial improvements for use cases document w3c/sensors#256.
-
Use proper reference in [HTML] for task queue w3c/sensors#259.
-
Add categorization of security and privacy threats w3c/sensors#255.
-
Fix #253: Stop using incumbent settings object w3c/sensors#258.
-
Do not use the -ing form for consistency w3c/sensors#254.
-
Refer to the latest [FEATURE-POLICY] spec w3c/sensors#252.
-
Fix 'steps to determine the visibility state' dfn link w3c/sensors#251.
-
Fix a broken link to HTML w3c/sensors#250.
-
Add `Level: none` to the metadata block w3c/sensors#249.
-
Modify example to use addEventListener and change table style w3c/sensors#247.
-
Be explicit about steps taken when a Sensor instance is GCed w3c/sensors#248.
-
-
9 pull requests received 69 new comments.
-
Add categorization of security and privacy threats w3c/sensors#255 (22 comments by @alexshalamov, @anssiko, @pozdnyakov)
-
Initial improvements for use cases document w3c/sensors#256 (20 comments by @alexshalamov, @anssiko, @pozdnyakov)
-
Add `Level: none` to the metadata block w3c/sensors#249 (9 comments by @anssiko, @dontcallmedom, @xfq)
-
Modify example to use addEventListener and change table style w3c/sensors#247 (8 comments by @alexshalamov, @rwaldron)
-
Fix a couple of algorithms with their use of variables w3c/sensors#260 (4 comments by @anssiko, @dontcallmedom, @pozdnyakov)
-
Fix #261: Rename Error -> onerror in state diagram w3c/sensors#262 (2 comments by @anssiko, @rwaldron)
-
w3c/deviceorientation
-
1 issue opened.
-
devicemotion: rotationRate is not implemented according to specification w3c/deviceorientation#44, by @juncaidf.
-
-
1 issue received 1 new comment.
-
devicemotion: rotationRate is not implemented according to specification w3c/deviceorientation#44 (1 comment by @reillyeon)
-
-
1 pull request opened.
-
update rotationRate alpha, beta, gamma description to be the same as implementation w3c/deviceorientation#43, by @juncaidf.
-
w3c/screen-wake-lock
-
1 issue closed.
-
Restrict Wake Lock to secure context w3c/screen-wake-lock#100.
-
-
2 issues received 2 new comments.
-
1 pull request merged.
-
Restrict Wake Lock API to secure context w3c/screen-wake-lock#109.
-
-
1 pull request closed.
-
require a secure context for wakelock w3c/screen-wake-lock#104.
-
-
2 pull requests received 4 new comments.
-
Restrict Wake Lock API to secure context w3c/screen-wake-lock#109 (3 comments by @andrey-logvinov, @dontcallmedom)
-
w3c/accelerometer
-
1 issue closed.
-
Address DeviceOrientation issue #4 w3c/accelerometer#7.
-
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
Add Previous Version metadata w3c/accelerometer#21, by @anssiko.
-
The spec does not use levels w3c/accelerometer#20, by @xfq.
-
-
2 pull requests merged.
-
Add Previous Version metadata w3c/accelerometer#21.
-
The spec does not use levels w3c/accelerometer#20.
-
-
1 pull request received 2 new comments.
w3c/gyroscope
-
1 issue opened.
-
Define coordinate system w3c/gyroscope#17, by @anssiko.
-
-
2 issues closed.
-
Address DeviceOrientation issue number 4 w3c/gyroscope#6.
-
Define coordinate system w3c/gyroscope#17.
-
-
1 issue received 1 new comment.
-
3 pull requests opened.
-
Fix #17: Define local coordinate system w3c/gyroscope#18, by @anssiko.
-
Add Previous Version metadata w3c/gyroscope#16, by @anssiko.
-
The spec does not use levels w3c/gyroscope#15, by @xfq.
-
-
3 pull requests merged.
-
Fix #17: Define local coordinate system w3c/gyroscope#18.
-
Add Previous Version metadata w3c/gyroscope#16.
-
The spec does not use levels w3c/gyroscope#15.
-
-
2 pull requests received 3 new comments.
w3c/das-charter
-
1 issue received 1 new comment.
w3c/das-wg
-
2 pull requests opened.
-
Update WD publication dates w3c/das-wg#3, by @anssiko.
-
Rename Last Call Working Draft w3c/das-wg#2, by @xfq.
-
-
2 pull requests merged.
-
Update WD publication dates w3c/das-wg#3.
-
Rename Last Call Working Draft w3c/das-wg#2.
-
-
1 pull request received 3 new comments.
w3c/magnetometer
-
1 pull request opened.
-
Add Previous Version metadata w3c/magnetometer#29, by @anssiko.
-
-
1 pull request merged.
-
Add Previous Version metadata w3c/magnetometer#29.
-
w3c/orientation-sensor
-
2 pull requests opened.
-
Add Previous Version metadata w3c/orientation-sensor#42, by @anssiko.
-
The spec does not use levels w3c/orientation-sensor#41, by @xfq.
-
-
2 pull requests merged.
-
Add Previous Version metadata w3c/orientation-sensor#42.
-
The spec does not use levels w3c/orientation-sensor#41.
-
w3c/proximity
-
1 pull request opened.
-
The spec does not use levels w3c/proximity#22, by @xfq.
-
-
1 pull request merged.
-
The spec does not use levels w3c/proximity#22.
-
-
1 pull request received 1 new comment.
w3c/contact-picker
-
1 issue received 5 new comments.
-
Add payerGivenName + payerFamilyName to PaymentAddress w3c/contact-picker#69 (5 comments by @ianbjacobs, @marcoscaceres, @r12a)
-
TR publications
-
3 documents published.
-
Wake Lock API published 3 times as a Working Draft. History of Wake Lock API
-
Participants
-
1 participant joined.
-
Fuqiao Xue (W3C) joined.
-
GitHub
w3c/screen-wake-lock
-
5 issues closed.
-
Disable Wake Lock in sandboxed frames w3c/screen-wake-lock#99.
-
Consider restricting Wake Lock API to Secure Contexts w3c/screen-wake-lock#82.
-
iframes keeping screen awake w3c/screen-wake-lock#51.
-
Spec needs to be explicit about resetting release timer on lock release w3c/screen-wake-lock#57.
-
Specify that platform-specific inactivity timer should be reset after the lock is released w3c/screen-wake-lock#101.
-
-
1 issue reopened.
-
Disable Wake Lock in sandboxed frames w3c/screen-wake-lock#99, by @marcoscaceres.
-
-
4 issues received 9 new comments.
-
Disable Wake Lock in sandboxed frames w3c/screen-wake-lock#99 (6 comments by @andrey-logvinov, @marcoscaceres)
-
Consider restricting Wake Lock API to Secure Contexts w3c/screen-wake-lock#82 (1 comment by @andrey-logvinov)
-
Spec needs to be explicit about resetting release timer on lock release w3c/screen-wake-lock#57 (1 comment by @andrey-logvinov)
-
-
4 pull requests opened.
-
Restrict Wake Lock API to secure context w3c/screen-wake-lock#109, by @andrey-logvinov.
-
Replace browser context with document w3c/screen-wake-lock#108, by @andrey-logvinov.
-
Add feature policy w3c/screen-wake-lock#107, by @andrey-logvinov.
-
Reset inactivity timer on screen wake lock release w3c/screen-wake-lock#106, by @andrey-logvinov.
-
-
3 pull requests merged.
-
Replace browser context with document w3c/screen-wake-lock#108.
-
Add feature policy w3c/screen-wake-lock#107.
-
Reset inactivity timer on screen wake lock release w3c/screen-wake-lock#106.
-
-
3 pull requests received 8 new comments.
-
Replace browser context with document w3c/screen-wake-lock#108 (3 comments by @andrey-logvinov, @marcoscaceres)
w3c/sensors
-
2 issues opened.
-
Should a Sensor instance be deactivated/stopped when being garbage collected? w3c/sensors#246, by @martijnthe.
-
What are the event.type strings? w3c/sensors#245, by @martijnthe.
-
-
6 issues closed.
-
Reporting mode and polling frequency w3c/sensors#126.
-
Sensor object can stuck in `activating` state w3c/sensors#203.
-
The Update latest reading abstract operation is never invoked w3c/sensors#204.
-
Define tasks for state changes w3c/sensors#218.
-
The internal slots are not reset w3c/sensors#243.
-
-
3 issues received 6 new comments.
-
What are the event.type strings? w3c/sensors#245 (4 comments by @alexshalamov, @jiangzidong, @rwaldron)
-
Should a Sensor instance be deactivated/stopped when being garbage collected? w3c/sensors#246 (1 comment by @pozdnyakov)
-
Define algorithm for suspending / resuming activated sensor objects w3c/sensors#227 (1 comment by @tobie)
-
-
3 pull requests opened.
-
Be explicit about steps taken when a Sensor instance is GCed w3c/sensors#248, by @pozdnyakov.
-
Modify example to use addEventListener and change table style w3c/sensors#247, by @alexshalamov.
-
Move initial reading notification into 'notify activated state' w3c/sensors#244, by @pozdnyakov.
-
-
2 pull requests merged.
-
Move initial reading notification into 'notify activated state' w3c/sensors#244.
-
Rewrite Abstract Operations w3c/sensors#197.
-
-
4 pull requests received 7 new comments.
-
Be explicit about steps taken when a Sensor instance is GCed w3c/sensors#248 (2 comments by @alexshalamov, @pozdnyakov)
-
Modify example to use addEventListener and change table style w3c/sensors#247 (2 comments by @alexshalamov, @rwaldron)
-
Move initial reading notification into 'notify activated state' w3c/sensors#244 (2 comments by @alexshalamov, @rwaldron)
-
w3c/contact-picker
-
1 issue received 4 new comments.
-
Add payerGivenName + payerFamilyName to PaymentAddress w3c/contact-picker#69 (4 comments by @aphillips, @hober, @marcoscaceres, @rsolomakhin)
-
TR publications
-
4 documents published.
-
Wake Lock API published twice as a Working Draft. History of Wake Lock API
-
"MediaStream Image Capture" published as a Working Draft. History of "MediaStream Image Capture"
-
MediaStream Recording published as a Working Draft. History of MediaStream Recording
-
Participants
-
1 organization joined.
-
Trust1Team joined.
-
GitHub
w3c/sensors
-
4 issues opened.
-
The internal slots are not reset w3c/sensors#243, by @pozdnyakov.
-
Find an appropriate test reviewer w3c/sensors#242, by @Honry.
-
Let the UA (platform) calculate optimal sampling frequency w3c/sensors#240, by @alexshalamov.
-
[meta] Fix broken deploy story, redux w3c/sensors#237, by @anssiko.
-
-
8 issues closed.
-
The Sensor.waitingForUpdate internal slot is useless w3c/sensors#201.
-
The Sensor.lastEventFiredAt internal slot is useless w3c/sensors#199.
-
Find an appropriate test reviewer w3c/sensors#242.
-
Agree on event names w3c/sensors#205.
-
Let the UA (platform) calculate optimal sampling frequency w3c/sensors#240.
-
[meta] Fix broken deploy story, redux w3c/sensors#237.
-
Clarify relationship between Sensor object and task source w3c/sensors#216.
-
-
1 issue reopened.
-
Clarify relationship between Sensor object and task source w3c/sensors#216, by @pozdnyakov.
-
-
13 issues received 37 new comments.
-
Should the API allow setting both samplingFrequency and reportingFrequency? w3c/sensors#209 (19 comments by @alexshalamov, @anssiko, @kenchris, @pozdnyakov, @rwaldron, @tobie)
-
Clarify relationship between Sensor object and task source w3c/sensors#216 (2 comments by @pozdnyakov, @tobie)
-
Define algorithm for suspending / resuming activated sensor objects w3c/sensors#227 (2 comments by @alexshalamov, @tobie)
-
Sensor.frequency needs to be setable to allow frequency adaptation w3c/sensors#63 (1 comment by @alexshalamov)
-
Issues caused by visibility state restriction semantics w3c/sensors#149 (1 comment by @alexshalamov)
-
Sensors unable to provide their state when instantiated w3c/sensors#214 (1 comment by @alexshalamov)
-
-
9 pull requests opened.
-
Add definition for optimal sampling frequency w3c/sensors#241, by @alexshalamov.
-
Rename 'onchange' to 'onreading' w3c/sensors#239, by @pozdnyakov.
-
Simplify deployment infra w3c/sensors#238, by @pozdnyakov.
-
Reland "Sensor objects fire 'change' event considering their own freq… w3c/sensors#236, by @pozdnyakov.
-
Introduce "sensor task source" w3c/sensors#234, by @pozdnyakov.
-
Add new editors w3c/sensors#233, by @anssiko.
-
[DO NOT MERGE] Add preliminary interactive diagram. w3c/sensors#232, by @tobie.
-
Update Sensor.timestamp description w3c/sensors#231, by @pozdnyakov.
-
-
9 pull requests merged.
-
Rename 'onchange' to 'onreading' w3c/sensors#239.
-
Add definition for optimal sampling frequency w3c/sensors#241.
-
Simplify deployment infra w3c/sensors#238.
-
Introduce "sensor task source" w3c/sensors#234.
-
Add new editors w3c/sensors#233.
-
Update Sensor.timestamp description w3c/sensors#231.
-
-
9 pull requests received 45 new comments.
-
Add definition for optimal sampling frequency w3c/sensors#241 (14 comments by @alexshalamov, @kenchris, @pozdnyakov, @rwaldron)
-
Sensor objects fire 'change' event considering their own frequency hint w3c/sensors#210 (2 comments by @anssiko)
-
Revert "Sensor objects fire 'change' event considering their own frequency hint" w3c/sensors#235 (1 comment by @pozdnyakov)
w3c/screen-wake-lock
-
4 issues opened.
-
Clarify state of screen lock after manual lock & unlock w3c/screen-wake-lock#102, by @jakearchibald.
-
Specify that platform-specific inactivity timer should be reset after the lock is released w3c/screen-wake-lock#101, by @andrey-logvinov.
-
Restrict Wake Lock to secure context w3c/screen-wake-lock#100, by @andrey-logvinov.
-
Disable Wake Lock in sandboxed frames w3c/screen-wake-lock#99, by @andrey-logvinov.
-
-
2 issues closed.
-
Clarify state of screen lock after manual lock & unlock w3c/screen-wake-lock#102.
-
"Implementation status" does not link anywhere w3c/screen-wake-lock#76.
-
-
5 issues received 11 new comments.
-
iframes keeping screen awake w3c/screen-wake-lock#51 (5 comments by @clelland, @dontcallmedom, @igrigorik, @marcoscaceres, @patrickkettner)
-
Clarify state of screen lock after manual lock & unlock w3c/screen-wake-lock#102 (3 comments by @andrey-logvinov, @jakearchibald, @patrickkettner)
-
-
3 pull requests opened.
-
Clarify screen lock reinstate on manual switch off w3c/screen-wake-lock#105, by @andrey-logvinov.
-
require a secure context for wakelock w3c/screen-wake-lock#104, by @patrickkettner.
-
clean up implementation status section w3c/screen-wake-lock#103, by @patrickkettner.
-
-
2 pull requests merged.
-
Clarify screen lock reinstate on manual switch off w3c/screen-wake-lock#105.
-
clean up implementation status section w3c/screen-wake-lock#103.
-
-
2 pull requests received 7 new comments.
-
clean up implementation status section w3c/screen-wake-lock#103 (3 comments by @dontcallmedom, @marcoscaceres, @patrickkettner)
w3c/ambient-light
-
1 issue received 10 new comments.
-
Security and Privacy considerations for ALS w3c/ambient-light#13 (10 comments by @alexshalamov, @anssiko, @lknik, @tobie)
-
-
1 pull request opened.
-
Align example code with latest GS API changes w3c/ambient-light#30, by @alexshalamov.
-
-
1 pull request merged.
-
Align example code with latest GS API changes w3c/ambient-light#30.
-
-
1 pull request received 1 new comment.
w3c/magnetometer
-
2 pull requests opened.
-
Align example code with latest GS API changes w3c/magnetometer#28, by @alexshalamov.
-
Update examples, fix some Bikeshed warnings w3c/magnetometer#27, by @anssiko.
-
-
2 pull requests merged.
-
Align example code with latest GS API changes w3c/magnetometer#28.
-
Update examples, fix some Bikeshed warnings w3c/magnetometer#27.
-
-
2 pull requests received 3 new comments.
-
Align example code with latest GS API changes w3c/magnetometer#28 (2 comments by @alexshalamov, @riju)
-
w3c/motion-sensors
-
1 pull request opened.
-
Synced the example code snippet with the updated Sensor interface. w3c/motion-sensors#22, by @pozdnyakov.
-
-
1 pull request merged.
-
Synced the example code snippet with the updated Sensor interface. w3c/motion-sensors#22.
-
w3c/accelerometer
-
1 pull request opened.
-
Align example with GS API spec changes w3c/accelerometer#19, by @alexshalamov.
-
-
1 pull request merged.
-
Align example with GS API spec changes w3c/accelerometer#19.
-
w3c/das-charter
-
7 issues opened.
-
Environmental sensors w3c/das-charter#33, by @kenchris.
-
Generic-sensor based geolocation API? w3c/das-charter#32, by @dontcallmedom.
-
Restart work on DeviceOrientation Event API w3c/das-charter#31, by @dontcallmedom.
-
Integrate WebUSB w3c/das-charter#30, by @dontcallmedom.
-
Integrate WebNFC w3c/das-charter#29, by @dontcallmedom.
-
Integrate Web Bluetooth? w3c/das-charter#28, by @dontcallmedom.
-
Stop joint work on media capture task force w3c/das-charter#27, by @dontcallmedom.
-
-
2 issues closed.
-
grammar in Media Capture section w3c/das-charter#19.
-
unclear requirement for implementations w3c/das-charter#20.
-
-
1 issue received 1 new comment.
-
1 pull request closed.
-
Clarify that multi groups task forces can only do in scope work w3c/das-charter#26.
-
w3c/battery
-
1 issue reopened.
-
Allow use from within secure context and top-level browsing context only w3c/battery#10, by @anssiko.
-
-
2 issues received 14 new comments.
-
Allow use from within secure context and top-level browsing context only w3c/battery#10 (10 comments by @anssiko, @FluorescentHallucinogen, @mounirlamouri, @RByers)
-
w3c/geolocation
-
1 issue received 1 new comment.
-
Disable geolocation by default in cross-origin iframes w3c/geolocation#10 (1 comment by @raymeskhoury)
-
w3c/gyroscope
-
1 issue closed.
-
Add link to use cases in spec w3c/gyroscope#13.
-
-
1 pull request merged.
-
Add link to use cases w3c/gyroscope#14.
-
TR publications
-
6 documents published.
-
HTML Media Capture published as a Candidate Recommendation Snapshot. History of HTML Media Capture
-
Generic Sensor API published twice as a Working Draft. History of Generic Sensor API
-
Ambient Light Sensor published as a Working Draft. History of Ambient Light Sensor
-
Orientation Sensor published as a First Public Working Draft. History of Orientation Sensor
-
Motion Sensors Explainer published as a Note. History of Motion Sensors Explainer
-
Participants
-
1 participant joined.
-
Raphael Spreitzer (W3C Invited Experts) joined.
-
GitHub
w3c/sensors
-
28 issues opened.
-
Define algorithm for suspending / resuming activated sensor objects w3c/sensors#227, by @alexshalamov.
-
Mark mitigation strategy section as informative and avoid RFC2119 language in it. w3c/sensors#226, by @tobie.
-
Should a "suspended" state be added w3c/sensors#223, by @tobie.
-
Missing browsing-context focus/unfocus hooks in HTML spec. w3c/sensors#222, by @tobie.
-
Investigate adding dedicated task sources w3c/sensors#221, by @tobie.
-
Should update sensor reading task be in sync with latest reading? w3c/sensors#220, by @alexshalamov.
-
Define parameters for events w3c/sensors#219, by @alexshalamov.
-
Define tasks for state changes w3c/sensors#218, by @alexshalamov.
-
Define algorithm for suspending / resuming activated sensor objects w3c/sensors#217, by @alexshalamov.
-
Clarify relationship between Sensor object and task source w3c/sensors#216, by @alexshalamov.
-
Sensors unable to provide their state when instantiated w3c/sensors#214, by @tobie.
-
Clarify sensor task source scope w3c/sensors#212, by @tobie.
-
Investigate using PWA installed status as indication of user intent w3c/sensors#211, by @tobie.
-
Should the API allow setting both samplingFrequency and reportingFrequency? w3c/sensors#209, by @pozdnyakov.
-
Agree on event names w3c/sensors#205, by @tobie.
-
The Update latest reading abstract operation is never invoked w3c/sensors#204, by @pozdnyakov.
-
Sensor object can stuck in `activating` state w3c/sensors#203, by @pozdnyakov.
-
The Sensor.waitingForUpdate internal slot is useless w3c/sensors#201, by @pozdnyakov.
-
The Update Observers abstract operation fires unspecified "reading" event w3c/sensors#200, by @pozdnyakov.
-
The Sensor.lastEventFiredAt internal slot is useless w3c/sensors#199, by @pozdnyakov.
-
Define processing model w3c/sensors#198, by @tobie.
-
Take into account user gestures as an input for security policy enforcement w3c/sensors#196, by @alexshalamov.
-
Security issues when used in combination with other APIs w3c/sensors#193, by @tobie.
-
Listing threats w3c/sensors#192, by @tobie.
-
Avoid PIN skimming attacks w3c/sensors#189, by @alexshalamov.
-
[meta] Publish a new Working Draft w3c/sensors#188, by @anssiko.
-
-
12 issues closed.
-
Reading attributes at different sensor states w3c/sensors#168.
-
Should update sensor reading task be in sync with latest reading? w3c/sensors#220.
-
Clarify sensor task source scope w3c/sensors#212.
-
Define algorithm for suspending / resuming activated sensor objects w3c/sensors#217.
-
Avoid PIN skimming attacks w3c/sensors#189.
-
Define parameters for events w3c/sensors#219.
-
[meta] Publish a new Working Draft w3c/sensors#188.
-
Exposing secondary values in the SensorReading w3c/sensors#151.
-
Provide the DeviceOrientation sensor w3c/sensors#170.
-
-
4 issues reopened.
-
Missing browsing-context focus/unfocus hooks in HTML spec. w3c/sensors#222, by @tobie.
-
The Handle Errors abstract operation must deactivate the activated Sensor object w3c/sensors#202, by @anssiko.
-
Avoid PIN skimming attacks w3c/sensors#189, by @tobie.
-
-
25 issues received 222 new comments.
-
Define processing model w3c/sensors#198 (31 comments by @alexshalamov, @anssiko, @pozdnyakov, @tobie)
-
Should the API allow setting both samplingFrequency and reportingFrequency? w3c/sensors#209 (29 comments by @alexshalamov, @pozdnyakov, @tobie)
-
Use task source mechanism to dispatch events instead of firing them synchronously w3c/sensors#215 (28 comments by @alexshalamov, @anssiko, @pozdnyakov, @tobie)
-
Call 'onchange' on a Senor instance considering its own frequency hint w3c/sensors#152 (27 comments by @alexshalamov, @anssiko, @pozdnyakov, @tobie)
-
Avoid PIN skimming attacks w3c/sensors#189 (21 comments by @alexshalamov, @anssiko, @kenchris, @lknik, @pozdnyakov, @tobie)
-
[meta] Publish a new Working Draft w3c/sensors#188 (9 comments by @anssiko, @dontcallmedom, @fhirsch, @tobie)
-
The Handle Errors abstract operation must deactivate the activated Sensor object w3c/sensors#202 (8 comments by @anssiko, @pozdnyakov, @tobie)
-
Take into account user gestures as an input for security policy enforcement w3c/sensors#196 (8 comments by @alexshalamov, @ojanvafai, @tobie)
-
Clarify relationship between Sensor object and task source w3c/sensors#216 (6 comments by @alexshalamov, @tobie)
-
Should update sensor reading task be in sync with latest reading? w3c/sensors#220 (6 comments by @alexshalamov, @tobie)
-
Define algorithm for suspending / resuming activated sensor objects w3c/sensors#217 (4 comments by @alexshalamov, @tobie)
-
Security issues when used in combination with other APIs w3c/sensors#193 (4 comments by @lknik, @tobie)
-
Define algorithm for suspending / resuming activated sensor objects w3c/sensors#227 (1 comment by @tobie)
-
-
15 pull requests opened.
-
Add Get value from latest reading abstract op. w3c/sensors#230, by @tobie.
-
Queue tasks for [[state]] changes. w3c/sensors#229, by @tobie.
-
Make mitigation strategy section informative. w3c/sensors#228, by @tobie.
-
Use the has focus steps algorithm. w3c/sensors#225, by @tobie.
-
Use focus chain. w3c/sensors#224, by @tobie.
-
Add mitigation strategy for skimming attacks when focus is lost. w3c/sensors#213, by @tobie.
-
Sensor objects fire 'change' event considering their own frequency hint w3c/sensors#210, by @pozdnyakov.
-
Consistent event names. w3c/sensors#208, by @tobie.
-
Add 'user triggered activation' as mitigation strategy w3c/sensors#207, by @alexshalamov.
-
Add mitigation strategy for focuseable elements w3c/sensors#206, by @alexshalamov.
-
Rewrite Abstract Operations w3c/sensors#197, by @pozdnyakov.
-
A Sensor instance sends 'onchange' considering its frequency hint w3c/sensors#195, by @pozdnyakov.
-
Update Acknowledgements w3c/sensors#194, by @anssiko.
-
First pass at adding sensor-specific mitigation strategies. w3c/sensors#191, by @tobie.
-
Add Input Elements to Mitigation Strategies w3c/sensors#190, by @anssiko.
-
-
7 pull requests merged.
-
Add Get value from latest reading abstract op. w3c/sensors#230.
-
Make mitigation strategy section informative. w3c/sensors#228.
-
Use the has focus steps algorithm. w3c/sensors#225.
-
Add mitigation strategy for skimming attacks when focus is lost. w3c/sensors#213.
-
Consistent event names. w3c/sensors#208.
-
First pass at adding sensor-specific mitigation strategies. w3c/sensors#191.
-
Update Acknowledgements w3c/sensors#194.
-
-
5 pull requests closed.
-
Queue tasks for [[state]] changes. w3c/sensors#229.
-
Use focus chain. w3c/sensors#224.
-
Add mitigation strategy for focuseable elements w3c/sensors#206.
-
Add Input Elements to Mitigation Strategies w3c/sensors#190.
-
A Sensor instance sends 'onchange' considering its frequency hint w3c/sensors#195.
-
-
13 pull requests received 216 new comments.
-
Add mitigation strategy for skimming attacks when focus is lost. w3c/sensors#213 (69 comments by @alexshalamov, @anssiko, @kenchris, @pozdnyakov, @tobie)
-
First pass at adding sensor-specific mitigation strategies. w3c/sensors#191 (47 comments by @alexshalamov, @anssiko, @kenchris, @maryammjd, @pozdnyakov, @tobie)
-
Add 'user triggered activation' as mitigation strategy w3c/sensors#207 (24 comments by @alexshalamov, @anssiko, @jyasskin, @ojanvafai, @tobie)
-
Rewrite Abstract Operations w3c/sensors#197 (21 comments by @alexshalamov, @anssiko, @pozdnyakov, @tobie)
-
Add Input Elements to Mitigation Strategies w3c/sensors#190 (21 comments by @anssiko, @rwaldron, @tobie)
-
Sensor objects fire 'change' event considering their own frequency hint w3c/sensors#210 (14 comments by @alexshalamov, @anssiko, @pozdnyakov, @tobie)
-
Add mitigation strategy for focuseable elements w3c/sensors#206 (3 comments by @alexshalamov, @anssiko, @tobie)
-
A Sensor instance sends 'onchange' considering its frequency hint w3c/sensors#195 (2 comments by @pozdnyakov)
-
w3c/gyroscope
-
1 issue opened.
-
Add link to use cases in spec w3c/gyroscope#13, by @owencm.
-
-
1 pull request opened.
-
Add link to use cases w3c/gyroscope#14, by @pozdnyakov.
-
w3c/magnetometer
-
1 issue opened.
-
Link to use cases in the spec w3c/magnetometer#26, by @owencm.
-
-
2 issues closed.
-
Permission w3c/magnetometer#5.
-
Link to use cases in the spec w3c/magnetometer#26.
-
-
3 issues received 7 new comments.
-
Provide API to access uncalibrated magnetometer values w3c/magnetometer#16 (5 comments by @anssiko, @riju, @tobie)
-
-
1 pull request merged.
-
Add RawMagnetometer, for uncalibrated readings. w3c/magnetometer#21.
-
-
1 pull request received 59 new comments.
-
Add RawMagnetometer, for uncalibrated readings. w3c/magnetometer#21 (59 comments by @alexshalamov, @anssiko, @kenchris, @pozdnyakov, @riju, @rwaldron, @tobie)
-
w3c/accelerometer
-
1 issue opened.
-
Add use cases to spec w3c/accelerometer#18, by @owencm.
-
w3c/geolocation
-
1 issue opened.
-
Background Geolocation via Service Workers w3c/geolocation#13, by @RichardMaher.
-
w3c/contact-picker
-
1 issue received 1 new comment.
w3c/ambient-light
-
1 issue opened.
-
[meta] Publish a new Working Draft w3c/ambient-light#29, by @anssiko.
-
-
2 issues closed.
-
[meta] Publish a new Working Draft w3c/ambient-light#29.
-
Auto reporting mode is not defined w3c/ambient-light#19.
-
-
4 issues received 8 new comments.
-
Security and Privacy considerations for ALS w3c/ambient-light#13 (4 comments by @alexshalamov, @lknik)
-
-
1 pull request opened.
-
Align reporting mode terminology with the Generic Sensor API w3c/ambient-light#28, by @anssiko.
-
-
1 pull request merged.
-
Align reporting mode terminology with the Generic Sensor API w3c/ambient-light#28.
-
-
2 pull requests received 9 new comments.
-
Align reporting mode terminology with the Generic Sensor API w3c/ambient-light#28 (5 comments by @anssiko, @tobie)
-
Provide "Use Cases and Requirements" section w3c/ambient-light#26 (4 comments by @anssiko, @lknik, @tobie)
-
w3c/battery
-
1 issue opened.
-
[meta] Publish a revised Candidate Recommendation w3c/battery#12, by @anssiko.
-
-
2 issues received 7 new comments.
-
[meta] Publish a revised Candidate Recommendation w3c/battery#12 (6 comments by @anssiko, @dontcallmedom, @Honry)
-
Allow use from within secure context and top-level browsing context only w3c/battery#10 (1 comment by @anssiko)
-
-
1 pull request opened.
-
Fix #10: Restrict to secure context and top-level browsing context w3c/battery#11, by @anssiko.
-
-
1 pull request merged.
-
1 pull request received 1 new comment.
-
Fix #10: Restrict to secure context and top-level browsing context w3c/battery#11 (1 comment by @anssiko)
-
w3c/html-media-capture
-
2 issues opened.
-
[meta] Publish a revised Candidate Recommendation w3c/html-media-capture#14, by @anssiko.
-
Define clearly how the capture IDL attribute is reflected w3c/html-media-capture#12, by @foolip.
-
-
2 issues closed.
-
Define clearly how the capture IDL attribute is reflected w3c/html-media-capture#12.
-
Update test suite w3c/html-media-capture#7.
-
-
5 issues received 6 new comments.
-
[meta] Publish a revised Candidate Recommendation w3c/html-media-capture#14 (2 comments by @anssiko)
-
VideoFacingModeEnum as the capture attribute's value w3c/html-media-capture#4 (1 comment by @anssiko)
-
Define clearly how the capture IDL attribute is reflected w3c/html-media-capture#12 (1 comment by @domenic)
-
[meta] Prepare a revised Candidate Recommendation snapshot w3c/html-media-capture#9 (1 comment by @anssiko)
-
-
2 pull requests opened.
-
Fix #12: Make the capture IDL attribute a DOMString w3c/html-media-capture#13, by @anssiko.
-
Fix broken fragments w3c/html-media-capture#11, by @anssiko.
-
-
2 pull requests merged.
-
Fix #12: Make the capture IDL attribute a DOMString w3c/html-media-capture#13.
-
Fix broken fragments w3c/html-media-capture#11.
-
-
1 pull request received 4 new comments.
-
Fix #12: Make the capture IDL attribute a DOMString w3c/html-media-capture#13 (4 comments by @anssiko, @domenic)
-
w3c/screen-wake-lock
-
1 issue opened.
-
new type: location? w3c/screen-wake-lock#98, by @chaals.
-
w3c/orientation-sensor
-
1 issue reopened.
-
Define GeomagneticOrientationSensor interface w3c/orientation-sensor#15, by @alexshalamov.
-
-
2 issues received 2 new comments.
-
Clicking on Alex goes to https://intel.com, click on others goes to intel.com without https:// w3c/orientation-sensor#9 (1 comment by @anssiko)
-
Define GeomagneticOrientationSensor interface w3c/orientation-sensor#15 (1 comment by @alexshalamov)
-
-
4 pull requests opened.
-
Fix typo in model section w3c/orientation-sensor#40, by @alexshalamov.
-
Add RelativeOrietnationSensor interface w3c/orientation-sensor#39, by @alexshalamov.
-
FPWD snapshot w3c/orientation-sensor#38, by @anssiko.
-
Editorial pass w3c/orientation-sensor#37, by @anssiko.
-
-
4 pull requests merged.
-
Fix typo in model section w3c/orientation-sensor#40.
-
Add RelativeOrietnationSensor interface w3c/orientation-sensor#39.
-
FPWD snapshot w3c/orientation-sensor#38.
-
Editorial pass w3c/orientation-sensor#37.
-
-
3 pull requests received 16 new comments.
-
Add RelativeOrietnationSensor interface w3c/orientation-sensor#39 (14 comments by @alexshalamov, @anssiko, @kenchris, @pozdnyakov)
-
w3c/das-wg
-
1 pull request opened.
-
Homepage cleanup w3c/das-wg#1, by @anssiko.
-
-
1 pull request merged.
-
Homepage cleanup w3c/das-wg#1.
-
-
1 pull request received 2 new comments.
w3c/motion-sensors
-
1 pull request opened.
-
FPWD snapshot w3c/motion-sensors#21, by @anssiko.
-
-
1 pull request merged.
-
FPWD snapshot w3c/motion-sensors#21.
-
TR publications
-
8 documents published.
-
Accelerometer published twice as a Working Draft. History of Accelerometer
-
Gyroscope published twice as a Working Draft. History of Gyroscope
-
Magnetometer published twice as a Working Draft. History of Magnetometer
-
Media Capture Depth Stream Extensions published as a Working Draft. History of Media Capture Depth Stream Extensions
-
MediaStream Recording published as a Working Draft. History of MediaStream Recording
-
GitHub
w3c/ambient-light
-
2 issues opened.
-
Make the `illuminance` attribute nullable w3c/ambient-light#25, by @pozdnyakov.
-
AmbientLightSensor constructor cannot initialize illuminance w3c/ambient-light#24, by @foolip.
-
-
2 issues closed.
-
Make the `illuminance` attribute nullable w3c/ambient-light#25.
-
AmbientLightSensor constructor cannot initialize illuminance w3c/ambient-light#24.
-
-
1 issue reopened.
-
Add description for use cases w3c/ambient-light#23, by @anssiko.
-
-
3 issues received 21 new comments.
-
Add description for use cases w3c/ambient-light#23 (13 comments by @anssiko, @noncombatant, @owencm, @reillyeon, @tobie)
-
AmbientLightSensor constructor cannot initialize illuminance w3c/ambient-light#24 (6 comments by @foolip, @pozdnyakov, @tobie)
-
-
2 pull requests opened.
-
Make the illuminance attribute nullable. w3c/ambient-light#27, by @tobie.
-
Provide "Use Cases and Requirements" section w3c/ambient-light#26, by @pozdnyakov.
-
-
2 pull requests merged.
-
Make the illuminance attribute nullable. w3c/ambient-light#27.
-
Provide "Use Cases and Requirements" section w3c/ambient-light#26.
-
-
2 pull requests received 25 new comments.
-
Provide "Use Cases and Requirements" section w3c/ambient-light#26 (24 comments by @alexshalamov, @anssiko, @tobie)
-
w3c/html-media-capture
-
2 issues opened.
-
[meta] Prepare a revised Candidate Recommendation snapshot w3c/html-media-capture#9, by @anssiko.
-
No facing mode for microphone when capturing audio w3c/html-media-capture#8, by @Honry.
-
-
2 issues closed.
-
[meta] Prepare a revised Candidate Recommendation snapshot w3c/html-media-capture#9.
-
No facing mode for microphone when capturing audio w3c/html-media-capture#8.
-
-
3 issues received 15 new comments.
-
[meta] Prepare a revised Candidate Recommendation snapshot w3c/html-media-capture#9 (4 comments by @anssiko, @dontcallmedom)
-
1 pull request opened.
-
CR3 snapshot w3c/html-media-capture#10, by @anssiko.
-
-
1 pull request merged.
-
CR3 snapshot w3c/html-media-capture#10.
-
w3c/sensors
-
3 issues opened.
-
Relation to Permissions API w3c/sensors#183, by @reillyeon.
-
Security/privacy concerns beyond fingerprinting -- data exfiltration w3c/sensors#182, by @wseltzer.
-
w3c.github.io/sensors/usecases.html 404s w3c/sensors#181, by @scheib.
-
-
4 issues closed.
-
Find a better name for 'unconnected' state w3c/sensors#160.
-
Fix deploy script for PRs w3c/sensors#173.
-
Top-level browsing context restrictions. w3c/sensors#175.
-
Relax requirements for asking permissions in sensors w3c/sensors#174.
-
-
1 issue reopened.
-
Find a better name for 'unconnected' state w3c/sensors#160, by @tobie.
-
-
8 issues received 52 new comments.
-
Find a better name for 'unconnected' state w3c/sensors#160 (20 comments by @kenchris, @pozdnyakov, @rwaldron, @tobie)
-
Javascript 120Hz devicemotion events for high end inertial applications w3c/sensors#98 (14 comments by @alexshalamov, @maryammjd, @timvolodine, @tobie)
-
Relation to Permissions API w3c/sensors#183 (9 comments by @anssiko, @pozdnyakov, @reillyeon, @riju, @tobie)
-
Simplify extension of the Permissions API for concrete sensor implementations w3c/sensors#22 (5 comments by @anssiko, @tobie)
-
Security/privacy concerns beyond fingerprinting -- data exfiltration w3c/sensors#182 (1 comment by @lknik)
-
-
6 pull requests opened.
-
Fix deploy script for PRs. w3c/sensors#187, by @tobie.
-
Add first draft of lifecycle diagram. w3c/sensors#186, by @tobie.
-
Structure threat mitigation section. w3c/sensors#185, by @tobie.
-
Revamp requirements around the Permissions API. w3c/sensors#184, by @tobie.
-
Stop exposing Sensor state. w3c/sensors#180, by @tobie.
-
Merge 'unconnected' and 'errored' states into 'idle' w3c/sensors#179, by @pozdnyakov.
-
-
6 pull requests merged.
-
Add first draft of lifecycle diagram. w3c/sensors#186.
-
Fix deploy script for PRs. w3c/sensors#187.
-
Structure threat mitigation section. w3c/sensors#185.
-
Revamp requirements around the Permissions API. w3c/sensors#184.
-
Stop exposing Sensor state. w3c/sensors#180.
-
Merge 'unconnected' and 'errored' states into 'idle' w3c/sensors#179.
-
-
1 pull request closed.
-
Use 'activate' semantics in state and method names w3c/sensors#177.
-
-
4 pull requests received 15 new comments.
w3c/magnetometer
-
1 issue opened.
-
Add use-cases and requirements section w3c/magnetometer#24, by @alexshalamov.
-
-
1 issue closed.
-
Add use-cases and requirements section w3c/magnetometer#24.
-
-
1 issue received 3 new comments.
-
1 pull request opened.
-
Add use cases section w3c/magnetometer#25, by @riju.
-
-
1 pull request merged.
-
Add use cases section w3c/magnetometer#25.
-
-
2 pull requests received 47 new comments.
-
Add RawMagnetometer, for uncalibrated readings. w3c/magnetometer#21 (41 comments by @alexshalamov, @anssiko, @kenchris, @riju, @tobie)
-
Add use cases section w3c/magnetometer#25 (6 comments by @alexshalamov, @anssiko, @pozdnyakov, @riju)
-
w3c/deviceorientation
-
1 issue received 2 new comments.
-
Security/privacy consideration: cross-origin linkage w3c/deviceorientation#33 (2 comments by @dontcallmedom, @gmandyam)
-
-
1 pull request opened.
-
updated references with the latest W3C spec drafts w3c/deviceorientation#42, by @ashimura.
-
-
2 pull requests merged.
-
updated references with the latest W3C spec drafts w3c/deviceorientation#42.
-
Update spec-source-orientation.html - clarify null case for motion w3c/deviceorientation#41.
-
w3c/orientation-sensor
-
3 issues opened.
-
Use low-level permission tokens for orientation sensors w3c/orientation-sensor#33, by @alexshalamov.
-
Throw TypeError when invalid type is provided to populateMatrix w3c/orientation-sensor#31, by @alexshalamov.
-
Return quaternion as [x,y,z,w] w3c/orientation-sensor#29, by @pozdnyakov.
-
-
3 issues closed.
-
Use low-level permission tokens for orientation sensors w3c/orientation-sensor#33.
-
Return quaternion as [x,y,z,w] w3c/orientation-sensor#29.
-
Throw TypeError when invalid type is provided to populateMatrix w3c/orientation-sensor#31.
-
-
1 issue reopened.
-
Return quaternion as [x,y,z,w] w3c/orientation-sensor#29, by @pozdnyakov.
-
-
2 issues received 14 new comments.
-
Return quaternion as [x,y,z,w] w3c/orientation-sensor#29 (12 comments by @alexshalamov, @kenchris, @pozdnyakov)
-
Use low-level permission tokens for orientation sensors w3c/orientation-sensor#33 (2 comments by @alexshalamov, @pozdnyakov)
-
-
6 pull requests opened.
-
Move illustrations to 'images' folder w3c/orientation-sensor#36, by @alexshalamov.
-
Use low-level sensor permission tokens for orientation sensor w3c/orientation-sensor#35, by @alexshalamov.
-
Add a note explaining the quaternion components order used w3c/orientation-sensor#34, by @pozdnyakov.
-
Fix #31 Throw TypeError when invalid type is provided to populateMatrix w3c/orientation-sensor#32, by @pozdnyakov.
-
Return quaternion as [x,y,z,w] w3c/orientation-sensor#30, by @pozdnyakov.
-
Update populateMatrix() algorithm w3c/orientation-sensor#28, by @pozdnyakov.
-
-
7 pull requests merged.
-
Move illustrations to 'images' folder w3c/orientation-sensor#36.
-
Use low-level sensor permission tokens for orientation sensor w3c/orientation-sensor#35.
-
Add a note explaining the quaternion components order used w3c/orientation-sensor#34.
-
Fix #31 Throw TypeError when invalid type is provided to populateMatrix w3c/orientation-sensor#32.
-
Return quaternion as [x,y,z,w] w3c/orientation-sensor#30.
-
Update populateMatrix() algorithm w3c/orientation-sensor#28.
-
Reference the Motion Sensor Explainer document w3c/orientation-sensor#26.
-
-
2 pull requests received 4 new comments.
-
Use low-level sensor permission tokens for orientation sensor w3c/orientation-sensor#35 (3 comments by @alexshalamov, @anssiko)
-
w3c/screen-wake-lock
-
2 issues received 4 new comments.
-
Consider restricting Wake Lock API to Secure Contexts w3c/screen-wake-lock#82 (2 comments by @dontcallmedom, @marcoscaceres)
-
"Implementation status" does not link anywhere w3c/screen-wake-lock#76 (2 comments by @dontcallmedom, @marcoscaceres)
-
w3c/accelerometer
-
1 issue opened.
-
The image is not showing in the live spec w3c/accelerometer#17, by @kenchris.
-
-
1 issue closed.
-
The image is not showing in the live spec w3c/accelerometer#17.
-
-
1 issue received 6 new comments.
-
The image is not showing in the live spec w3c/accelerometer#17 (6 comments by @alexshalamov, @anssiko, @dontcallmedom)
-
w3c/geolocation
-
1 issue opened.
-
What error should be returned when trying to access position from insecure origin? w3c/geolocation#12, by @yell0wd0g.
-
-
1 issue received 3 new comments.
-
What error should be returned when trying to access position from insecure origin? w3c/geolocation#12 (3 comments by @mkruisselbrink, @yell0wd0g)
-
TR publications
-
1 document published.
-
Media Capture Depth Stream Extensions published as a Working Draft. History of Media Capture Depth Stream Extensions
-
GitHub
w3c/sensors
-
5 issues opened.
-
Dynamic sensor add/remove w3c/sensors#178, by @larsgk.
-
Calibration using other sensors w3c/sensors#176, by @kenchris.
-
Top-level browsing context restrictions. w3c/sensors#175, by @mikewest.
-
Relax requirements for asking permissions in sensors w3c/sensors#174, by @pozdnyakov.
-
Fix deploy script for PRs w3c/sensors#173, by @tobie.
-
-
2 issues closed.
-
Calibration using other sensors w3c/sensors#176.
-
Dynamic sensor add/remove w3c/sensors#178.
-
-
2 issues reopened.
-
Don't allocate response objects to avoid triggering GC w3c/sensors#153, by @tobie.
-
Relax requirements for asking permissions in sensors w3c/sensors#174, by @anssiko.
-
-
14 issues received 139 new comments.
-
Provide the DeviceOrientation sensor w3c/sensors#170 (26 comments by @alexshalamov, @anssiko, @kenchris, @pozdnyakov, @tobie)
-
Don't allocate response objects to avoid triggering GC w3c/sensors#153 (14 comments by @alexshalamov, @Maksims, @pozdnyakov, @rwaldron, @tobie)
-
Find a better name for 'unconnected' state w3c/sensors#160 (13 comments by @dontcallmedom, @pozdnyakov, @rwaldron, @tobie)
-
Javascript 120Hz devicemotion events for high end inertial applications w3c/sensors#98 (12 comments by @lknik, @maryammjd, @timvolodine, @tobie)
-
Relax requirements for asking permissions in sensors w3c/sensors#174 (11 comments by @anssiko, @kenchris, @lknik, @maryammjd, @owencm, @tobie)
-
Simplify extension of the Permissions API for concrete sensor implementations w3c/sensors#22 (10 comments by @anssiko, @owencm, @tobie)
-
Call 'onchange' on a Senor instance considering its own frequency hint w3c/sensors#152 (8 comments by @jimmy-huang, @pozdnyakov, @tobie)
-
granularity of Permission name for concrete/ fusion sensors w3c/sensors#132 (3 comments by @pozdnyakov, @tobie)
-
Do we need a lightweight interface representing available sensors? w3c/sensors#28 (1 comment by @larsgk)
-
2 pull requests opened.
-
Use 'activate' semantics in state and method names w3c/sensors#177, by @pozdnyakov.
-
Simplify permissions. w3c/sensors#172, by @tobie.
-
-
1 pull request merged.
-
Simplify permissions. w3c/sensors#172.
-
-
2 pull requests received 18 new comments.
-
Use 'activate' semantics in state and method names w3c/sensors#177 (9 comments by @pozdnyakov, @rwaldron, @tobie)
-
w3c/motion-sensors
-
5 issues opened.
-
Clarify expectations or requirements for sampling rate and precision given use cases w3c/motion-sensors#19, by @owencm.
-
Consider using MathJax for math w3c/motion-sensors#8, by @kenchris.
-
Replace 𝛼 with a in complementary filter w3c/motion-sensors#7, by @kenchris.
-
Use × in multiplication, not x w3c/motion-sensors#6, by @kenchris.
-
Link to calibration dfn in Generic Sensor API w3c/motion-sensors#3, by @tobie.
-
-
5 issues closed.
-
Clarify expectations or requirements for sampling rate and precision given use cases w3c/motion-sensors#19.
-
Replace 𝛼 with a in complementary filter w3c/motion-sensors#7.
-
Consider using MathJax for math w3c/motion-sensors#8.
-
Use × in multiplication, not x w3c/motion-sensors#6.
-
Link to calibration dfn in Generic Sensor API w3c/motion-sensors#3.
-
-
3 issues received 3 new comments.
-
Clarify expectations or requirements for sampling rate and precision given use cases w3c/motion-sensors#19 (1 comment by @alexshalamov)
-
-
15 pull requests opened.
-
Add use-cases section to the explainer document w3c/motion-sensors#20, by @alexshalamov.
-
Add link to version history of the document w3c/motion-sensors#18, by @alexshalamov.
-
Add Alex to editors list w3c/motion-sensors#17, by @pozdnyakov.
-
Editorial pass fix w3c/motion-sensors#16, by @anssiko.
-
Add links to LinearAccelerometer and Gravity sensor interfaces w3c/motion-sensors#15, by @alexshalamov.
-
Rename OrientationSensor to AbsoluteOrientationSensor w3c/motion-sensors#14, by @pozdnyakov.
-
Editorial pass w3c/motion-sensors#13, by @anssiko.
-
Replace weight constant symbol in a complementary filter description w3c/motion-sensors#12, by @alexshalamov.
-
Use correct math symbol for cross product operations w3c/motion-sensors#11, by @alexshalamov.
-
Add reference to "calibration" definition in generic sensor spec w3c/motion-sensors#10, by @alexshalamov.
-
Add cross-references to low-level sensor specifications w3c/motion-sensors#9, by @alexshalamov.
-
Add illustration for orientation sensor w3c/motion-sensors#5, by @alexshalamov.
-
Fix a mistake in prose describing Orientation Sensor w3c/motion-sensors#4, by @pozdnyakov.
-
explainer.bs --> index.bs w3c/motion-sensors#2, by @tobie.
-
Probably don't want it to look like a spec. w3c/motion-sensors#1, by @marcoscaceres.
-
-
14 pull requests merged.
-
Add use-cases section to the explainer document w3c/motion-sensors#20.
-
Add link to version history of the document w3c/motion-sensors#18.
-
Add Alex to editors list w3c/motion-sensors#17.
-
Editorial pass fix w3c/motion-sensors#16.
-
Add links to LinearAccelerometer and Gravity sensor interfaces w3c/motion-sensors#15.
-
Editorial pass w3c/motion-sensors#13.
-
Rename OrientationSensor to AbsoluteOrientationSensor w3c/motion-sensors#14.
-
Replace weight constant symbol in a complementary filter description w3c/motion-sensors#12.
-
Use correct math symbol for cross product operations w3c/motion-sensors#11.
-
Add reference to "calibration" definition in generic sensor spec w3c/motion-sensors#10.
-
Add cross-references to low-level sensor specifications w3c/motion-sensors#9.
-
Add illustration for orientation sensor w3c/motion-sensors#5.
-
Fix a mistake in prose describing Orientation Sensor w3c/motion-sensors#4.
-
explainer.bs --> index.bs w3c/motion-sensors#2.
-
-
1 pull request closed.
-
Probably don't want it to look like a spec. w3c/motion-sensors#1.
-
-
9 pull requests received 43 new comments.
-
Add illustration for orientation sensor w3c/motion-sensors#5 (22 comments by @alexshalamov, @kenchris, @pozdnyakov)
-
Fix a mistake in prose describing Orientation Sensor w3c/motion-sensors#4 (6 comments by @kenchris, @pozdnyakov)
-
Probably don't want it to look like a spec. w3c/motion-sensors#1 (4 comments by @marcoscaceres, @tobie)
-
Add use-cases section to the explainer document w3c/motion-sensors#20 (2 comments by @anssiko, @pozdnyakov)
-
Add links to LinearAccelerometer and Gravity sensor interfaces w3c/motion-sensors#15 (1 comment by @kenchris)
-
Add cross-references to low-level sensor specifications w3c/motion-sensors#9 (1 comment by @kenchris)
-
w3c/magnetometer
-
2 pull requests opened.
-
Add permission descriptor for Magnetometer API w3c/magnetometer#23, by @alexshalamov.
-
Correct physical definition for magnetometer sensor w3c/magnetometer#22, by @alexshalamov.
-
-
2 pull requests merged.
-
Add permission descriptor for Magnetometer API w3c/magnetometer#23.
-
Correct physical definition for magnetometer sensor w3c/magnetometer#22.
-
-
2 pull requests received 5 new comments.
-
Add RawMagnetometer, for uncalibrated readings. w3c/magnetometer#21 (3 comments by @anssiko, @kenchris, @tobie)
-
Add permission descriptor for Magnetometer API w3c/magnetometer#23 (2 comments by @alexshalamov, @riju)
-
w3c/orientation-sensor
-
9 issues opened.
-
Find better references for [QUATERNIONS] and [QUATCONV] w3c/orientation-sensor#25, by @alexshalamov.
-
Define populateMatrix algorithm taking into account projection / translation values w3c/orientation-sensor#24, by @alexshalamov.
-
Expose quaternion as an attribute w3c/orientation-sensor#21, by @pozdnyakov.
-
Allow other buffer types to be passed to populateMatrix w3c/orientation-sensor#20, by @alexshalamov.
-
Define GeomagneticOrientationSensor interface w3c/orientation-sensor#15, by @alexshalamov.
-
Clarify the relationship with [DEVICEORIENTATION] w3c/orientation-sensor#13, by @reillyeon.
-
Clicking on Alex goes to https://intel.com, click on others goes to intel.com without https:// w3c/orientation-sensor#9, by @kenchris.
-
Maybe too restrictive: with a size other than four w3c/orientation-sensor#7, by @kenchris.
-
Image has weird perspective w3c/orientation-sensor#3, by @kenchris.
-
-
6 issues closed.
-
Allow other buffer types to be passed to populateMatrix w3c/orientation-sensor#20.
-
Define populateMatrix algorithm taking into account projection / translation values w3c/orientation-sensor#24.
-
Expose quaternion as an attribute w3c/orientation-sensor#21.
-
Clarify the relationship with [DEVICEORIENTATION] w3c/orientation-sensor#13.
-
Clicking on Alex goes to https://intel.com, click on others goes to intel.com without https:// w3c/orientation-sensor#9.
-
Image has weird perspective w3c/orientation-sensor#3.
-
-
7 issues received 34 new comments.
-
Define GeomagneticOrientationSensor interface w3c/orientation-sensor#15 (9 comments by @alexshalamov, @anssiko, @kenchris, @pozdnyakov)
-
Maybe too restrictive: with a size other than four w3c/orientation-sensor#7 (8 comments by @alexshalamov, @anssiko, @kenchris, @pozdnyakov)
-
Allow other buffer types to be passed to populateMatrix w3c/orientation-sensor#20 (6 comments by @alexshalamov, @kenchris, @pozdnyakov)
-
Define populateMatrix algorithm taking into account projection / translation values w3c/orientation-sensor#24 (3 comments by @alexshalamov, @pozdnyakov)
-
Clicking on Alex goes to https://intel.com, click on others goes to intel.com without https:// w3c/orientation-sensor#9 (3 comments by @alexshalamov, @anssiko, @kenchris)
-
Expose quaternion as an attribute w3c/orientation-sensor#21 (2 comments by @alexshalamov, @pozdnyakov)
-
-
18 pull requests opened.
-
Add permission descriptor for OrientationSensor API w3c/orientation-sensor#27, by @alexshalamov.
-
Reference the Motion Sensor Explainer document w3c/orientation-sensor#26, by @pozdnyakov.
-
Allow other buffer types to be passed to populateMatrix w3c/orientation-sensor#23, by @alexshalamov.
-
Expose quaternion as an attribute w3c/orientation-sensor#22, by @pozdnyakov.
-
Convert the 'populateQuaternion' function to 'quaternion' attribute w3c/orientation-sensor#19, by @pozdnyakov.
-
Reference to Motion Sensors explainer w3c/orientation-sensor#18, by @pozdnyakov.
-
Split between OrientationSensor and AbsoluteOrientationSensor w3c/orientation-sensor#17, by @pozdnyakov.
-
Align with low-level sensor specifications w3c/orientation-sensor#16, by @alexshalamov.
-
Fix #13 Describe differences with [DEVICEORIENTATION] w3c/orientation-sensor#14, by @pozdnyakov.
-
Add description for populateMatrix() w3c/orientation-sensor#12, by @pozdnyakov.
-
Fix editor's url from https => http w3c/orientation-sensor#11, by @alexshalamov.
-
Expand sensor-fusion, link to low-level sensors w3c/orientation-sensor#10, by @anssiko.
-
Fix prose in Abstract section w3c/orientation-sensor#8, by @pozdnyakov.
-
Minor editorial changes w3c/orientation-sensor#6, by @alexshalamov.
-
Editorial changes w3c/orientation-sensor#5, by @kenchris.
-
Align z axis of a device with coordinate system w3c/orientation-sensor#4, by @alexshalamov.
-
Improve description of model section w3c/orientation-sensor#2, by @alexshalamov.
-
Editorial changes w3c/orientation-sensor#1, by @kenchris.
-
-
16 pull requests merged.
-
Add permission descriptor for OrientationSensor API w3c/orientation-sensor#27.
-
Allow other buffer types to be passed to populateMatrix w3c/orientation-sensor#23.
-
Expose quaternion as an attribute w3c/orientation-sensor#22.
-
Convert the 'populateQuaternion' function to 'quaternion' attribute w3c/orientation-sensor#19.
-
Reference to Motion Sensors explainer w3c/orientation-sensor#18.
-
Split between OrientationSensor and AbsoluteOrientationSensor w3c/orientation-sensor#17.
-
Align with low-level sensor specifications w3c/orientation-sensor#16.
-
Fix #13 Describe differences with [DEVICEORIENTATION] w3c/orientation-sensor#14.
-
Add description for populateMatrix() w3c/orientation-sensor#12.
-
Fix editor's url from https => http w3c/orientation-sensor#11.
-
Expand sensor-fusion, link to low-level sensors w3c/orientation-sensor#10.
-
Fix prose in Abstract section w3c/orientation-sensor#8.
-
Minor editorial changes w3c/orientation-sensor#6.
-
Editorial changes w3c/orientation-sensor#5.
-
Align z axis of a device with coordinate system w3c/orientation-sensor#4.
-
Improve description of model section w3c/orientation-sensor#2.
-
-
1 pull request closed.
-
Editorial changes w3c/orientation-sensor#1.
-
-
1 pull request reopened.
-
Editorial changes w3c/orientation-sensor#1, by @kenchris.
-
-
16 pull requests received 145 new comments.
-
Editorial changes w3c/orientation-sensor#1 (59 comments by @anssiko, @kenchris, @pozdnyakov, @tobie)
-
Allow other buffer types to be passed to populateMatrix w3c/orientation-sensor#23 (25 comments by @alexshalamov, @anssiko, @kenchris, @pozdnyakov)
-
Split between OrientationSensor and AbsoluteOrientationSensor w3c/orientation-sensor#17 (10 comments by @alexshalamov, @anssiko, @kenchris, @pozdnyakov)
-
Add description for populateMatrix() w3c/orientation-sensor#12 (10 comments by @alexshalamov, @kenchris, @pozdnyakov)
-
Expose quaternion as an attribute w3c/orientation-sensor#22 (7 comments by @alexshalamov, @kenchris, @pozdnyakov)
-
Convert the 'populateQuaternion' function to 'quaternion' attribute w3c/orientation-sensor#19 (7 comments by @alexshalamov, @kenchris, @pozdnyakov)
-
Improve description of model section w3c/orientation-sensor#2 (7 comments by @alexshalamov, @anssiko, @kenchris, @pozdnyakov)
-
Editorial changes w3c/orientation-sensor#5 (5 comments by @alexshalamov, @anssiko, @kenchris, @pozdnyakov)
-
Fix #13 Describe differences with [DEVICEORIENTATION] w3c/orientation-sensor#14 (3 comments by @kenchris)
-
Expand sensor-fusion, link to low-level sensors w3c/orientation-sensor#10 (3 comments by @anssiko, @kenchris)
-
w3c/gyroscope
-
2 pull requests opened.
-
Add permission descriptor for Gyroscope API w3c/gyroscope#12, by @alexshalamov.
-
Rename "current angular velocity" to "angular velocity" w3c/gyroscope#11, by @alexshalamov.
-
-
2 pull requests merged.
-
Add permission descriptor for Gyroscope API w3c/gyroscope#12.
-
Rename "current angular velocity" to "angular velocity" w3c/gyroscope#11.
-
w3c/accelerometer
-
3 issues closed.
-
Integration in Permission API w3c/accelerometer#4.
-
includeGravity parameter turns low-level sensor into high-level fused one. w3c/accelerometer#3.
-
No way to get isolated gravity w3c/accelerometer#13.
-
-
2 issues received 9 new comments.
-
includeGravity parameter turns low-level sensor into high-level fused one. w3c/accelerometer#3 (5 comments by @alexshalamov, @anssiko, @tobie)
-
Integration in Permission API w3c/accelerometer#4 (4 comments by @alexshalamov, @anssiko, @dontcallmedom)
-
-
3 pull requests opened.
-
Add permission descriptor for Accelerometer API w3c/accelerometer#16, by @alexshalamov.
-
Fix bikeshed id's for LinearAccelerationSensor and GravitySensor w3c/accelerometer#15, by @alexshalamov.
-
Split Accelerometer interface w3c/accelerometer#14, by @alexshalamov.
-
-
3 pull requests merged.
-
Add permission descriptor for Accelerometer API w3c/accelerometer#16.
-
Fix bikeshed id's for LinearAccelerationSensor and GravitySensor w3c/accelerometer#15.
-
Split Accelerometer interface w3c/accelerometer#14.
-
-
2 pull requests received 15 new comments.
-
Split Accelerometer interface w3c/accelerometer#14 (14 comments by @alexshalamov, @anssiko, @kenchris, @pozdnyakov)
-
w3c/contact-picker
-
1 issue opened.
-
Add payerGivenName + payerFamilyName to PaymentAddress w3c/contact-picker#69, by @marcos-travel.
-
-
1 issue received 7 new comments.
-
Add payerGivenName + payerFamilyName to PaymentAddress w3c/contact-picker#69 (7 comments by @ianbjacobs, @lararennie, @marcoscaceres, @nickjshearer, @rsolomakhin, @zkoch)
-
w3c/html-media-capture
-
1 issue received 7 new comments.
-
1 pull request received 6 new comments.
-
Fix #4: Make @capture an enumerated attribute w3c/html-media-capture#6 (6 comments by @anssiko, @foolip, @hober)
-
w3c/ambient-light
-
1 issue opened.
-
Add description for use cases w3c/ambient-light#23, by @pozdnyakov.
-
-
2 issues closed.
-
Adapt ALS to the latest changes in the Generic Sensor API w3c/ambient-light#20.
-
API Name Objection w3c/ambient-light#14.
-
-
2 issues received 2 new comments.
-
Adapt ALS to the latest changes in the Generic Sensor API w3c/ambient-light#20 (1 comment by @anssiko)
-
2 pull requests opened.
-
Add pr-preview file w3c/ambient-light#22, by @anssiko.
-
Update ALS to latest generic sensor spec. w3c/ambient-light#21, by @tobie.
-
-
2 pull requests merged.
-
Update ALS to latest generic sensor spec. w3c/ambient-light#21.
-
Add pr-preview file w3c/ambient-light#22.
-
-
1 pull request received 3 new comments.
w3c/deviceorientation
-
4 issues opened.
-
DeviceMotionEvent.interval is nullable but must be initialized to 0 w3c/deviceorientation#39, by @reillyeon.
-
compassneedscalibration event - cannot confirm interoperability w3c/deviceorientation#38, by @gmandyam.
-
Is the editor's draft still maintained? w3c/deviceorientation#36, by @yell0wd0g.
-
Reach consensus on deprecation and removal of de facto standard init*Event() methods w3c/deviceorientation#35, by @reillyeon.
-
-
2 issues closed.
-
DeviceMotionEvent.interval is nullable but must be initialized to 0 w3c/deviceorientation#39.
-
Is the editor's draft still maintained? w3c/deviceorientation#36.
-
-
3 issues received 16 new comments.
-
Reach consensus on deprecation and removal of de facto standard init*Event() methods w3c/deviceorientation#35 (12 comments by @cdumez, @foolip, @khuey, @marcoscaceres, @reillyeon, @smaug----, @travisleithead)
-
Is the editor's draft still maintained? w3c/deviceorientation#36 (3 comments by @ashimura, @timvolodine, @yell0wd0g)
-
DeviceMotionEvent.interval is nullable but must be initialized to 0 w3c/deviceorientation#39 (1 comment by @reillyeon)
-
-
3 pull requests opened.
-
Update spec-source-orientation.html - clarify null case for motion w3c/deviceorientation#41, by @timvolodine.
-
Make interval IDL consistent with normative text. w3c/deviceorientation#40, by @reillyeon.
-
Rectify date spec-source-orientation.html w3c/deviceorientation#37, by @timvolodine.
-
-
2 pull requests merged.
-
Make interval IDL consistent with normative text. w3c/deviceorientation#40.
-
Rectify date spec-source-orientation.html w3c/deviceorientation#37.
-
-
2 pull requests received 7 new comments.
-
Add the ondeviceorientationabsolute event handler attribute w3c/deviceorientation#34 (5 comments by @ashimura, @foolip, @plehegar, @timvolodine)
-
Make interval IDL consistent with normative text. w3c/deviceorientation#40 (2 comments by @timvolodine)
-
w3c/battery
-
2 issues opened.
-
Allow use from within secure context and top-level browsing context only w3c/battery#10, by @anssiko.
-
Detect power saving mode w3c/battery#9, by @jimmywarting.
-
-
1 issue closed.
-
Mitigating potential privacy-invasive usage w3c/battery#5.
-
-
3 issues received 11 new comments.
-
Allow use from within secure context and top-level browsing context only w3c/battery#10 (2 comments by @anssiko, @riju)
w3c/geolocation
-
1 issue opened.
-
Suggest adding a PositionError entry for requests denied because of origin w3c/geolocation#11, by @yell0wd0g.
-
TR publications
-
6 documents published.
-
Media Capture Depth Stream Extensions published as a Working Draft. History of Media Capture Depth Stream Extensions
-
Wake Lock API published twice as a Working Draft. History of Wake Lock API
-
Media Capture from DOM Elements published 3 times as a Working Draft. History of Media Capture from DOM Elements
-
GitHub
w3c/sensors
-
3 issues opened.
-
Batching API for sensor readings w3c/sensors#171, by @pozdnyakov.
-
Provide the DeviceOrientation sensor w3c/sensors#170, by @pozdnyakov.
-
What if setting a negative frequency? w3c/sensors#169, by @Honry.
-
-
1 issue closed.
-
What if setting a negative frequency? w3c/sensors#169.
-
-
9 issues received 98 new comments.
-
Provide the DeviceOrientation sensor w3c/sensors#170 (45 comments by @alexshalamov, @kenchris, @pozdnyakov, @tobie)
-
Javascript 120Hz devicemotion events for high end inertial applications w3c/sensors#98 (18 comments by @adonikian, @maryammjd, @padenot, @tobie)
-
What if setting a negative frequency? w3c/sensors#169 (6 comments by @anssiko, @Honry, @pozdnyakov, @tobie)
-
Call 'onchange' on a Senor instance considering its own frequency hint w3c/sensors#152 (6 comments by @kenchris, @pozdnyakov, @tobie)
-
w3c/html-media-capture
-
1 issue opened.
-
Update test suite w3c/html-media-capture#7, by @anssiko.
-
-
1 issue closed.
-
VideoFacingModeEnum as the capture attribute's value w3c/html-media-capture#4.
-
-
1 issue received 3 new comments.
-
1 pull request opened.
-
Fix #4: Make @capture an enumerated attribute w3c/html-media-capture#6, by @anssiko.
-
-
1 pull request merged.
-
Fix #4: Make @capture an enumerated attribute w3c/html-media-capture#6.
-
-
1 pull request closed.
-
Use https links w3c/html-media-capture#5.
-
-
2 pull requests received 17 new comments.
-
Fix #4: Make @capture an enumerated attribute w3c/html-media-capture#6 (16 comments by @anssiko, @hober, @yell0wd0g)
-
w3c/accelerometer
-
2 issues opened.
-
No way to get isolated gravity w3c/accelerometer#13, by @kenchris.
-
"includesGravity" vs "includeGravity" w3c/accelerometer#12, by @Honry.
-
-
1 issue closed.
-
"includesGravity" vs "includeGravity" w3c/accelerometer#12.
-
-
1 issue received 2 new comments.
-
1 pull request opened.
-
Align Accelerometer interface with the Generic Sensor API w3c/accelerometer#11, by @alexshalamov.
-
-
1 pull request merged.
-
Align Accelerometer interface with the Generic Sensor API w3c/accelerometer#11.
-
-
1 pull request received 4 new comments.
-
Align Accelerometer interface with the Generic Sensor API w3c/accelerometer#11 (4 comments by @anssiko)
-
w3c/screen-wake-lock
-
1 issue opened.
-
Clarify wake lock state transitions when the device is manually locked w3c/screen-wake-lock#95, by @andrey-logvinov.
-
-
4 issues closed.
-
Review the Privacy & Security section w3c/screen-wake-lock#89.
-
The spec is unnecessarily strict in regard to promise handling w3c/screen-wake-lock#92.
-
Clarify wake lock state transitions when the device is manually locked w3c/screen-wake-lock#95.
-
TAG feedback on wake-lock API w3c/screen-wake-lock#85.
-
-
3 issues received 6 new comments.
-
The spec is unnecessarily strict in regard to promise handling w3c/screen-wake-lock#92 (4 comments by @andrey-logvinov, @marcoscaceres)
-
-
3 pull requests opened.
-
Review privacy and security section w3c/screen-wake-lock#97, by @andrey-logvinov.
-
Clarify wake lock applicability when the device is manually locked w3c/screen-wake-lock#96, by @andrey-logvinov.
-
Fix promise handling w3c/screen-wake-lock#94, by @andrey-logvinov.
-
-
3 pull requests merged.
-
Review privacy and security section w3c/screen-wake-lock#97.
-
Fix promise handling w3c/screen-wake-lock#94.
-
Clarify wake lock applicability when the device is manually locked w3c/screen-wake-lock#96.
-
-
1 pull request received 2 new comments.
w3c/deviceorientation
-
1 pull request opened.
-
Add the ondeviceorientationabsolute event handler attribute w3c/deviceorientation#34, by @foolip.
-
-
1 pull request received 1 new comment.
-
Add the ondeviceorientationabsolute event handler attribute w3c/deviceorientation#34 (1 comment by @foolip)
-
w3c/ambient-light
-
1 issue opened.
-
Adapt ALS to the latest changes in the Generic Sensor API w3c/ambient-light#20, by @anssiko.
-
-
2 issues received 2 new comments.
w3c/geolocation
-
1 issue opened.
-
Disable geolocation by default in cross-origin iframes w3c/geolocation#10, by @raymeskhoury.
-
w3c/magnetometer
-
2 issues closed.
-
Model duplicates WebIDL w3c/magnetometer#4.
-
Who is you, we, etc.? w3c/magnetometer#7.
-
-
6 issues received 12 new comments.
-
Local coordinates could use further detail/examples w3c/magnetometer#19 (2 comments by @anssiko, @markafoltz)
-
2 pull requests opened.
-
Add RawMagnetometer, for uncalibrated readings. w3c/magnetometer#21, by @riju.
-
Adapt magnetometer after remove_reading w3c/magnetometer#20, by @riju.
-
-
1 pull request merged.
-
Adapt magnetometer after remove_reading w3c/magnetometer#20.
-
-
1 pull request closed.
-
Add support for raw w3c/magnetometer#17.
-
-
3 pull requests received 5 new comments.
w3c/proximity
-
2 pull requests opened.
-
Define distance, max, and near in the model, add cross-references w3c/proximity#21, by @anssiko.
-
Adapt Proximity to the latest changes in the Generic Sensor API w3c/proximity#20, by @riju.
-
-
2 pull requests merged.
-
Define distance, max, and near in the model, add cross-references w3c/proximity#21.
-
Adapt Proximity to the latest changes in the Generic Sensor API w3c/proximity#20.
-
-
2 pull requests received 14 new comments.
-
Adapt Proximity to the latest changes in the Generic Sensor API w3c/proximity#20 (13 comments by @anssiko, @pozdnyakov, @riju)
-
Define distance, max, and near in the model, add cross-references w3c/proximity#21 (1 comment by @riju)
-
w3c/gyroscope
-
1 pull request merged.
-
Adapt Gyroscope to the latest changes in the Generic Sensor API w3c/gyroscope#10.
-
-
1 pull request received 1 new comment.
-
Adapt Gyroscope to the latest changes in the Generic Sensor API w3c/gyroscope#10 (1 comment by @pozdnyakov)
-
TR publications
-
4 documents published.
-
Generic Sensor API published as a Working Draft. History of Generic Sensor API
-
Wake Lock API published as a Working Draft. History of Wake Lock API
-
MediaStream Image Capture published as a Working Draft. History of MediaStream Image Capture
-
Network Service Discovery published as a Note. History of Network Service Discovery
-
Participants
-
1 organization joined.
-
CoSMo Software Consulting Pte Ltd joined.
-
GitHub
w3c/sensors
-
7 issues opened.
-
Reading attributes at different sensor states w3c/sensors#168, by @pozdnyakov.
-
Meta: figure out why travis fails for pull requests w3c/sensors#165, by @tobie.
-
Find a clearer name for the sensor concept w3c/sensors#162, by @pozdnyakov.
-
Fix Sensor.start() operation description w3c/sensors#161, by @pozdnyakov.
-
Find a better name for 'unconnected' state w3c/sensors#160, by @pozdnyakov.
-
Sensor.timestamp must be nullable w3c/sensors#159, by @pozdnyakov.
-
DOMExceptions when calling stop/start on already stopped/started sensor w3c/sensors#158, by @darktears.
-
-
16 issues closed.
-
Meta: figure out why travis fails for pull requests w3c/sensors#165.
-
Fix Sensor.start() operation description w3c/sensors#161.
-
Sensor.timestamp must be nullable w3c/sensors#159.
-
Frequency readout allows fingerprinting sensors, privacy. w3c/sensors#99.
-
Malicious use of the phone's Gyroscope w3c/sensors#112.
-
Updating privacy considerations - accounting w3c/sensors#148.
-
Revoking user permission w3c/sensors#146.
-
Updating security and privacy considerations w3c/sensors#117.
-
Clarify scope of generic sensor w3c/sensors#130.
-
Should the enum SensorState have nosensor ? w3c/sensors#104.
-
Move default sensor check to start() w3c/sensors#128.
-
Remove side-effects from Sensor Constructor w3c/sensors#138.
-
-
11 issues received 50 new comments.
-
Find a better name for 'unconnected' state w3c/sensors#160 (21 comments by @kenchris, @pozdnyakov, @tobie)
-
DOMExceptions when calling stop/start on already stopped/started sensor w3c/sensors#158 (7 comments by @darktears, @kenchris, @pozdnyakov, @tobie)
-
Javascript 120Hz devicemotion events for high end inertial applications w3c/sensors#98 (5 comments by @lukes3315, @tobie)
-
Call 'onchange' on a Senor instance considering its own frequency hint w3c/sensors#152 (1 comment by @tobie)
-
-
6 pull requests opened.
-
Fix broken deploy story. w3c/sensors#167, by @tobie.
-
Add script to easily publish to /TR/. w3c/sensors#166, by @tobie.
-
Make start()/stop() fail silently instead of throwing w3c/sensors#164, by @tobie.
-
Make timestamp nullable w3c/sensors#163, by @tobie.
-
Sync refs with the Permissions spec changes w3c/sensors#157, by @anssiko.
-
Large rewrite/refactoring of the spec w3c/sensors#156, by @tobie.
-
-
6 pull requests merged.
-
Add script to easily publish to /TR/. w3c/sensors#166.
-
Fix broken deploy story. w3c/sensors#167.
-
Make start()/stop() fail silently instead of throwing w3c/sensors#164.
-
Make timestamp nullable w3c/sensors#163.
-
Sync refs with the Permissions spec changes w3c/sensors#157.
-
Large rewrite/refactoring of the spec w3c/sensors#156.
-
-
2 pull requests received 5 new comments.
w3c/gyroscope
-
1 pull request opened.
-
Adapt Gyroscope to the latest changes in the Generic Sensor API w3c/gyroscope#10, by @pozdnyakov.
-
-
1 pull request received 17 new comments.
-
Adapt Gyroscope to the latest changes in the Generic Sensor API w3c/gyroscope#10 (17 comments by @anssiko, @pozdnyakov, @tobie)
-
w3c/html-media-capture
-
1 issue received 1 new comment.
-
VideoFacingModeEnum as the capture attribute's value w3c/html-media-capture#4 (1 comment by @anssiko)
-
w3c/screen-wake-lock
-
2 issues opened.
-
The spec is unnecessarily strict in regard to promise handling w3c/screen-wake-lock#92, by @andrey-logvinov.
-
Fix respec warnings w3c/screen-wake-lock#91, by @andrey-logvinov.
-
-
2 issues closed.
-
"System" wake lock use cases w3c/screen-wake-lock#86.
-
Fix respec warnings w3c/screen-wake-lock#91.
-
-
3 issues received 4 new comments.
-
The spec is unnecessarily strict in regard to promise handling w3c/screen-wake-lock#92 (1 comment by @marcoscaceres)
-
1 pull request opened.
-
chore: fix ReSpec warnings (closes #91) w3c/screen-wake-lock#93, by @marcoscaceres.
-
-
1 pull request merged.
-
chore: fix ReSpec warnings (closes #91) w3c/screen-wake-lock#93.
-
-
1 pull request received 2 new comments.
-
chore: fix ReSpec warnings (closes #91) w3c/screen-wake-lock#93 (2 comments by @andrey-logvinov, @marcoscaceres)
-
w3c/battery
-
1 issue opened.
-
Respec warns about missing <dfn>'s in contiguous webidl w3c/battery#7, by @andrey-logvinov.
-
-
1 issue closed.
-
Respec warns about missing <dfn>'s in contiguous webidl w3c/battery#7.
-
-
2 issues received 2 new comments.
-
1 pull request opened.
-
Fix ReSpec warnings w3c/battery#8, by @anssiko.
-
-
1 pull request merged.
-
Fix ReSpec warnings w3c/battery#8.
-
-
1 pull request received 1 new comment.
w3c/vibration
-
1 pull request opened.
-
Fix ReSpec warnings w3c/vibration#18, by @anssiko.
-
-
1 pull request merged.
-
Fix ReSpec warnings w3c/vibration#18.
-
-
1 pull request received 1 new comment.
w3c/accelerometer
-
1 issue received 2 new comments.
-
includeGravity parameter turns low-level sensor into high-level fused one. w3c/accelerometer#3 (2 comments by @tobie)
-
w3c/magnetometer
-
1 issue received 1 new comment.
-
1 pull request merged.
-
Fix typos: remove duplicated words w3c/magnetometer#15.
-
-
1 pull request closed.
-
Fixup example to use JS conventions w3c/magnetometer#8.
-
-
2 pull requests received 2 new comments.