Devices and Sensors Working Group - Activity in 2016
No matches.
TR publications
-
13 documents published.
-
MediaStream Recording published 6 times as a Working Draft. History of MediaStream Recording
-
Wake Lock API published as a Working Draft. History of Wake Lock API
-
MediaStream Image Capture published 5 times as a Working Draft. History of MediaStream Image Capture
-
Audio Output Devices API published as a Working Draft. History of Audio Output Devices API
-
GitHub
w3c/magnetometer
-
2 issues opened.
-
Local coordinates could use further detail/examples w3c/magnetometer#19, by @markafoltz.
-
Shouldn't need Web Service to compute declination w3c/magnetometer#18, by @markafoltz.
-
w3c/sensors
-
3 issues opened.
-
Sensor.timeStamp could be clarified w3c/sensors#155, by @markafoltz.
-
Need API to report platform accuracy changes? w3c/sensors#154, by @markafoltz.
-
Don't allocate response objects to avoid triggering GC w3c/sensors#153, by @tobie.
-
-
4 issues closed.
-
Add abstract operation for constructing a SensorReading w3c/sensors#134.
-
SensorReadings must be immutable. w3c/sensors#147.
-
Should SensorReading be a dictionary? w3c/sensors#150.
-
SensorErrorEvent IDL doesn't match Blink w3c/sensors#142.
-
-
6 issues received 43 new comments.
-
Don't allocate response objects to avoid triggering GC w3c/sensors#153 (30 comments by @alexshalamov, @Maksims, @pozdnyakov, @rwaldron, @tobie)
-
Call 'onchange' on a Senor instance considering its own frequency hint w3c/sensors#152 (8 comments by @foolip, @pozdnyakov, @tobie)
-
w3c/ambient-light
-
1 issue opened.
-
Auto reporting mode is not defined w3c/ambient-light#19, by @markafoltz.
-
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 @legion80)
-
w3c/screen-wake-lock
-
1 issue opened.
-
Review the Privacy & Security section w3c/screen-wake-lock#89, by @andrey-logvinov.
-
-
4 issues closed.
-
Several defined terms are way too generic w3c/screen-wake-lock#69.
-
Current API not friendly to components w3c/screen-wake-lock#55.
-
System lock should be specified w3c/screen-wake-lock#50.
-
Plans for v2 w3c/screen-wake-lock#87.
-
-
3 issues received 3 new comments.
-
2 pull requests opened.
-
Fix an overly generic definition w3c/screen-wake-lock#90, by @andrey-logvinov.
-
Spec update w3c/screen-wake-lock#88, by @andrey-logvinov.
-
-
2 pull requests merged.
-
Fix an overly generic definition w3c/screen-wake-lock#90.
-
Spec update w3c/screen-wake-lock#88.
-
-
1 pull request received 5 new comments.
w3c/deviceorientation
-
1 issue opened.
-
Security/privacy consideration: cross-origin linkage w3c/deviceorientation#33, by @wseltzer.
-
TR publications
-
3 documents published.
-
MediaStream Image Capture published twice as a Working Draft. History of MediaStream Image Capture
-
Audio Output Devices API published as a Working Draft. History of Audio Output Devices API
-
GitHub
w3c/screen-wake-lock
-
1 issue opened.
-
Plans for v2 w3c/screen-wake-lock#87, by @andrey-logvinov.
-
-
2 issues received 2 new comments.
w3c/magnetometer
-
1 issue opened.
-
Provide API to access uncalibrated magnetometer values w3c/magnetometer#16, by @alexshalamov.
-
-
1 issue received 29 new comments.
-
Provide API to access uncalibrated magnetometer values w3c/magnetometer#16 (29 comments by @alexshalamov, @anssiko, @pozdnyakov, @riju, @rwaldron, @tobie)
-
-
1 pull request opened.
-
Add support for raw w3c/magnetometer#17, by @riju.
-
w3c/sensors
-
5 issues opened.
-
Call 'onchange' on a Senor instance considering its own frequency hint w3c/sensors#152, by @pozdnyakov.
-
Exposing secondary values in the SensorReading w3c/sensors#151, by @tobie.
-
Should SensorReading be a dictionary? w3c/sensors#150, by @tobie.
-
Issues caused by visibility state restriction semantics w3c/sensors#149, by @rwaldron.
-
Updating privacy considerations - accounting w3c/sensors#148, by @lknik.
-
-
2 issues closed.
-
Using PIA terminology w3c/sensors#144.
-
Add prose for on{error|change} w3c/sensors#135.
-
-
12 issues received 110 new comments.
-
Should we request permission when sensor is not supported by the platform? w3c/sensors#145 (54 comments by @lknik, @maryammjd, @owencm, @pozdnyakov, @raymeskhoury, @tobie)
-
granularity of Permission name for concrete/ fusion sensors w3c/sensors#132 (18 comments by @lknik, @maryammjd, @tobie)
-
Call 'onchange' on a Senor instance considering its own frequency hint w3c/sensors#152 (9 comments by @pozdnyakov, @rwaldron, @tobie)
-
SensorErrorEvent IDL doesn't match Blink w3c/sensors#142 (6 comments by @foolip, @pozdnyakov, @tobie)
-
-
1 pull request merged.
-
Add "impact" w3c/sensors#143.
-
w3c/ambient-light
-
2 issues opened.
-
Is "frequency" available in ALS? w3c/ambient-light#18, by @Honry.
-
Should we really redefine AmbientLightSensor.reading? w3c/ambient-light#17, by @tobie.
-
-
2 issues closed.
-
Is "frequency" available in ALS? w3c/ambient-light#18.
-
Should we really redefine AmbientLightSensor.reading? w3c/ambient-light#17.
-
-
3 issues received 19 new comments.
-
What illuminance value should be reported for stopped sensor? w3c/ambient-light#15 (9 comments by @alexshalamov, @pozdnyakov, @rwaldron, @tobie)
-
Should we really redefine AmbientLightSensor.reading? w3c/ambient-light#17 (8 comments by @annevk, @anssiko, @dontcallmedom, @tobie)
-
w3c/battery
-
1 issue received 13 new comments.
-
Mitigating potential privacy-invasive usage w3c/battery#5 (13 comments by @anssiko, @cpeterso, @lknik, @marcoscaceres)
-
TR publications
-
14 documents published.
-
Vibration API (Second Edition) published as a Recommendation. History of Vibration API (Second Edition)
-
Audio Output Devices API published twice as a Working Draft. History of Audio Output Devices API
-
MediaStream Recording published as a Working Draft. History of MediaStream Recording
-
MediaStream Image Capture published 10 times as a Working Draft. History of MediaStream Image Capture
-
Participants
-
1 participant joined.
-
Maryam Mehrnezhad (W3C Invited Experts) joined.
-
-
1 organization joined.
-
Mitsubishi Electric Corporation joined.
-
GitHub
w3c/ambient-light
-
1 issue opened.
-
Available in workers? w3c/ambient-light#16, by @torgo.
-
-
1 issue closed.
-
Permissions for verbose readout of ALS w3c/ambient-light#10.
-
-
4 issues received 21 new comments.
-
What illuminance value should be reported for stopped sensor? w3c/ambient-light#15 (15 comments by @alexshalamov, @rwaldron, @tobie)
-
w3c/sensors
-
10 issues opened.
-
SensorReadings must be immutable. w3c/sensors#147, by @tobie.
-
Revoking user permission w3c/sensors#146, by @alexshalamov.
-
Should we request permission when sensor is not supported by the platform? w3c/sensors#145, by @alexshalamov.
-
Using PIA terminology w3c/sensors#144, by @lknik.
-
SensorErrorEvent IDL doesn't match Blink w3c/sensors#142, by @foolip.
-
Multiple sensor & sensor change discoverability w3c/sensors#141, by @rektide.
-
Example code omits call to .start() w3c/sensors#140, by @jyasskin.
-
Split parameters between start() and constructor w3c/sensors#139, by @alexshalamov.
-
Remove side-effects from Sensor Constructor w3c/sensors#138, by @pozdnyakov.
-
Should we use OnErrorEventHandler error handler instead of EventHandler? w3c/sensors#137, by @alexshalamov.
-
-
14 issues closed.
-
Should SensorReadingEvent carry reading payload? w3c/sensors#103.
-
Validate state transitions. w3c/sensors#113.
-
Clarify terminology w3c/sensors#78.
-
Constructing a SensorReading with SensorReadingInit is non-optional? w3c/sensors#116.
-
WebIDL ref label is "Level 1" but links to "Level 2" w3c/sensors#108.
-
Naming of derivative sensors are very inconsistent w3c/sensors#131.
-
Example code omits call to .start() w3c/sensors#140.
-
SensorReadingEventInit's reading member needs to be required w3c/sensors#129.
-
Prepare licensing change in spec w3c/sensors#91.
-
Multiple sensor & sensor change discoverability w3c/sensors#141.
-
20 issues received 41 new comments.
-
Reporting mode and polling frequency w3c/sensors#126 (14 comments by @alexshalamov, @pozdnyakov, @tobie)
-
Possibility of cross-domain communication using frequency in periodic reporting mode w3c/sensors#100 (1 comment by @tobie)
-
Should we request permission when sensor is not supported by the platform? w3c/sensors#145 (1 comment by @lknik)
-
start() to return a cancellable promise that resolves on first reading w3c/sensors#94 (1 comment by @tobie)
-
Should we use OnErrorEventHandler error handler instead of EventHandler? w3c/sensors#137 (1 comment by @tobie)
-
Constructing a SensorReading with SensorReadingInit is non-optional? w3c/sensors#116 (1 comment by @tobie)
-
-
1 pull request opened.
-
Add "impact" w3c/sensors#143, by @lknik.
-
w3c/battery
-
1 issue received 11 new comments.
-
Mitigating potential privacy-invasive usage w3c/battery#5 (11 comments by @anssiko, @dontcallmedom, @lknik)
-
-
1 pull request merged.
-
Use https links w3c/battery#6.
-
-
1 pull request received 1 new comment.
w3c/screen-wake-lock
-
1 issue received 1 new comment.
w3c/accelerometer
-
1 issue opened.
-
Rename AccelerometerReading properties to x, y, z w3c/accelerometer#9, by @anssiko.
-
-
2 issues closed.
-
Rename AccelerometerReading properties to x, y, z w3c/accelerometer#9.
-
API Name Objection w3c/accelerometer#5.
-
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
Fix #9: Rename AccelerometerReading properties to x, y, z w3c/accelerometer#10, by @anssiko.
-
Rename AccelerometerSensor interface to Accelerometer w3c/accelerometer#8, by @alexshalamov.
-
-
2 pull requests merged.
-
Fix #9: Rename AccelerometerReading properties to x, y, z w3c/accelerometer#10.
-
Rename AccelerometerSensor interface to Accelerometer w3c/accelerometer#8.
-
-
2 pull requests received 6 new comments.
-
Rename AccelerometerSensor interface to Accelerometer w3c/accelerometer#8 (5 comments by @anssiko, @dontcallmedom)
-
Fix #9: Rename AccelerometerReading properties to x, y, z w3c/accelerometer#10 (1 comment by @alexshalamov)
-
w3c/gyroscope
-
1 issue opened.
-
Rename GyroscopeReading properties to x, y, z w3c/gyroscope#8, by @anssiko.
-
-
2 issues closed.
-
Rename GyroscopeReading properties to x, y, z w3c/gyroscope#8.
-
API Name Objection w3c/gyroscope#4.
-
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
Fix #8: Rename GyroscopeReading properties to x, y, z w3c/gyroscope#9, by @anssiko.
-
Rename 'GyroscopeSensor' to 'Gyroscope' w3c/gyroscope#7, by @pozdnyakov.
-
-
2 pull requests merged.
-
Fix #8: Rename GyroscopeReading properties to x, y, z w3c/gyroscope#9.
-
Rename 'GyroscopeSensor' to 'Gyroscope' w3c/gyroscope#7.
-
-
2 pull requests received 3 new comments.
w3c/proximity
-
1 issue opened.
-
Issues about the near attribute w3c/proximity#18, by @Honry.
-
-
1 issue closed.
-
Issues about the near attribute w3c/proximity#18.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Fix typo in 'near' attribute and remove 'in centimeters' in 'near' attribute w3c/proximity#19, by @MichaelKohler.
-
-
1 pull request merged.
-
1 pull request received 2 new comments.
-
Fix typo in 'near' attribute and remove 'in centimeters' in 'near' attribute w3c/proximity#19 (2 comments by @anssiko, @dontcallmedom)
-
w3c/vibration
-
2 issues opened.
-
Add vibration strength control w3c/vibration#17, by @laukstein.
-
Accessible Platform Architectures WG feedback w3c/vibration#16, by @anssiko.
-
w3c/magnetometer
-
1 pull request opened.
-
Fix typos: remove duplicated words w3c/magnetometer#15, by @Honry.
-
TR publications
-
10 documents published.
-
MediaStream Image Capture published 6 times as a Working Draft. History of MediaStream Image Capture
-
MediaStream Recording published as a Working Draft. History of MediaStream Recording
-
Accelerometer Sensor published as a First Public Working Draft. History of Accelerometer Sensor
-
Gyroscope Sensor published as a First Public Working Draft. History of Gyroscope Sensor
-
Magnetometer Sensor published as a First Public Working Draft. History of Magnetometer Sensor
-
GitHub
w3c/sensors
-
11 issues opened.
-
Add prose for on{error|change} w3c/sensors#135, by @anssiko.
-
Add abstract operation for constructing a SensorReading w3c/sensors#134, by @anssiko.
-
Relation to Feature Policy w3c/sensors#133, by @dontcallmedom.
-
granularity of Permission name for concrete/ fusion sensors w3c/sensors#132, by @riju.
-
Naming of derivative sensors are very inconsistent w3c/sensors#131, by @kenchris.
-
Clarify scope of generic sensor w3c/sensors#130, by @dontcallmedom.
-
SensorReadingEventInit's reading member needs to be required w3c/sensors#129, by @foolip.
-
Move default sensor check to start() w3c/sensors#128, by @pozdnyakov.
-
Why was namespacing dropped? w3c/sensors#127, by @rwaldron.
-
Reporting mode and polling frequency w3c/sensors#126, by @pozdnyakov.
-
3 issues closed.
-
Does SensorReading always need a timeStamp ? w3c/sensors#105.
-
Why was namespacing dropped? w3c/sensors#127.
-
Event object in error callback w3c/sensors#111.
-
-
1 issue reopened.
-
Why was namespacing dropped? w3c/sensors#127, by @anssiko.
-
-
13 issues received 37 new comments.
-
Why was namespacing dropped? w3c/sensors#127 (12 comments by @anssiko, @domenic, @marcoscaceres, @riju, @rwaldron, @tobie)
-
Naming of derivative sensors are very inconsistent w3c/sensors#131 (5 comments by @anssiko, @kenchris, @rwaldron, @tobie)
-
Construct Sensor Object algorithm is doing weird things with frequency w3c/sensors#125 (4 comments by @bzbarsky, @rwaldron, @tobie)
-
granularity of Permission name for concrete/ fusion sensors w3c/sensors#132 (3 comments by @anssiko, @lknik, @riju)
-
Constructing a SensorReading with SensorReadingInit is non-optional? w3c/sensors#116 (1 comment by @anssiko)
-
Simplify extension of the Permissions API for concrete sensor implementations w3c/sensors#22 (1 comment by @anssiko)
-
API must allow Web devs to easily create fused sensors in JS with an API consistant with native sensors w3c/sensors#42 (1 comment by @kenchris)
-
w3c/gyroscope
-
3 issues opened.
-
Address DeviceOrientation issue number 4 w3c/gyroscope#6, by @tobie.
-
Change reporting mode to "periodic" w3c/gyroscope#5, by @anssiko.
-
API Name Objection w3c/gyroscope#4, by @rwaldron.
-
-
1 issue closed.
-
Change reporting mode to "periodic" w3c/gyroscope#5.
-
-
1 issue reopened.
-
API Name Objection w3c/gyroscope#4, by @riju.
-
-
1 issue received 1 new comment.
w3c/accelerometer
-
4 issues opened.
-
Address DeviceOrientation issue #4 w3c/accelerometer#7, by @tobie.
-
Change reporting mode to "periodic" w3c/accelerometer#6, by @anssiko.
-
API Name Objection w3c/accelerometer#5, by @rwaldron.
-
Integration in Permission API w3c/accelerometer#4, by @dontcallmedom.
-
-
1 issue closed.
-
Change reporting mode to "periodic" w3c/accelerometer#6.
-
-
1 issue reopened.
-
API Name Objection w3c/accelerometer#5, by @riju.
-
-
2 issues received 11 new comments.
-
includeGravity parameter turns low-level sensor into high-level fused one. w3c/accelerometer#3 (10 comments by @alexshalamov, @anssiko, @tobie)
-
w3c/magnetometer
-
3 issues opened.
-
Should we expose heading? w3c/magnetometer#14, by @anssiko.
-
Change reporting mode to "periodic" w3c/magnetometer#13, by @anssiko.
-
API Name Objection w3c/magnetometer#12, by @rwaldron.
-
-
4 issues closed.
-
API Name Objection w3c/magnetometer#12.
-
Why magneticFieldX instead of x? w3c/magnetometer#3.
-
Change reporting mode to "periodic" w3c/magnetometer#13.
-
Conformance Classes w3c/magnetometer#9.
-
-
3 issues received 8 new comments.
-
Why magneticFieldX instead of x? w3c/magnetometer#3 (6 comments by @anssiko, @marcoscaceres, @rwaldron)
-
w3c/ambient-light
-
2 issues opened.
-
What illuminance value should be reported for stopped sensor? w3c/ambient-light#15, by @alexshalamov.
-
API Name Objection w3c/ambient-light#14, by @rwaldron.
-
-
3 issues received 3 new comments.
-
What illuminance value should be reported for stopped sensor? w3c/ambient-light#15 (1 comment by @anssiko)
-
w3c/geolocation
-
1 issue closed.
-
Make the API promise compatible w3c/geolocation#8.
-
-
1 issue received 1 new comment.
w3c/screen-wake-lock
-
2 issues opened.
-
"System" wake lock use cases w3c/screen-wake-lock#86, by @triblondon.
-
TAG feedback on wake-lock API w3c/screen-wake-lock#85, by @travisleithead.
-
-
2 issues received 3 new comments.
TR publications
-
16 documents published.
-
Vibration API published as a Proposed Edited Recommendation. History of Vibration API
-
MediaStream Recording published twice as a Working Draft. History of MediaStream Recording
-
Ambient Light Sensor published as a Working Draft. History of Ambient Light Sensor
-
Generic Sensor API published as a Working Draft. History of Generic Sensor API
-
Media Capture from DOM Elements published 3 times as a Working Draft. History of Media Capture from DOM Elements
-
MediaStream Image Capture published 7 times as a Working Draft. History of MediaStream Image Capture
-
Wake Lock API published as a Working Draft. History of Wake Lock API
-
GitHub
w3c/sensors
-
2 issues opened.
-
Construct Sensor Object algorithm is doing weird things with frequency w3c/sensors#125, by @bzbarsky.
-
Clarifying the behavior of suspending or pausing sensors upon inactivity. w3c/sensors#124, by @bbernhar.
-
-
3 issues closed.
-
Feature Detection of Hardware Features - privacy considerations w3c/sensors#118.
-
Out of band communication w3c/sensors#119.
-
4 issues received 8 new comments.
-
Construct Sensor Object algorithm is doing weird things with frequency w3c/sensors#125 (2 comments by @bzbarsky, @rwaldron)
-
1 pull request opened.
-
Consistently use event.reading in examples w3c/sensors#123, by @jscissr.
-
-
3 pull requests merged.
-
Out of band communication. Fixes gh-119 w3c/sensors#122.
-
Consistently use event.reading in examples w3c/sensors#123.
-
3 pull requests received 6 new comments.
-
Additional text added to, per Feature Detection of Hardware Features- privacy considerations. Closes gh-118 w3c/sensors#121 (1 comment by @dontcallmedom)
w3c/ambient-light
-
1 issue opened.
-
Security and Privacy considerations for ALS w3c/ambient-light#13, by @lknik.
-
w3c/accelerometer
-
2 issues opened.
-
includeGravity parameter turns low-level sensor into high-level fused one. w3c/accelerometer#3, by @tobie.
-
Normative reference to WebIDL-1 is missing w3c/accelerometer#2, by @dontcallmedom.
-
-
1 issue closed.
-
Normative reference to WebIDL-1 is missing w3c/accelerometer#2.
-
-
1 issue received 4 new comments.
-
Normative reference to WebIDL-1 is missing w3c/accelerometer#2 (4 comments by @dontcallmedom, @marcoscaceres)
-
w3c/magnetometer
-
1 issue opened.
-
Normative reference to WebIDL-1 is missing w3c/magnetometer#11, by @dontcallmedom.
-
-
2 issues closed.
-
Normative reference to WebIDL-1 is missing w3c/magnetometer#11.
-
Limitations of Magnetometer Sensors w3c/magnetometer#6.
-
-
2 issues received 3 new comments.
-
1 pull request opened.
-
Fixes #6. mark Limitations section text as non-normative. w3c/magnetometer#10, by @riju.
-
-
1 pull request merged.
-
Fixes #6. mark Limitations section text as non-normative. w3c/magnetometer#10.
-
-
1 pull request received 2 new comments.
w3c/gyroscope
-
1 issue opened.
-
Normative reference to WebIDL-1 is missing w3c/gyroscope#3, by @dontcallmedom.
-
-
1 issue closed.
-
Normative reference to WebIDL-1 is missing w3c/gyroscope#3.
-
-
1 issue received 1 new comment.
w3c/geolocation
-
2 issues opened.
-
IDL is wrong w3c/geolocation#9, by @marcoscaceres.
-
Make the API promise compatible w3c/geolocation#8, by @marcoscaceres.
-
-
1 issue received 3 new comments.
w3c/battery
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Use https links w3c/battery#6, by @dontcallmedom.
-
w3c/vibration
-
2 issues opened.
-
Block navigator.vibrate in cross-origin iframes w3c/vibration#15, by @dontcallmedom.
-
shouldn't the title be "Vibration API (Second Edition)"? w3c/vibration#14, by @dret.
-
-
1 issue closed.
-
shouldn't the title be "Vibration API (Second Edition)"? w3c/vibration#14.
-
-
3 issues received 6 new comments.
-
Updating privacy considerations - recovery of two identifiers w3c/vibration#12 (4 comments by @anssiko, @dontcallmedom, @lknik)
-
shouldn't the title be "Vibration API (Second Edition)"? w3c/vibration#14 (1 comment by @dontcallmedom)
-
-
1 pull request opened.
-
Update administrative date and upgrade links to https w3c/vibration#13, by @dontcallmedom.
-
-
1 pull request merged.
-
Update administrative date and upgrade links to https w3c/vibration#13.
-
-
1 pull request received 1 new comment.
w3c/proximity
-
1 issue opened.
-
Security/privacy considerations w3c/proximity#17, by @lknik.
-
-
1 issue received 1 new comment.
w3c/screen-wake-lock
-
2 issues opened.
-
More diplay power modes w3c/screen-wake-lock#84, by @dontcallmedom.
-
Consider restricting Wake Lock API to Secure Contexts w3c/screen-wake-lock#82, by @andrey-logvinov.
-
-
2 issues received 3 new comments.
-
Consider restricting Wake Lock API to Secure Contexts w3c/screen-wake-lock#82 (2 comments by @andrey-logvinov, @dontcallmedom)
-
-
1 pull request opened.
-
Use https links w3c/screen-wake-lock#83, by @dontcallmedom.
-
-
1 pull request merged.
-
Use https links w3c/screen-wake-lock#83.
-
-
1 pull request received 1 new comment.
w3c/html-media-capture
-
1 pull request opened.
-
Use https links w3c/html-media-capture#5, by @dontcallmedom.
-
TR publications
-
8 documents published.
-
Battery Status API published as a Candidate Recommendation Snapshot. History of Battery Status API
-
MediaStream Image Capture published as a Working Draft. History of MediaStream Image Capture
-
Proximity Sensor published as a Working Draft. History of Proximity Sensor
-
Audio Output Devices API published as a Working Draft. History of Audio Output Devices API
-
Media Capture from DOM Elements published as a Working Draft. History of Media Capture from DOM Elements
-
Screen Capture published as a Working Draft. History of Screen Capture
-
Wake Lock API published as a Working Draft. History of Wake Lock API
-
Media Capture Depth Stream Extensions published as a Working Draft. History of Media Capture Depth Stream Extensions
-
Participants
-
1 organization joined.
-
Ecole Mohammadia d'Ingenieurs Rabat (EMI) joined.
-
GitHub
w3c/sensors
-
5 issues opened.
-
Privacy - identifying parameters w3c/sensors#120, by @lknik.
-
Out of band communication w3c/sensors#119, by @lknik.
-
Feature Detection of Hardware Features - privacy considerations w3c/sensors#118, by @lknik.
-
Updating security and privacy considerations w3c/sensors#117, by @lknik.
-
Constructing a SensorReading with SensorReadingInit is non-optional? w3c/sensors#116, by @bbernhar.
-
-
1 issue received 5 new comments.
-
2 pull requests opened.
-
Out of band communication. Fixes gh-119 w3c/sensors#122, by @rwaldron.
-
-
1 pull request received 2 new comments.
-
Additional text added to, per Feature Detection of Hardware Features- privacy considerations. Closes gh-118 w3c/sensors#121 (2 comments by @rwaldron)
-
w3c/magnetometer
-
8 issues opened.
-
Conformance Classes w3c/magnetometer#9, by @marcoscaceres.
-
Who is you, we, etc.? w3c/magnetometer#7, by @marcoscaceres.
-
Limitations of Magnetometer Sensors w3c/magnetometer#6, by @marcoscaceres.
-
Permission w3c/magnetometer#5, by @marcoscaceres.
-
Model duplicates WebIDL w3c/magnetometer#4, by @marcoscaceres.
-
Why magneticFieldX instead of x? w3c/magnetometer#3, by @marcoscaceres.
-
Security and Privacy Considerations w3c/magnetometer#2, by @marcoscaceres.
-
Privacy implications? w3c/magnetometer#1, by @chaals.
-
-
3 issues received 4 new comments.
-
1 pull request opened.
-
Fixup example to use JS conventions w3c/magnetometer#8, by @marcoscaceres.
-
-
1 pull request received 1 new comment.
w3c/ambient-light
-
1 issue opened.
-
Light-level deferred to Media Queries Level 5 w3c/ambient-light#12, by @lknik.
-
-
1 pull request opened.
-
Remove Conformance section w3c/ambient-light#11, by @riju.
-
-
1 pull request closed.
-
Remove Conformance section w3c/ambient-light#11.
-
w3c/screen-wake-lock
-
12 issues opened.
-
Update security and privacy considerations w3c/screen-wake-lock#78, by @lknik.
-
Security and Privacy considerations about safety w3c/screen-wake-lock#77, by @lknik.
-
"Implementation status" does not link anywhere w3c/screen-wake-lock#76, by @domenic.
-
"Same origin" should reference the definition w3c/screen-wake-lock#75, by @domenic.
-
Typo: extra spaces after [ w3c/screen-wake-lock#74, by @domenic.
-
Typo: "it's" -> "its" w3c/screen-wake-lock#73, by @domenic.
-
"user agent" -> "the user agent" w3c/screen-wake-lock#72, by @domenic.
-
Typo: "form" -> "from" w3c/screen-wake-lock#71, by @domenic.
-
Typo: extra space w3c/screen-wake-lock#70, by @domenic.
-
Several defined terms are way too generic w3c/screen-wake-lock#69, by @domenic.
-
3.1 attributes appears to be rendering wrong w3c/screen-wake-lock#68, by @domenic.
-
Usecase of keeping WiFi and cellular radio not covered w3c/screen-wake-lock#67, by @leolux.
-
-
10 issues closed.
-
Usecase of keeping WiFi and cellular radio not covered w3c/screen-wake-lock#67.
-
"Same origin" should reference the definition w3c/screen-wake-lock#75.
-
3.1 attributes appears to be rendering wrong w3c/screen-wake-lock#68.
-
Typo: extra spaces after [ w3c/screen-wake-lock#74.
-
Typo: extra space w3c/screen-wake-lock#70.
-
Typo: "form" -> "from" w3c/screen-wake-lock#71.
-
"user agent" -> "the user agent" w3c/screen-wake-lock#72.
-
Typo: "it's" -> "its" w3c/screen-wake-lock#73.
-
Security and Privacy considerations about safety w3c/screen-wake-lock#77.
-
Don't allow third party content to request wake lock w3c/screen-wake-lock#64.
-
-
12 issues received 22 new comments.
-
Update security and privacy considerations w3c/screen-wake-lock#78 (4 comments by @andrey-logvinov, @lknik)
-
Security and Privacy considerations about safety w3c/screen-wake-lock#77 (3 comments by @andrey-logvinov, @lknik)
-
Usecase of keeping WiFi and cellular radio not covered w3c/screen-wake-lock#67 (2 comments by @andrey-logvinov, @leolux)
-
"Same origin" should reference the definition w3c/screen-wake-lock#75 (1 comment by @andrey-logvinov)
-
"Implementation status" does not link anywhere w3c/screen-wake-lock#76 (1 comment by @andrey-logvinov)
-
3.1 attributes appears to be rendering wrong w3c/screen-wake-lock#68 (1 comment by @andrey-logvinov)
-
Don't allow third party content to request wake lock w3c/screen-wake-lock#64 (1 comment by @dontcallmedom)
-
-
3 pull requests opened.
-
Add same origin link, typo fix w3c/screen-wake-lock#81, by @andrey-logvinov.
-
Use contiguous IDL for interface specification w3c/screen-wake-lock#80, by @andrey-logvinov.
-
Fix typos and articles w3c/screen-wake-lock#79, by @andrey-logvinov.
-
-
3 pull requests merged.
-
Add same origin link, typo fix w3c/screen-wake-lock#81.
-
Use contiguous IDL for interface specification w3c/screen-wake-lock#80.
-
Fix typos and articles w3c/screen-wake-lock#79.
-
-
1 pull request received 8 new comments.
-
Use contiguous IDL for interface specification w3c/screen-wake-lock#80 (8 comments by @andrey-logvinov, @domenic, @dontcallmedom)
-
w3c/proximity
-
5 issues opened.
-
In centimeters... min/max privacy issue? w3c/proximity#10, by @marcoscaceres.
-
conformant server defined but never used w3c/proximity#9, by @marcoscaceres.
-
Conformant Algorithms w3c/proximity#8, by @marcoscaceres.
-
Maybe add a "limitations of proximity sensors" section w3c/proximity#6, by @marcoscaceres.
-
Model section duplicates IDL w3c/proximity#5, by @marcoscaceres.
-
-
5 issues closed.
-
distance and max: default values/ nullable w3c/proximity#3.
-
Maybe add a "limitations of proximity sensors" section w3c/proximity#6.
-
Model section duplicates IDL w3c/proximity#5.
-
conformant server defined but never used w3c/proximity#9.
-
Conformant Algorithms w3c/proximity#8.
-
-
5 issues received 5 new comments.
-
7 pull requests opened.
-
Add WD-proximity-20160714 snapshot w3c/proximity#16, by @anssiko.
-
WD for Proximity Sensor spec. w3c/proximity#15, by @riju.
-
Add default values for distance and max. w3c/proximity#14, by @riju.
-
Add more concise Conformance section w3c/proximity#13, by @riju.
-
Add limitations section w3c/proximity#12, by @riju.
-
Remove Conformance part from the spec. w3c/proximity#11, by @riju.
-
Fix typo. w3c/proximity#7, by @marcoscaceres.
-
-
6 pull requests merged.
-
Add WD-proximity-20160714 snapshot w3c/proximity#16.
-
Add default values for distance and max. w3c/proximity#14.
-
Add more concise Conformance section w3c/proximity#13.
-
Add limitations section w3c/proximity#12.
-
Fix typo. w3c/proximity#7.
-
Remove Conformance part from the spec. w3c/proximity#11.
-
-
1 pull request closed.
-
WD for Proximity Sensor spec. w3c/proximity#15.
-
-
4 pull requests received 10 new comments.
w3c/vibration
-
1 issue opened.
-
Updating privacy considerations - recovery of two identifiers w3c/vibration#12, by @lknik.
-
-
1 issue closed.
-
Use visibilityState rather than hidden w3c/vibration#7.
-
-
1 pull request opened.
-
Adjust reference to page-visibility algorithm w3c/vibration#11, by @dontcallmedom.
-
-
1 pull request merged.
-
Adjust reference to page-visibility algorithm w3c/vibration#11.
-
-
1 pull request received 1 new comment.
w3c/battery
-
1 issue opened.
-
Mitigating potential privacy-invasive usage w3c/battery#5, by @anssiko.
-
-
1 issue received 1 new comment.
w3c/gyroscope
-
2 pull requests opened.
-
Add more concise Conformance section w3c/gyroscope#2, by @riju.
-
Remove Conformance Section. w3c/gyroscope#1, by @riju.
-
-
2 pull requests merged.
-
Add more concise Conformance section w3c/gyroscope#2.
-
Remove Conformance Section. w3c/gyroscope#1.
-
w3c/accelerometer
-
1 pull request opened.
-
Add more concise Conformance section w3c/accelerometer#1, by @riju.
-
-
1 pull request merged.
-
Add more concise Conformance section w3c/accelerometer#1.
-
w3c/deviceorientation
-
3 issues closed.
-
Add DeviceAcceleration and DeviceRotationRate constructors? w3c/deviceorientation#19.
-
DeviceMotionEventInit interface members w3c/deviceorientation#14.
-
Specify the onfoo event listener attributes in Web IDL w3c/deviceorientation#17.
-
-
3 issues received 5 new comments.
-
DeviceMotionEventInit interface members w3c/deviceorientation#14 (2 comments by @foolip, @timvolodine)
-
Specify the onfoo event listener attributes in Web IDL w3c/deviceorientation#17 (2 comments by @foolip, @timvolodine)
-
Add DeviceAcceleration and DeviceRotationRate constructors? w3c/deviceorientation#19 (1 comment by @timvolodine)
-
-
2 pull requests merged.
-
Update spec-source-orientation.html w3c/deviceorientation#32.
-
Update spec-source-orientation.html w3c/deviceorientation#31.
-
TR publications
-
7 documents published.
-
MediaStream Recording published as a Working Draft. History of MediaStream Recording
-
Wake Lock API published 3 times 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
-
Screen Capture published as a Working Draft. History of Screen Capture
-
Audio Output Devices API published as a Working Draft. History of Audio Output Devices API
-
Participants
-
1 organization joined.
-
Sony Group Corporation joined.
-
GitHub
w3c/proximity
-
2 issues opened.
-
Generic Proximity sensor or UserProximity sensor w3c/proximity#4, by @tobie.
-
distance and max: default values/ nullable w3c/proximity#3, by @riju.
-
-
2 issues received 4 new comments.
-
Generic Proximity sensor or UserProximity sensor w3c/proximity#4 (3 comments by @dontcallmedom, @riju, @tobie)
-
-
1 pull request opened.
-
Proximity Sensor API based on Generic Sensor API w3c/proximity#2, by @riju.
-
-
1 pull request merged.
-
Proximity Sensor API based on Generic Sensor API w3c/proximity#2.
-
-
1 pull request received 8 new comments.
-
Proximity Sensor API based on Generic Sensor API w3c/proximity#2 (8 comments by @anssiko, @dontcallmedom, @riju, @tobie)
-
w3c/sensors
-
2 issues opened.
-
Why u data-include-sync? w3c/sensors#114, by @marcoscaceres.
-
Validate state transitions. w3c/sensors#113, by @riju.
-
-
1 issue closed.
-
Why u data-include-sync? w3c/sensors#114.
-
-
3 issues received 25 new comments.
-
Malicious use of the phone's Gyroscope w3c/sensors#112 (12 comments by @chaals, @lknik, @richtr, @tobie, @Yossioren)
-
Possibility of cross-domain communication using frequency in periodic reporting mode w3c/sensors#100 (9 comments by @lknik, @rwaldron, @tobie)
-
-
1 pull request opened.
-
Fixes #114 : Convert usecases doc to bikeshed. w3c/sensors#115, by @riju.
-
-
1 pull request merged.
-
Fixes #114 : Convert usecases doc to bikeshed. w3c/sensors#115.
-
w3c/deviceorientation
-
2 issues received 3 new comments.
-
Malicious use of the phone's Gyroscope w3c/deviceorientation#30 (2 comments by @gmandyam, @Yossioren)
-
-
2 pull requests opened.
-
Update spec-source-orientation.html w3c/deviceorientation#32, by @timvolodine.
-
Update spec-source-orientation.html w3c/deviceorientation#31, by @timvolodine.
-
w3c/screen-wake-lock
-
1 issue opened.
-
Don't allow third party content to request wake lock w3c/screen-wake-lock#64, by @andrey-logvinov.
-
-
1 issue received 4 new comments.
-
Don't allow third party content to request wake lock w3c/screen-wake-lock#64 (4 comments by @andrey-logvinov, @dontcallmedom)
-
-
2 pull requests opened.
-
Add note about permissions w3c/screen-wake-lock#66, by @andrey-logvinov.
-
Add same-origin requirement (issue #64) w3c/screen-wake-lock#65, by @andrey-logvinov.
-
-
3 pull requests merged.
-
Add note about permissions w3c/screen-wake-lock#66.
-
Add same-origin requirement (issue #64) w3c/screen-wake-lock#65.
-
Security and privacy consideration section w3c/screen-wake-lock#63.
-
-
3 pull requests received 10 new comments.
-
Security and privacy consideration section w3c/screen-wake-lock#63 (5 comments by @andrey-logvinov, @dontcallmedom)
-
Add same-origin requirement (issue #64) w3c/screen-wake-lock#65 (2 comments by @andrey-logvinov, @dontcallmedom)
-
w3c/vibration
-
3 issues opened.
-
Vibration should require user's permission w3c/vibration#10, by @andrey-logvinov.
-
Updating privacy considerations to reflect recomentations. w3c/vibration#8, by @lknik.
-
Use visibilityState rather than hidden w3c/vibration#7, by @dontcallmedom.
-
-
1 issue closed.
-
Updating privacy considerations to reflect recomentations. w3c/vibration#8.
-
-
2 issues received 8 new comments.
-
Vibration should require user's permission w3c/vibration#10 (6 comments by @andrey-logvinov, @anssiko, @lknik)
-
Updating privacy considerations to reflect recomentations. w3c/vibration#8 (2 comments by @anssiko, @lknik)
-
-
1 pull request opened.
-
Fix #8: Update privacy considerations w3c/vibration#9, by @anssiko.
-
-
1 pull request merged.
-
Fix #8: Update privacy considerations w3c/vibration#9.
-
w3c/ambient-light
-
1 issue opened.
-
Permissions for verbose readout of ALS w3c/ambient-light#10, by @lknik.
-
-
1 issue received 4 new comments.
TR publications
-
4 documents published.
-
Media Capture and Streams published as a Candidate Recommendation Snapshot. History of Media Capture and Streams
-
Media Capture Depth Stream Extensions published as a Working Draft. History of Media Capture Depth Stream Extensions
-
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
-
2 participants joined.
-
Lukasz Olejnik (W3C Invited Experts) joined.
-
Dave Raggett (W3C) joined.
-
-
11 organizations joined.
-
Orange joined.
-
Qualcomm Innovation Center, Inc joined.
-
OpenJS Foundation joined.
-
Deutsche Telekom AG joined.
-
Alibaba Group joined.
-
Mozilla Foundation joined.
-
Yandex joined.
-
Fraunhofer Gesellschaft joined.
-
Electronics and Telecommunications Research Institute (ETRI) joined.
-
MITRE Corporation joined.
-
LG Electronics joined.
-
GitHub
w3c/deviceorientation
-
1 issue opened.
-
Malicious use of the phone's Gyroscope w3c/deviceorientation#30, by @Yossioren.
-
-
1 issue received 1 new comment.
w3c/sensors
-
11 issues opened.
-
Malicious use of the phone's Gyroscope w3c/sensors#112, by @Yossioren.
-
Event object in error callback w3c/sensors#111, by @cleancoderocker.
-
What is the plan for actuators? w3c/sensors#109, by @mwichmann.
-
WebIDL ref label is "Level 1" but links to "Level 2" w3c/sensors#108, by @tidoust.
-
nit: Implementations instead of Browser implementations? w3c/sensors#107, by @mwichmann.
-
Exposing sensors in service workers w3c/sensors#106, by @tobie.
-
Does SensorReading always need a timeStamp ? w3c/sensors#105, by @riju.
-
Should the enum SensorState have nosensor ? w3c/sensors#104, by @riju.
-
Should SensorReadingEvent carry reading payload? w3c/sensors#103, by @timvolodine.
-
SensorState "idle" w3c/sensors#102, by @timvolodine.
-
-
4 issues closed.
-
What is the plan for actuators? w3c/sensors#109.
-
nit: Implementations instead of Browser implementations? w3c/sensors#107.
-
SensorState "idle" w3c/sensors#102.
-
1 issue reopened.
-
Clarify terminology w3c/sensors#78, by @tobie.
-
-
10 issues received 49 new comments.
-
Should SensorReadingEvent carry reading payload? w3c/sensors#103 (13 comments by @rwaldron, @timvolodine, @tobie, @zolkis)
-
Does SensorReading always need a timeStamp ? w3c/sensors#105 (13 comments by @mwichmann, @riju, @timvolodine, @tobie)
-
Should the enum SensorState have nosensor ? w3c/sensors#104 (7 comments by @anssiko, @riju, @timvolodine, @tobie)
-
WebIDL ref label is "Level 1" but links to "Level 2" w3c/sensors#108 (3 comments by @tidoust, @tobie)
-
Eventually rename the SensorReading timeStamp attribute for consistency with DOM events. w3c/sensors#101 (3 comments by @timvolodine, @tobie)
-
w3c/screen-wake-lock
-
1 pull request opened.
-
Security and privacy consideration section w3c/screen-wake-lock#63, by @andrey-logvinov.
-
-
1 pull request received 4 new comments.
-
Security and privacy consideration section w3c/screen-wake-lock#63 (4 comments by @andrey-logvinov, @dontcallmedom, @mwichmann)
-
w3c/battery
-
1 issue opened.
-
Expose getBattery to ServiceWorker w3c/battery#4, by @stefhak.
-
-
1 issue received 8 new comments.
w3c/html-media-capture
-
1 issue opened.
-
VideoFacingModeEnum as the capture attribute's value w3c/html-media-capture#4, by @anssiko.
-
TR publications
-
3 documents published.
-
MediaStream Recording published as a Working Draft. History of MediaStream Recording
-
Media Capture Depth Stream Extensions published twice as a Working Draft. History of Media Capture Depth Stream Extensions
-
Participants
-
1 participant joined.
-
Frederick Hirsch (W3C Invited Experts) joined.
-
-
3 organizations joined.
-
Tencent joined.
-
Google LLC joined.
-
Samsung Electronics Co., Ltd. joined.
-
GitHub
w3c/sensors
-
4 issues opened.
-
Frequency readout allows fingerprinting sensors, privacy. w3c/sensors#99, by @lknik.
-
Javascript 120Hz devicemotion events for high end inertial applications w3c/sensors#98, by @lukes3315.
-
1 issue closed.
-
Add high resolution monotonic timestamps to SensorReadings w3c/sensors#43.
-
-
2 issues reopened.
-
Add high resolution monotonic timestamps to SensorReadings w3c/sensors#43, by @tobie.
-
-
2 issues received 8 new comments.
-
API must allow Web devs to easily create fused sensors in JS with an API consistant with native sensors w3c/sensors#42 (5 comments by @marcoscaceres, @rwaldron, @tobie)
-
Javascript 120Hz devicemotion events for high end inertial applications w3c/sensors#98 (3 comments by @lukes3315, @tobie)
-
w3c/vibration
-
1 issue closed.
-
Privacy considerations w3c/vibration#2.
-
-
1 issue received 2 new comments.
-
2 pull requests opened.
-
Add Participate header w3c/vibration#6, by @anssiko.
-
Editorial: Use Contiguous IDL w3c/vibration#5, by @anssiko.
-
-
3 pull requests merged.
-
Add Participate header w3c/vibration#6.
-
Editorial: Use Contiguous IDL w3c/vibration#5.
-
Vibration API Recommendation errata w3c/vibration#1.
-
-
1 pull request received 2 new comments.
w3c/html-media-capture
-
3 pull requests opened.
-
Add Participate header w3c/html-media-capture#3, by @anssiko.
-
Editorial: Use Contiguous IDL w3c/html-media-capture#2, by @anssiko.
-
Add [CEReactions] annotation to capture w3c/html-media-capture#1, by @domenic.
-
-
3 pull requests merged.
-
Add Participate header w3c/html-media-capture#3.
-
Editorial: Use Contiguous IDL w3c/html-media-capture#2.
-
Add [CEReactions] annotation to capture w3c/html-media-capture#1.
-
-
1 pull request received 1 new comment.
w3c/battery
-
1 issue opened.
-
A promise/BatteryManager *per browsing context*!? w3c/battery#2, by @domenic.
-
-
1 issue closed.
-
A promise/BatteryManager *per browsing context*!? w3c/battery#2.
-
-
1 issue received 4 new comments.
-
A promise/BatteryManager *per browsing context*!? w3c/battery#2 (4 comments by @anssiko, @mounirlamouri, @zqzhang)
-
-
1 pull request opened.
-
Fix #2: Clarify there is one battery promise per Document w3c/battery#3, by @anssiko.
-
-
1 pull request merged.
-
Fix #2: Clarify there is one battery promise per Document w3c/battery#3.
-
-
1 pull request received 23 new comments.
-
Fix #2: Clarify there is one battery promise per Document w3c/battery#3 (23 comments by @anssiko, @bzbarsky, @domenic, @dontcallmedom, @mounirlamouri)
-
w3c/ambient-light
-
2 issues opened.
-
Ambient Light Sensors to detect RGB colors w3c/ambient-light#9, by @lknik.
-
Security and privacy considerations for Ambient Light Events w3c/ambient-light#8, by @lknik.
-
-
2 issues received 15 new comments.
-
Security and privacy considerations for Ambient Light Events w3c/ambient-light#8 (14 comments by @anssiko, @chaals, @fhirsch, @lknik, @schwittmann, @tobie)
-
w3c/geolocation
-
2 pull requests closed.
-
Create contributing.md (closes #4) w3c/geolocation#6.
-
Added README (closes #3) w3c/geolocation#4.
-
Lifecycle
-
1 charter started.
-
Chartered until 31 December 2017. Participants had to rejoin under this charter.
-
TR publications
-
4 documents published.
-
Battery Status API published as a Proposed Recommendation. History of Battery Status API
-
Ambient Light Sensor published as a Working Draft. History of Ambient Light Sensor
-
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
-
Participants
-
1 participant joined.
-
Dominique Hazaël-Massieux (W3C) joined.
-
-
6 participants left.
-
Lukasz Olejnik (W3C Invited Experts) left.
-
Josh Soref (W3C Invited Experts) left.
-
Robin Berjon (W3C Invited Experts) left.
-
Frederick Hirsch (W3C Invited Experts) left.
-
Dominique Hazaël-Massieux (W3C) left.
-
Dave Raggett (W3C) left.
-
-
3 organizations joined.
-
Intel Corporation joined.
-
360 joined.
-
360 joined.
-
-
41 organizations left.
-
360 left.
-
AT&T left.
-
Plantronics, Inc. left.
-
Viacom inc. left.
-
Alibaba Group left.
-
Universidade Federal de Alagoas left.
-
Tencent left.
-
OpenJS Foundation left.
-
Yandex left.
-
Mitsubishi Electric Corporation left.
-
IBM Corporation left.
-
Square Enix Holdings left.
-
ACCESS CO., LTD. left.
-
Qualcomm Innovation Center, Inc left.
-
China Academy of Information and Communications Technology (CAICT) left.
-
Huawei left.
-
Baidu, Inc. left.
-
Sony Group Corporation left.
-
Cable Television Laboratories Inc left.
-
Tomo-Digi Corporation left.
-
LG Electronics left.
-
China Unicom left.
-
Samsung Electronics Co., Ltd. left.
-
imec left.
-
Institut Mines-Télécom left.
-
Google LLC left.
-
Mozilla Foundation left.
-
Vodafone left.
-
Telefónica left.
-
BlackBerry Limited left.
-
Electronics and Telecommunications Research Institute (ETRI) left.
-
Voxeo left.
-
Center for Democracy and Technology left.
-
Intel Corporation left.
-
Deutsche Telekom AG left.
-
Opera Software AS left.
-
Fraunhofer Gesellschaft left.
-
Nokia Corporation left.
-
MITRE Corporation left.
-
Microsoft Corporation left.
-
Orange left.
-
GitHub
w3c/sensors
-
7 issues opened.
-
Adding a sensor.activated attribute w3c/sensors#95, by @tobie.
-
start() to return a cancellable promise that resolves on first reading w3c/sensors#94, by @tobie.
-
Handling fatal vs. transient errors w3c/sensors#93, by @tobie.
-
Is there a need for a oncalibrationneeded event w3c/sensors#92, by @tobie.
-
Prepare licensing change in spec w3c/sensors#91, by @dontcallmedom.
-
Add solution for cached value readings w3c/sensors#89, by @tobie.
-
Add solution for one-shot readings w3c/sensors#88, by @tobie.
-
-
9 issues closed.
-
Define behavior when visibilityState != "visible" w3c/sensors#81.
-
Discrete vs continuous reporting modes w3c/sensors#75.
-
Should sensors be singleton? w3c/sensors#8.
-
Handling fatal vs. transient errors w3c/sensors#93.
-
1 issue reopened.
-
Clarify terminology w3c/sensors#78, by @tobie.
-
-
15 issues received 41 new comments.
-
Add solution for one-shot readings w3c/sensors#88 (21 comments by @annevk, @anssiko, @darobin, @domenic, @marcoscaceres, @rwaldron, @tobie)
-
Is there a need for a oncalibrationneeded event w3c/sensors#92 (2 comments by @dontcallmedom, @tobie)
-
Spec should allow user agents to reduce or disable sensor read for power saving purposes w3c/sensors#66 (1 comment by @tobie)
-
Discreet sensors must fire an event with their current state on instantiation w3c/sensors#87 (1 comment by @tobie)
-
What if requested polling frequency is > time it takes to read data out of the sensor? w3c/sensors#23 (1 comment by @tobie)
-
Define behavior when multiple instances of a sensor set different settings w3c/sensors#79 (1 comment by @tobie)
-
Allow for async permission request when first accessing sensor data w3c/sensors#20 (1 comment by @tobie)
-
-
3 pull requests opened.
-
Add Sensor.onstatechange to be defined. w3c/sensors#97, by @riju.
-
Set expected metadata on repository w3c/sensors#90, by @dontcallmedom.
-
-
3 pull requests merged.
-
Add Sensor.onstatechange to be defined. w3c/sensors#97.
-
Typos. w3c/sensors#96.
-
Set expected metadata on repository w3c/sensors#90.
-
w3c/ambient-light
-
1 pull request opened.
-
Add bikeshed index file. w3c/ambient-light#7, by @tobie.
-
-
1 pull request merged.
-
Add bikeshed index file. w3c/ambient-light#7.
-
-
1 pull request received 9 new comments.
-
Add bikeshed index file. w3c/ambient-light#7 (9 comments by @anssiko, @dontcallmedom, @tabatkins, @tobie)
-
w3c/battery
-
1 pull request opened.
-
Update links w3c/battery#1, by @dontcallmedom.
-
-
1 pull request merged.
-
Update links w3c/battery#1.
-
w3c/screen-wake-lock
-
1 pull request opened.
-
Set expected metadata on repository w3c/screen-wake-lock#62, by @dontcallmedom.
-
-
1 pull request merged.
-
Set expected metadata on repository w3c/screen-wake-lock#62.
-
w3c/vibration
-
1 issue opened.
-
Change WebIDL ref to WebIDL-1 w3c/vibration#3, by @dontcallmedom.
-
-
1 issue closed.
-
Change WebIDL ref to WebIDL-1 w3c/vibration#3.
-
-
1 pull request opened.
-
Use WEBIDL-1 as a reference w3c/vibration#4, by @dontcallmedom.
-
-
1 pull request merged.
-
Use WEBIDL-1 as a reference w3c/vibration#4.
-
-
1 pull request received 1 new comment.
w3c/deviceorientation
-
3 issues closed.
-
webkitCompassHeading / webkitCompassAccuracy w3c/deviceorientation#6.
-
Add Security and Privacy Section w3c/deviceorientation#24.
-
Security considerations w3c/deviceorientation#13.
-
-
3 issues received 4 new comments.
-
Specify the onfoo event listener attributes in Web IDL w3c/deviceorientation#17 (2 comments by @foolip, @timvolodine)
-
-
1 pull request merged.
-
add security and privacy section w3c/deviceorientation#25.
-
TR publications
-
2 documents published.
-
Media Capture Depth Stream Extensions published twice as a Working Draft. History of Media Capture Depth Stream Extensions
-
Participants
-
1 organization left.
-
Smart Communications Inc., left.
-
GitHub
w3c/sensors
-
3 issues opened.
-
Discreet sensors must fire an event with their current state on instantiation w3c/sensors#87, by @tobie.
-
constructor of "Abstract" Sensor w3c/sensors#86, by @riju.
-
sensorId : how are they named w3c/sensors#85, by @riju.
-
-
7 issues closed.
-
Add a section on how sensors are implemented w3c/sensors#53.
-
No way to express an abstract constructor in WebIDL w3c/sensors#19.
-
sensorId : how are they named w3c/sensors#85.
-
constructor of "Abstract" Sensor w3c/sensors#86.
-
Conformance requirements for concrete specs w3c/sensors#84.
-
Define instantiation behavior in non top-level browsing contexts w3c/sensors#80.
-
-
2 issues reopened.
-
sensorId : how are they named w3c/sensors#85, by @tobie.
-
No way to express an abstract constructor in WebIDL w3c/sensors#19, by @tobie.
-
-
8 issues received 21 new comments.
-
Conformance requirements for concrete specs w3c/sensors#84 (7 comments by @anssiko, @chaals, @marcoscaceres, @tobie)
-
Define behavior when visibilityState != "visible" w3c/sensors#81 (4 comments by @anssiko, @marcoscaceres, @tobie)
-
Identify the lower level primitives that do the actual sensor polling. w3c/sensors#24 (2 comments by @rwaldron, @tobie)
-
w3c/deviceorientation
-
4 issues closed.
-
Specify the init*Event() methods? w3c/deviceorientation#18.
-
Spec should include a link for where issues are tracked w3c/deviceorientation#20.
-
[Callback] extended attributes w3c/deviceorientation#9.
-
Absolute-only DeviceOrientationEvents are bad for head tracking in VR w3c/deviceorientation#21.
-
-
4 issues received 8 new comments.
-
Absolute-only DeviceOrientationEvents are bad for head tracking in VR w3c/deviceorientation#21 (4 comments by @RByers, @timvolodine)
-
-
5 pull requests opened.
-
Add a Participate section with links to GitHub w3c/deviceorientation#29, by @foolip.
-
Use HTTPS as needed to avoid mixed content warnings w3c/deviceorientation#28, by @foolip.
-
Add missing semicolons to IDL blocks w3c/deviceorientation#27, by @foolip.
-
Remove the [Callback] extended attribute w3c/deviceorientation#26, by @foolip.
-
add security and privacy section w3c/deviceorientation#25, by @timvolodine.
-
-
4 pull requests merged.
-
Add a Participate section with links to GitHub w3c/deviceorientation#29.
-
Use HTTPS as needed to avoid mixed content warnings w3c/deviceorientation#28.
-
Add missing semicolons to IDL blocks w3c/deviceorientation#27.
-
Remove the [Callback] extended attribute w3c/deviceorientation#26.
-
-
2 pull requests received 7 new comments.
-
add security and privacy section w3c/deviceorientation#25 (5 comments by @martinthomson, @maryammjd, @richtr, @timvolodine)
-
Remove the [Callback] extended attribute w3c/deviceorientation#26 (2 comments by @foolip, @timvolodine)
-
w3c/screen-wake-lock
-
1 issue reopened.
-
Book reader usecase not well supported w3c/screen-wake-lock#56, by @andrey-logvinov.
-
-
4 issues received 6 new comments.
-
Current API not friendly to components w3c/screen-wake-lock#55 (2 comments by @andrey-logvinov, @sicking)
-
Spec needs to be explicit about resetting release timer on lock release w3c/screen-wake-lock#57 (1 comment by @andrey-logvinov)
w3c/vibration
-
1 issue opened.
-
Privacy considerations w3c/vibration#2, by @chaals.
-
-
1 issue received 6 new comments.
-
1 pull request opened.
-
Vibration API Recommendation errata w3c/vibration#1, by @anssiko.
-
-
1 pull request received 1 new comment.
TR publications
-
2 documents published.
-
Wake Lock API published as a Working Draft. History of Wake Lock API
-
Media Capture Depth Stream Extensions published as a Working Draft. History of Media Capture Depth Stream Extensions
-
GitHub
w3c/sensors
-
9 issues opened.
-
Conformance requirements for concrete specs w3c/sensors#84, by @tobie.
-
Should SensorReading inherit from Event? w3c/sensors#82, by @tobie.
-
Define behavior when visibilityState != "visible" w3c/sensors#81, by @tobie.
-
Define instantiation behavior in non top-level browsing contexts w3c/sensors#80, by @tobie.
-
Define behavior when multiple instances of a sensor set different settings w3c/sensors#79, by @tobie.
-
Clarify terminology w3c/sensors#78, by @tobie.
-
Discrete vs continuous reporting modes w3c/sensors#75, by @tobie.
-
Setup echidna for continuous deployment w3c/sensors#74, by @tobie.
-
Background support for sensors APIs w3c/sensors#73, by @mkruisselbrink.
-
-
1 issue closed.
-
Should SensorReading inherit from Event? w3c/sensors#82.
-
-
2 issues reopened.
-
Clarify terminology w3c/sensors#78, by @tobie.
-
Setup echidna for continuous deployment w3c/sensors#74, by @dontcallmedom.
-
-
8 issues received 26 new comments.
-
Setup echidna for continuous deployment w3c/sensors#74 (13 comments by @dontcallmedom, @marcoscaceres, @tobie)
-
Define behavior when visibilityState != "visible" w3c/sensors#81 (2 comments by @marcoscaceres, @tobie)
-
Identify the lower level primitives that do the actual sensor polling. w3c/sensors#24 (2 comments by @tobie)
-
Spec should allow user agents to reduce or disable sensor read for power saving purposes w3c/sensors#66 (1 comment by @tobie)
-
Sensor.frequency needs to be setable to allow frequency adaptation w3c/sensors#63 (1 comment by @tobie)
-
-
4 pull requests opened.
-
Update index.html to fix spelling errors. w3c/sensors#83, by @bbernhar.
-
Set up autopublication via echidna and travis w3c/sensors#77, by @dontcallmedom.
-
Indicate support for HTML5Apps project in ack of my work w3c/sensors#76, by @dontcallmedom.
-
Fixed typo in ProximitySensor w3c/sensors#72, by @djipco.
-
-
2 pull requests merged.
-
Set up autopublication via echidna and travis w3c/sensors#77.
-
Indicate support for HTML5Apps project in ack of my work w3c/sensors#76.
-
-
2 pull requests closed.
-
Update index.html to fix spelling errors. w3c/sensors#83.
-
Fixed typo in ProximitySensor w3c/sensors#72.
-
-
1 pull request received 1 new comment.
w3c/screen-wake-lock
-
5 issues closed.
-
shouldn't this be part of the permissions API? w3c/screen-wake-lock#59.
-
Why Document instead of Window? w3c/screen-wake-lock#52.
-
Update spec to match WHATWG discussion w3c/screen-wake-lock#39.
-
Lifecycle of release and regain ... is hard. w3c/screen-wake-lock#24.
-
Wake locks are lost, but not "changed" w3c/screen-wake-lock#21.
-
-
8 issues received 17 new comments.
-
Book reader usecase not well supported w3c/screen-wake-lock#56 (4 comments by @andrey-logvinov, @sicking)
-
Spec needs to be explicit about resetting release timer on lock release w3c/screen-wake-lock#57 (4 comments by @andrey-logvinov, @sicking)
-
shouldn't this be part of the permissions API? w3c/screen-wake-lock#59 (2 comments by @andrey-logvinov)
-
Current API not friendly to components w3c/screen-wake-lock#55 (2 comments by @andrey-logvinov, @sicking)
-
Lifecycle of release and regain ... is hard. w3c/screen-wake-lock#24 (1 comment by @andrey-logvinov)
-
-
2 pull requests opened.
-
Adapt to updated management of definitions in ReSpec w3c/screen-wake-lock#61, by @dontcallmedom.
-
Add ack for my work under HTML5Apps project w3c/screen-wake-lock#60, by @dontcallmedom.
-
-
2 pull requests merged.
-
Adapt to updated management of definitions in ReSpec w3c/screen-wake-lock#61.
-
Add ack for my work under HTML5Apps project w3c/screen-wake-lock#60.
-
-
1 pull request closed.
-
Adapt to use data-lt instead of title for definitions w3c/screen-wake-lock#58.
-
-
1 pull request received 1 new comment.
-
Adapt to use data-lt instead of title for definitions w3c/screen-wake-lock#58 (1 comment by @andrey-logvinov)
-
w3c/ambient-light
-
4 pull requests opened.
-
Add GH links boilerplate and SoTD section w3c/ambient-light#6, by @anssiko.
-
Rename README header too w3c/ambient-light#5, by @anssiko.
-
Rename the spec w3c/ambient-light#4, by @anssiko.
-
First draft of Generic Sensor based AmbientLightSensor w3c/ambient-light#3, by @tobie.
-
-
4 pull requests merged.
-
Add GH links boilerplate and SoTD section w3c/ambient-light#6.
-
Rename README header too w3c/ambient-light#5.
-
Rename the spec w3c/ambient-light#4.
-
First draft of Generic Sensor based AmbientLightSensor w3c/ambient-light#3.
-
-
1 pull request received 7 new comments.
-
First draft of Generic Sensor based AmbientLightSensor w3c/ambient-light#3 (7 comments by @anssiko, @riju, @tobie)
-