Devices and Sensors Working Group - Activity in 2019
No matches.
TR publications
-
4 documents published.
-
Accelerometer published as a Candidate Recommendation Snapshot. History of Accelerometer
-
Generic Sensor API published as a Candidate Recommendation Snapshot. History of Generic Sensor API
-
Gyroscope published as a Candidate Recommendation Snapshot. History of Gyroscope
-
Orientation Sensor published as a Candidate Recommendation Snapshot. History of Orientation Sensor
-
GitHub
w3c/das-wg
-
3 pull requests opened.
-
Slightly increase the contrast of the text w3c/das-wg#27, by @xfq.
-
Fix the color contrasts w3c/das-wg#26, by @xfq.
-
Update roadmap w3c/das-wg#25, by @anssiko.
-
-
3 pull requests merged.
-
Slightly increase the contrast of the text w3c/das-wg#27.
-
Fix the color contrasts w3c/das-wg#26.
-
Update roadmap w3c/das-wg#25.
-
w3c/sensors
-
1 issue received 14 new comments.
-
Spec should include mandatory mitigations for privacy harms / risks w3c/sensors#397 (14 comments by @anssiko, @pes10k, @swickr)
-
-
2 pull requests opened.
-
Note [PERMISSIONS-REQUEST] stability expectation for CR exit w3c/sensors#402, by @anssiko.
-
Make the permission request algorithm normative w3c/sensors#401, by @anssiko.
-
-
2 pull requests merged.
-
Note [PERMISSIONS-REQUEST] stability expectation for CR exit w3c/sensors#402.
-
Make the permission request algorithm normative w3c/sensors#401.
-
-
2 pull requests received 3 new comments.
-
Note [PERMISSIONS-REQUEST] stability expectation for CR exit w3c/sensors#402 (1 comment by @anssiko)
w3c/deviceorientation
-
1 issue received 5 new comments.
-
Move fingerprintable APIs behind permissions w3c/deviceorientation#85 (5 comments by @anssiko, @pes10k, @scheib)
-
w3c/contact-picker
-
1 issue opened.
-
maybe split up name to to components? w3c/contact-picker#29, by @jimmywarting.
-
-
1 issue received 1 new comment.
GitHub
w3c/sensors
-
1 issue opened.
-
access to orientation without access to linear acceleration? w3c/sensors#399, by @fergald.
-
-
2 issues closed.
-
[meta] Wide review tracker w3c/sensors#299.
-
Remove text about non-explicit permissions w3c/sensors#396.
-
-
4 issues received 25 new comments.
-
Spec should include mandatory mitigations for privacy harms / risks w3c/sensors#397 (17 comments by @anssiko, @pes10k, @plehegar, @reillyeon)
-
access to orientation without access to linear acceleration? w3c/sensors#399 (5 comments by @anssiko, @fergald, @pes10k, @reillyeon)
-
-
1 pull request opened.
-
Update "Security and privacy considerations" and "Permissions API" w3c/sensors#400, by @anssiko.
-
-
1 pull request merged.
-
Update "Security and privacy considerations" and "Permissions API" w3c/sensors#400.
-
-
1 pull request received 6 new comments.
-
Update "Security and privacy considerations" and "Permissions API" w3c/sensors#400 (6 comments by @anssiko, @pes10k, @xfq)
-
w3c/geolocation
-
1 pull request opened.
-
Typo: PositionOptions is a dictionary rather than an interface w3c/geolocation#38, by @bathos.
-
-
1 pull request merged.
-
Typo: PositionOptions is a dictionary rather than an interface w3c/geolocation#38.
-
-
3 pull requests received 4 new comments.
-
Rename NavigatorGeolocation* interfaces to Geolocation* w3c/geolocation#23 (2 comments by @anssiko, @marcoscaceres)
-
Typo: PositionOptions is a dictionary rather than an interface w3c/geolocation#38 (1 comment by @bathos)
-
w3c/deviceorientation
-
2 issues received 11 new comments.
-
Move fingerprintable APIs behind permissions w3c/deviceorientation#85 (6 comments by @anssiko, @pes10k, @reillyeon)
-
Add API for requesting permission to receive device motion / orientation events w3c/deviceorientation#57 (5 comments by @cdumez, @reillyeon, @solarsu, @yoyo837)
-
w3c/vibration
-
1 issue received 3 new comments.
-
1 pull request opened.
-
Editorial: Fix ReSpec cite error w3c/vibration#24, by @anssiko.
-
-
1 pull request merged.
-
Editorial: Fix ReSpec cite error w3c/vibration#24.
-
-
1 pull request received 1 new comment.
w3c/screen-wake-lock
-
1 issue received 2 new comments.
-
WakeLock.request() returns a promise that never resolves w3c/screen-wake-lock#226 (2 comments by @marcoscaceres, @tomayac)
-
-
1 pull request merged.
-
Editorial: ReSpec usage cleanup w3c/screen-wake-lock#248.
-
-
1 pull request received 6 new comments.
w3c/contact-picker
-
3 issues closed.
-
Detect which contact properties are supported by the browser w3c/contact-picker#19.
-
Provide access to address properties w3c/contact-picker#12.
-
Provide access to contact's icon w3c/contact-picker#13.
-
-
1 pull request merged.
-
Add support for selecting icons, resolves #13 w3c/contact-picker#28.
-
-
1 pull request received 10 new comments.
-
Add support for selecting icons, resolves #13 w3c/contact-picker#28 (10 comments by @beverloo, @rayankans)
-
GitHub
w3c/deviceorientation
-
1 issue opened.
-
Move fingerprintable APIs behind permissions w3c/deviceorientation#85, by @pes10k.
-
-
3 issues received 11 new comments.
-
Move fingerprintable APIs behind permissions w3c/deviceorientation#85 (5 comments by @anssiko, @pes10k, @reillyeon)
-
Add API for requesting permission to receive device motion / orientation events w3c/deviceorientation#57 (5 comments by @cdumez, @elmariocarlos, @gkoberger, @mvl22)
-
w3c/contact-picker
-
1 issue opened.
-
Unable to register for Origin Trial w3c/contact-picker#27, by @Exoplanet3000.
-
-
1 issue closed.
-
Unable to register for Origin Trial w3c/contact-picker#27.
-
-
3 issues received 5 new comments.
-
1 pull request opened.
-
Add support for selecting icons, resolves #13 w3c/contact-picker#28, by @rayankans.
-
-
1 pull request merged.
-
Add feature detection & create the concept of a Contacts Source. w3c/contact-picker#26.
-
w3c/sensors
-
4 issues opened.
-
Move fingerprintable APIs behind permissions w3c/sensors#398, by @pes10k.
-
Spec should include mandatory mitigations for privacy harms / risks w3c/sensors#397, by @pes10k.
-
Remove text about non-explicit permissions w3c/sensors#396, by @pes10k.
-
Access to magnetometer and potential security & privacy issues w3c/sensors#394, by @MTuner.
-
-
1 issue closed.
-
Move fingerprintable APIs behind permissions w3c/sensors#398.
-
-
1 issue reopened.
-
[meta] Wide review tracker w3c/sensors#299, by @anssiko.
-
-
5 issues received 11 new comments.
-
Spec should include mandatory mitigations for privacy harms / risks w3c/sensors#397 (2 comments by @anssiko, @pes10k)
-
Access to magnetometer and potential security & privacy issues w3c/sensors#394 (2 comments by @MTuner, @reillyeon)
-
1 pull request opened.
-
Syntax correction for the Feature-Policy response header example w3c/sensors#395, by @Malvoz.
-
-
1 pull request merged.
-
Syntax correction for the Feature-Policy response header example w3c/sensors#395.
-
-
1 pull request received 2 new comments.
-
Syntax correction for the Feature-Policy response header example w3c/sensors#395 (2 comments by @anssiko, @Malvoz)
-
w3c/screen-wake-lock
-
7 issues opened.
-
Hide failure to acquire a screen wake lock w3c/screen-wake-lock#247, by @reillyeon.
-
Figure out what to do with workers and permission requests w3c/screen-wake-lock#246, by @rakuco.
-
Describe WakeLockSentinel.type w3c/screen-wake-lock#240, by @rakuco.
-
Race condition in request() steps w3c/screen-wake-lock#239, by @reillyeon.
-
Consider not defining a custom WakeLockEvent w3c/screen-wake-lock#238, by @reillyeon.
-
WakeLockPermissionDescriptor's type should be required w3c/screen-wake-lock#233, by @marcoscaceres.
-
Anyone implementing "system" lock? w3c/screen-wake-lock#232, by @marcoscaceres.
-
-
5 issues closed.
-
Race condition in request() steps w3c/screen-wake-lock#239.
-
Consider not defining a custom WakeLockEvent w3c/screen-wake-lock#238.
-
Describe WakeLockSentinel.type w3c/screen-wake-lock#240.
-
WakeLockPermissionDescriptor's type should be required w3c/screen-wake-lock#233.
-
WakeLock.request() returns a promise that never resolves w3c/screen-wake-lock#226.
-
-
7 issues received 45 new comments.
-
In obtain permission: don't co-opt resultPromise - it's creating a custom permission model w3c/screen-wake-lock#198 (14 comments by @kenchris, @marcoscaceres, @rakuco, @reillyeon)
-
Anyone implementing "system" lock? w3c/screen-wake-lock#232 (14 comments by @kenchris, @marcoscaceres, @reillyeon)
-
WakeLock.request() returns a promise that never resolves w3c/screen-wake-lock#226 (7 comments by @marcoscaceres, @rakuco, @reillyeon, @tomayac)
-
Race condition in request() steps w3c/screen-wake-lock#239 (4 comments by @marcoscaceres, @rakuco, @reillyeon)
-
WakeLockPermissionDescriptor's type should be required w3c/screen-wake-lock#233 (3 comments by @kenchris, @marcoscaceres, @reillyeon)
-
Consider not defining a custom WakeLockEvent w3c/screen-wake-lock#238 (2 comments by @marcoscaceres, @reillyeon)
-
-
10 pull requests opened.
-
Editorial: ReSpec usage cleanup w3c/screen-wake-lock#248, by @marcoscaceres.
-
chore: more accurately capture commitments w3c/screen-wake-lock#245, by @marcoscaceres.
-
Make WakeLockPermissionDescriptor.type required. w3c/screen-wake-lock#244, by @rakuco.
-
Add a proper explanation for WakeLockSentinel.type w3c/screen-wake-lock#243, by @rakuco.
-
Remove WakeLockEvent and WakeLockEventInit. w3c/screen-wake-lock#242, by @rakuco.
-
chore(PULL_REQUEST_TEMPLATE): merge reminders w3c/screen-wake-lock#241, by @marcoscaceres.
-
Rewrite user-visible API w3c/screen-wake-lock#237, by @rakuco.
-
Fix spec validation issues. w3c/screen-wake-lock#236, by @rakuco.
-
Fix reference to "a new promise". w3c/screen-wake-lock#235, by @rakuco.
-
Add an "if aborted" step to WakeLock.request() to deal with hidden documents w3c/screen-wake-lock#234, by @rakuco.
-
-
8 pull requests merged.
-
chore: more accurately capture commitments w3c/screen-wake-lock#245.
-
Add an "if aborted" step to WakeLock.request() to deal with hidden documents w3c/screen-wake-lock#234.
-
Remove WakeLockEvent and WakeLockEventInit. w3c/screen-wake-lock#242.
-
Add a proper explanation for WakeLockSentinel.type w3c/screen-wake-lock#243.
-
Make WakeLockPermissionDescriptor.type required. w3c/screen-wake-lock#244.
-
chore(PULL_REQUEST_TEMPLATE): merge reminders w3c/screen-wake-lock#241.
-
Rewrite user-visible API w3c/screen-wake-lock#237.
-
Fix spec validation issues. w3c/screen-wake-lock#236.
-
-
1 pull request closed.
-
Fix reference to "a new promise". w3c/screen-wake-lock#235.
-
-
6 pull requests received 32 new comments.
-
Rewrite user-visible API w3c/screen-wake-lock#237 (13 comments by @anssiko, @kenchris, @marcoscaceres, @rakuco, @reillyeon)
-
Add an "if aborted" step to WakeLock.request() to deal with hidden documents w3c/screen-wake-lock#234 (10 comments by @kenchris, @marcoscaceres, @rakuco)
-
Remove WakeLockEvent and WakeLockEventInit. w3c/screen-wake-lock#242 (3 comments by @marcoscaceres, @rakuco)
-
Make WakeLockPermissionDescriptor.type required. w3c/screen-wake-lock#244 (2 comments by @kenchris, @rakuco)
-
w3c/battery
-
1 pull request received 1 new comment.
-
Allow use in same-origin children, add Feature Policy integration w3c/battery#13 (1 comment by @anssiko)
-
w3c/geolocation
-
1 issue opened.
-
Algorithms should integrate permission handling w3c/geolocation#37, by @marcoscaceres.
-
-
1 issue received 3 new comments.
-
Disable geolocation by default in cross-origin iframes w3c/geolocation#10 (3 comments by @engedy, @marcoscaceres, @raymeskhoury)
-
-
1 pull request merged.
-
Tidy up document w3c/geolocation#36.
-
w3c/das-wg
-
1 issue closed.
-
DAS WG TPAC F2F agenda (Fukuoka, Sep 19-20 2019) w3c/das-wg#24.
-
GitHub
w3c/screen-wake-lock
-
1 issue closed.
-
Use real instances of things w3c/screen-wake-lock#185.
-
-
1 issue reopened.
-
obtain permission seems wrong w3c/screen-wake-lock#187, by @rakuco.
-
-
5 issues received 25 new comments.
-
WakeLock.request() returns a promise that never resolves w3c/screen-wake-lock#226 (20 comments by @css-meeting-bot, @domenic, @kenchris, @marcoscaceres, @rakuco, @reillyeon, @tomayac)
-
In obtain permission: don't co-opt resultPromise - it's creating a custom permission model w3c/screen-wake-lock#198 (2 comments by @rakuco, @reillyeon)
-
w3c/battery
-
2 issues closed.
-
Checks on allowed usage are specced incorrectly w3c/battery#19.
-
-
1 pull request opened.
-
Replace SecurityError with NotAllowedError in feature policy w3c/battery#24, by @Honry.
-
-
2 pull requests merged.
-
Replace SecurityError with NotAllowedError in feature policy w3c/battery#24.
-
-
2 pull requests received 5 new comments.
-
Allow use in same-origin children, add Feature Policy integration w3c/battery#13 (3 comments by @anssiko, @css-meeting-bot)
-
Replace SecurityError with NotAllowedError in feature policy w3c/battery#24 (2 comments by @anssiko, @Honry)
-
w3c/sensors
-
1 issue closed.
-
Add API for requesting permission w3c/sensors#388.
-
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
Align WebIDL examples with WebIDL spec constructor operation w3c/sensors#393, by @anssiko.
-
[generic-sensor] Align with Web IDL specification w3c/sensors#392, by @autokagami.
-
-
2 pull requests merged.
-
Align WebIDL examples with WebIDL spec constructor operation w3c/sensors#393.
-
[generic-sensor] Align with Web IDL specification w3c/sensors#392.
-
-
1 pull request received 1 new comment.
-
Align WebIDL examples with WebIDL spec constructor operation w3c/sensors#393 (1 comment by @anssiko)
-
w3c/ambient-light
-
1 pull request opened.
-
[ambient-light] Align with Web IDL specification w3c/ambient-light#61, by @autokagami.
-
-
1 pull request merged.
-
[ambient-light] Align with Web IDL specification w3c/ambient-light#61.
-
w3c/gyroscope
-
1 pull request opened.
-
[gyroscope] Align with Web IDL specification w3c/gyroscope#44, by @autokagami.
-
-
1 pull request merged.
-
[gyroscope] Align with Web IDL specification w3c/gyroscope#44.
-
w3c/magnetometer
-
1 pull request opened.
-
[magnetometer] Align with Web IDL specification w3c/magnetometer#54, by @autokagami.
-
-
1 pull request merged.
-
[magnetometer] Align with Web IDL specification w3c/magnetometer#54.
-
w3c/deviceorientation
-
2 issues opened.
-
Need to define the DeviceMotionEvent constructor w3c/deviceorientation#83, by @foolip.
-
PermissionState is already defined in Permission API w3c/deviceorientation#82, by @dontcallmedom.
-
-
2 issues received 7 new comments.
-
PermissionState is already defined in Permission API w3c/deviceorientation#82 (6 comments by @anssiko, @cdumez, @dontcallmedom, @reillyeon)
-
-
2 pull requests opened.
-
[orientation-event] Align with Web IDL specification w3c/deviceorientation#84, by @autokagami.
-
Avoid breaking old URL of editors draft w3c/deviceorientation#81, by @dontcallmedom.
-
-
2 pull requests merged.
-
[orientation-event] Align with Web IDL specification w3c/deviceorientation#84.
-
Avoid breaking old URL of editors draft w3c/deviceorientation#81.
-
w3c/orientation-sensor
-
1 pull request opened.
-
[orientation-sensor] Align with Web IDL specification w3c/orientation-sensor#66, by @autokagami.
-
-
1 pull request merged.
-
[orientation-sensor] Align with Web IDL specification w3c/orientation-sensor#66.
-
w3c/proximity
-
1 issue received 1 new comment.
-
1 pull request opened.
-
[proximity] Align with Web IDL specification w3c/proximity#42, by @autokagami.
-
-
1 pull request merged.
-
[proximity] Align with Web IDL specification w3c/proximity#42.
-
w3c/contact-picker
-
1 issue opened.
-
Iterator getter is not callable w3c/contact-picker#25, by @ashinzekene.
-
-
1 issue closed.
-
Iterator getter is not callable w3c/contact-picker#25.
-
-
2 issues received 7 new comments.
-
2 pull requests opened.
-
Add feature detection & create the concept of a Contacts Source. w3c/contact-picker#26, by @rayankans.
-
Support sharing addresses w3c/contact-picker#24, by @rayankans.
-
-
1 pull request merged.
-
Support sharing addresses w3c/contact-picker#24.
-
-
2 pull requests received 4 new comments.
-
Add feature detection & create the concept of a Contacts Source. w3c/contact-picker#26 (1 comment by @rayankans)
w3c/das-wg
-
1 issue received 2 new comments.
-
DAS WG TPAC F2F agenda (Fukuoka, Sep 19-20 2019) w3c/das-wg#24 (2 comments by @maryammjd, @satakagi)
-
w3c/geolocation
-
3 issues closed.
-
Suggest adding a PositionError entry for requests denied because of origin w3c/geolocation#11.
-
Restrict interfaces to secure contexts? w3c/geolocation#25.
-
3 issues received 4 new comments.
-
Disable geolocation by default in cross-origin iframes w3c/geolocation#10 (2 comments by @flaki, @reillyeon)
-
What error should be returned when trying to access position from insecure origin? w3c/geolocation#12 (1 comment by @reillyeon)
-
Suggest adding a PositionError entry for requests denied because of origin w3c/geolocation#11 (1 comment by @reillyeon)
-
-
1 pull request merged.
-
Add SecureContext and API behavior of browsers w3c/geolocation#34.
-
-
1 pull request received 4 new comments.
-
Add SecureContext and API behavior of browsers w3c/geolocation#34 (4 comments by @anssiko, @marcoscaceres)
-
w3c/accelerometer
-
1 pull request opened.
-
Use new constructor() syntax w3c/accelerometer#53, by @saschanaz.
-
-
1 pull request merged.
-
Use new constructor() syntax w3c/accelerometer#53.
-
-
1 pull request received 2 new comments.
Participants
-
1 organization joined.
-
Mozilla Foundation joined.
-
GitHub
w3c/deviceorientation
-
1 issue opened.
-
Update to constructor operations w3c/deviceorientation#80, by @Ms2ger.
-
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
Add explicit [Exposed] w3c/deviceorientation#79, by @saschanaz.
-
Align with IDL dictionary changes w3c/deviceorientation#78, by @anssiko.
-
-
2 pull requests merged.
-
Add explicit [Exposed] w3c/deviceorientation#79.
-
Align with IDL dictionary changes w3c/deviceorientation#78.
-
-
1 pull request received 5 new comments.
w3c/ambient-light
-
1 issue opened.
-
Update to constructor operations w3c/ambient-light#60, by @Ms2ger.
-
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
Add a new editor w3c/ambient-light#59, by @anssiko.
-
Align with IDL dictionary changes w3c/ambient-light#58, by @anssiko.
-
-
1 pull request merged.
-
Align with IDL dictionary changes w3c/ambient-light#58.
-
w3c/geolocation
-
3 issues opened.
-
Editor's Draft is not listed in W3C w3c/geolocation#35, by @saschanaz.
-
Move to WICG w3c/geolocation#29, by @marcoscaceres.
-
Enable tls for gh-pages w3c/geolocation#28, by @marcoscaceres.
-
-
3 issues closed.
-
Editor's Draft is not listed in W3C w3c/geolocation#35.
-
Move to WICG w3c/geolocation#29.
-
Enable tls for gh-pages w3c/geolocation#28.
-
-
4 issues received 19 new comments.
-
Restrict interfaces to secure contexts? w3c/geolocation#25 (7 comments by @annevk, @foolip, @marcoscaceres)
-
Editor's Draft is not listed in W3C w3c/geolocation#35 (6 comments by @anssiko, @deniak, @saschanaz, @xfq)
-
-
7 pull requests opened.
-
Tidy up document w3c/geolocation#36, by @marcoscaceres.
-
Add SecureContext and API behavior of browsers w3c/geolocation#34, by @marcoscaceres.
-
Editorial: fix xrefs w3c/geolocation#33, by @marcoscaceres.
-
Editorial: Add Exposed extended attribute w3c/geolocation#32, by @marcoscaceres.
-
chore: add pull request template w3c/geolocation#31, by @marcoscaceres.
-
Update metadata w3c/geolocation#30, by @anssiko.
-
Align with IDL dictionary changes w3c/geolocation#27, by @anssiko.
-
-
5 pull requests merged.
-
Editorial: fix xrefs w3c/geolocation#33.
-
Editorial: Add Exposed extended attribute w3c/geolocation#32.
-
chore: add pull request template w3c/geolocation#31.
-
Update metadata w3c/geolocation#30.
-
Align with IDL dictionary changes w3c/geolocation#27.
-
-
6 pull requests received 54 new comments.
-
Remove [NoInterfaceObject] w3c/geolocation#20 (18 comments by @anssiko, @cdumez, @marcoscaceres, @reillyeon)
-
Add SecureContext and API behavior of browsers w3c/geolocation#34 (15 comments by @annevk, @anssiko, @cdumez, @foolip, @marcoscaceres, @reillyeon)
-
Editorial: Add Exposed extended attribute w3c/geolocation#32 (5 comments by @anssiko, @marcoscaceres)
-
w3c/das-wg
-
1 issue received 4 new comments.
w3c/screen-wake-lock
-
1 issue opened.
-
WakeLock.request() returns a promise that never resolves w3c/screen-wake-lock#226, by @tomayac.
-
-
1 issue closed.
-
Handling WakeLock.request() promises in parallel steps w3c/screen-wake-lock#222.
-
-
5 issues received 22 new comments.
-
WakeLock and only require activation once w3c/screen-wake-lock#139 (7 comments by @cterefinko, @kenchris, @rakuco, @tomayac)
-
WakeLock.request() returns a promise that never resolves w3c/screen-wake-lock#226 (7 comments by @marcoscaceres, @reillyeon, @tomayac)
-
Need to add "wake-lock" to permissions registry w3c/screen-wake-lock#184 (5 comments by @anssiko, @marcoscaceres)
-
In obtain permission: don't co-opt resultPromise - it's creating a custom permission model w3c/screen-wake-lock#198 (2 comments by @anssiko, @marcoscaceres)
-
Handling WakeLock.request() promises in parallel steps w3c/screen-wake-lock#222 (1 comment by @anssiko)
-
-
5 pull requests opened.
-
Remove paragraph about events and disclosing state in the Security section w3c/screen-wake-lock#231, by @rakuco.
-
Remove the note on page visibility handling from WakeLock.request() w3c/screen-wake-lock#230, by @rakuco.
-
Travis: Remove a few extra repositories now that we use Ubuntu Xenial w3c/screen-wake-lock#229, by @rakuco.
-
Travis: Adapt to Ubuntu Xenial being the default. w3c/screen-wake-lock#228, by @rakuco.
-
Add another condition to WakeLock.request()'s "abort when" block. w3c/screen-wake-lock#227, by @rakuco.
-
-
5 pull requests merged.
-
Remove paragraph about events and disclosing state in the Security section w3c/screen-wake-lock#231.
-
Remove the note on page visibility handling from WakeLock.request() w3c/screen-wake-lock#230.
-
Add another condition to WakeLock.request()'s "abort when" block. w3c/screen-wake-lock#227.
-
Travis: Remove a few extra repositories now that we use Ubuntu Xenial w3c/screen-wake-lock#229.
-
Travis: Adapt to Ubuntu Xenial being the default. w3c/screen-wake-lock#228.
-
-
3 pull requests received 4 new comments.
-
Travis: Adapt to Ubuntu Xenial being the default. w3c/screen-wake-lock#228 (2 comments by @anssiko, @rakuco)
-
Travis: Remove a few extra repositories now that we use Ubuntu Xenial w3c/screen-wake-lock#229 (1 comment by @rakuco)
-
Add another condition to WakeLock.request()'s "abort when" block. w3c/screen-wake-lock#227 (1 comment by @rakuco)
-
w3c/proximity
-
2 issues opened.
-
Published spec out of date w3c/proximity#41, by @Ms2ger.
-
Update spec to new IDL syntax for optional dictionaries w3c/proximity#40, by @Ms2ger.
-
-
1 issue closed.
-
Update spec to new IDL syntax for optional dictionaries w3c/proximity#40.
-
-
2 issues received 2 new comments.
-
1 pull request opened.
-
Align with IDL dictionary changes w3c/proximity#39, by @anssiko.
-
-
1 pull request merged.
-
Align with IDL dictionary changes w3c/proximity#39.
-
w3c/battery
-
1 issue closed.
-
Status of this API w3c/battery#23.
-
-
1 issue received 3 new comments.
-
1 pull request received 1 new comment.
-
Allow use in same-origin children, add Feature Policy integration w3c/battery#13 (1 comment by @anssiko)
-
w3c/sensors
-
1 issue received 2 new comments.
-
Allowing data batching when poll frequency < sensor frequency w3c/sensors#13 (2 comments by @anssiko, @robman)
-
-
1 pull request opened.
-
Align with IDL dictionary changes w3c/sensors#391, by @anssiko.
-
-
1 pull request merged.
-
Align with IDL dictionary changes w3c/sensors#391.
-
w3c/contact-picker
-
2 issues opened.
-
Closer HTML alignment w3c/contact-picker#21, by @marcoscaceres.
-
We REALLY need this! w3c/contact-picker#20, by @marcoscaceres.
-
-
4 issues received 36 new comments.
-
Closer HTML alignment w3c/contact-picker#21 (16 comments by @aarongustafson, @beverloo, @marcoscaceres, @markcellus, @rayankans, @tomayac)
-
Consider contact API that does not reveal contact info to the website w3c/contact-picker#7 (7 comments by @dtruffaut, @Gozala, @rayankans, @tomayac)
-
We REALLY need this! w3c/contact-picker#20 (7 comments by @aarongustafson, @beverloo, @marcoscaceres, @rayankans)
-
Detect which contact properties are supported by the browser w3c/contact-picker#19 (6 comments by @domenic, @rayankans)
-
-
2 pull requests opened.
-
Use an interface for ContactInfo & set unrequested fields to null. w3c/contact-picker#23, by @rayankans.
-
Use an interface for ContactInfo & set unrequested fields to null. w3c/contact-picker#22, by @rayankans.
-
-
1 pull request merged.
-
Copy edit the README. w3c/contact-picker#18.
-
-
2 pull requests closed.
-
Use an interface for ContactInfo & set unrequested fields to null. w3c/contact-picker#23.
-
Use an interface for ContactInfo & set unrequested fields to null. w3c/contact-picker#22.
-
-
2 pull requests received 5 new comments.
-
Use an interface for ContactInfo & set unrequested fields to null. w3c/contact-picker#23 (4 comments by @beverloo, @domenic, @rayankans, @yoavweiss)
-
w3c/orientation-sensor
-
1 pull request opened.
-
Align with IDL dictionary changes w3c/orientation-sensor#65, by @anssiko.
-
-
1 pull request merged.
-
Align with IDL dictionary changes w3c/orientation-sensor#65.
-
w3c/gyroscope
-
1 pull request opened.
-
Align with IDL dictionary changes w3c/gyroscope#43, by @anssiko.
-
-
1 pull request merged.
-
Align with IDL dictionary changes w3c/gyroscope#43.
-
w3c/accelerometer
-
1 pull request opened.
-
Align with IDL dictionary changes w3c/accelerometer#52, by @anssiko.
-
-
1 pull request merged.
-
Align with IDL dictionary changes w3c/accelerometer#52.
-
w3c/magnetometer
-
1 pull request opened.
-
Align with IDL dictionary changes w3c/magnetometer#53, by @anssiko.
-
-
1 pull request merged.
-
Align with IDL dictionary changes w3c/magnetometer#53.
-
-
1 pull request received 1 new comment.
Participants
-
2 participants joined.
-
Joshue O'Connor (W3C) joined.
-
Ehsan Toreini (Samsung Electronics Co., Ltd.) joined.
-
GitHub
w3c/contact-picker
-
1 issue opened.
-
Detect which contact properties are supported by the browser w3c/contact-picker#19, by @rayankans.
-
-
2 issues received 3 new comments.
-
Contacts Picker UI should have a "Select All" option w3c/contact-picker#15 (2 comments by @comp615, @rayankans)
-
-
1 pull request opened.
-
Copy edit the README. w3c/contact-picker#18, by @jpmedley.
-
-
1 pull request received 3 new comments.
w3c/sensors
-
1 issue received 1 new comment.
w3c/screen-wake-lock
-
3 pull requests opened.
-
chore: fix ReSpec xref errors w3c/screen-wake-lock#225, by @marcoscaceres.
-
Release wake lock: Adjust order of the items in the algorithm w3c/screen-wake-lock#224, by @rakuco.
-
Specify a default value for |options| in WakeLock.request() w3c/screen-wake-lock#223, by @rakuco.
-
-
3 pull requests merged.
-
chore: fix ReSpec xref errors w3c/screen-wake-lock#225.
-
Release wake lock: Adjust order of the items in the algorithm w3c/screen-wake-lock#224.
-
Specify a default value for |options| in WakeLock.request() w3c/screen-wake-lock#223.
-
-
1 pull request reopened.
-
Specify a default value for |options| in WakeLock.request() w3c/screen-wake-lock#223, by @rakuco.
-
-
2 pull requests received 9 new comments.
-
chore: fix ReSpec xref errors w3c/screen-wake-lock#225 (8 comments by @kenchris, @marcoscaceres, @rakuco, @siusin)
-
Release wake lock: Adjust order of the items in the algorithm w3c/screen-wake-lock#224 (1 comment by @rakuco)
-
w3c/battery
-
1 issue opened.
-
Status of this API w3c/battery#23, by @robinglen.
-
w3c/html-media-capture
-
1 issue opened.
-
It is unclear that .capture getter should return when the state is "implementation-specific" w3c/html-media-capture#33, by @smaug----.
-
-
1 issue closed.
-
It is unclear that .capture getter should return when the state is "implementation-specific" w3c/html-media-capture#33.
-
-
1 issue received 1 new comment.
-
It is unclear that .capture getter should return when the state is "implementation-specific" w3c/html-media-capture#33 (1 comment by @smaug----)
-
w3c/deviceorientation
-
1 issue opened.
-
DeviceMotion only works once at init and return null value w3c/deviceorientation#77, by @NjnuTZhou.
-
-
1 issue closed.
-
DeviceMotion only works once at init and return null value w3c/deviceorientation#77.
-
-
1 issue received 2 new comments.
-
DeviceMotion only works once at init and return null value w3c/deviceorientation#77 (2 comments by @NjnuTZhou, @reillyeon)
-
w3c/das-wg
-
1 issue received 1 new comment.
Participants
-
1 organization joined.
-
Bocoup joined.
-
GitHub
w3c/das-wg
-
1 issue opened.
-
DAS WG TPAC F2F agenda (Fukuoka, Sep 19-20 2019) w3c/das-wg#24, by @anssiko.
-
-
2 issues closed.
-
DAS WG TPAC F2F agenda proposals w3c/das-wg#22.
-
Edge renders roadmap maturity stages in wrong orientation w3c/das-wg#17.
-
-
3 issues received 6 new comments.
-
DAS WG TPAC F2F agenda (Fukuoka, Sep 19-20 2019) w3c/das-wg#24 (4 comments by @anssiko, @maryammjd, @tomayac)
-
w3c/screen-wake-lock
-
1 issue opened.
-
Handling WakeLock.request() promises in parallel steps w3c/screen-wake-lock#222, by @rakuco.
-
-
2 issues received 16 new comments.
-
Need maximum screen brightness mode w3c/screen-wake-lock#129 (12 comments by @aarongustafson, @marcoscaceres, @mounirlamouri, @tomayac)
-
Handling WakeLock.request() promises in parallel steps w3c/screen-wake-lock#222 (4 comments by @kenchris, @rakuco)
-
-
1 pull request opened.
-
Always reject |lockPromise| in "release wake lock". w3c/screen-wake-lock#221, by @rakuco.
-
-
1 pull request merged.
-
Always reject |lockPromise| in "release wake lock". w3c/screen-wake-lock#221.
-
w3c/vibration
-
1 pull request opened.
-
Update references [HTML5] -> [HTML] w3c/vibration#23, by @anssiko.
-
-
1 pull request merged.
-
Update references [HTML5] -> [HTML] w3c/vibration#23.
-
-
1 pull request received 1 new comment.
w3c/battery
-
3 pull requests opened.
-
Add EventTarget definition w3c/battery#22, by @anssiko.
-
Update references to HTML and DOM w3c/battery#21, by @xfq.
-
Remove processVersion w3c/battery#20, by @xfq.
-
-
3 pull requests merged.
-
Add EventTarget definition w3c/battery#22.
-
Update references to HTML and DOM w3c/battery#21.
-
Remove processVersion w3c/battery#20.
-
-
3 pull requests received 3 new comments.
-
Allow use in same-origin children, add Feature Policy integration w3c/battery#13 (1 comment by @anssiko)
-
w3c/contact-picker
-
1 issue closed.
-
Spec feedback w3c/contact-picker#17.
-
-
3 issues received 3 new comments.
-
Contacts Picker UI should have a "Select All" option w3c/contact-picker#15 (1 comment by @aarongustafson)
-
w3c/proximity
-
1 issue closed.
-
In centimeters... min/max privacy issue? w3c/proximity#10.
-
-
1 issue received 1 new comment.
w3c/deviceorientation
-
1 issue closed.
-
Define the relationship between device orientation/motion events and screen orientation in the spec w3c/deviceorientation#4.
-
-
2 issues received 2 new comments.
-
Define the relationship between device orientation/motion events and screen orientation in the spec w3c/deviceorientation#4 (1 comment by @anssiko)
-
Add API for requesting permission to receive device motion / orientation events w3c/deviceorientation#57 (1 comment by @cdumez)
-
w3c/geolocation
-
1 pull request opened.
-
Add .pr-preview.json w3c/geolocation#26, by @xfq.
-
-
1 pull request merged.
-
Add .pr-preview.json w3c/geolocation#26.
-
-
1 pull request received 1 new comment.
w3c/sensors
-
1 issue received 1 new comment.
w3c/ambient-light
-
1 issue received 1 new comment.
Participants
-
1 participant joined.
-
Lars Knudsen (W3C Invited Experts) joined.
-
-
1 organization joined.
-
Mitsubishi Electric Corporation joined.
-
GitHub
w3c/contact-picker
-
3 issues opened.
-
Spec feedback w3c/contact-picker#17, by @jakearchibald.
-
Save contact? w3c/contact-picker#16, by @vladimirbrasil.
-
Contacts Picker UI should have a "Select All" option w3c/contact-picker#15, by @adityapunjani.
-
-
3 issues received 5 new comments.
-
Contacts Picker UI should have a "Select All" option w3c/contact-picker#15 (2 comments by @laukstein, @rayankans)
-
1 pull request merged.
-
Create a spec skeleton with a few filled out parts. w3c/contact-picker#14.
-
-
1 pull request received 12 new comments.
-
Create a spec skeleton with a few filled out parts. w3c/contact-picker#14 (12 comments by @beverloo, @rayankans)
-
w3c/ambient-light
-
1 issue received 1 new comment.
w3c/screen-wake-lock
-
6 issues opened.
-
ReSpec is complaining about some spec references w3c/screen-wake-lock#219, by @rakuco.
-
New API with AbortController is not intuitive for developers. w3c/screen-wake-lock#214, by @mrunalk.
-
Avoid cases like |options|.|signal| as that creates a new variable signal w3c/screen-wake-lock#208, by @kenchris.
-
Avoid cases like |options w3c/screen-wake-lock#207, by @kenchris.
-
Page visibility and browsing contexts w3c/screen-wake-lock#206, by @rakuco.
-
request(): Order for permission and other checks w3c/screen-wake-lock#202, by @rakuco.
-
-
9 issues closed.
-
ReSpec is complaining about some spec references w3c/screen-wake-lock#219.
-
Page visibility and browsing contexts w3c/screen-wake-lock#206.
-
New API with AbortController is not intuitive for developers. w3c/screen-wake-lock#214.
-
Avoid cases like |options|.|signal| as that creates a new variable signal w3c/screen-wake-lock#208.
-
Avoid cases like |options w3c/screen-wake-lock#207.
-
Clarify platform wake lock's internal slots have different contexts w3c/screen-wake-lock#192.
-
Lifetime of WakeLock w3c/screen-wake-lock#195.
-
Losing reference to a WakeLock object is a bug or intended behavior w3c/screen-wake-lock#199.
-
Canceling using AbortSignal is a bit weird w3c/screen-wake-lock#171.
-
-
1 issue reopened.
-
Losing reference to a WakeLock object is a bug or intended behavior w3c/screen-wake-lock#199, by @kenchris.
-
-
8 issues received 27 new comments.
-
request(): Order for permission and other checks w3c/screen-wake-lock#202 (8 comments by @annevk, @kenchris, @marcoscaceres, @rakuco)
-
Losing reference to a WakeLock object is a bug or intended behavior w3c/screen-wake-lock#199 (7 comments by @jakearchibald, @kenchris, @marcoscaceres, @reillyeon)
-
Avoid cases like |options|.|signal| as that creates a new variable signal w3c/screen-wake-lock#208 (3 comments by @rakuco, @reillyeon)
-
Page visibility and browsing contexts w3c/screen-wake-lock#206 (3 comments by @kenchris, @rakuco, @reillyeon)
-
ReSpec is complaining about some spec references w3c/screen-wake-lock#219 (2 comments by @marcoscaceres, @rakuco)
-
New API with AbortController is not intuitive for developers. w3c/screen-wake-lock#214 (2 comments by @kenchris, @rakuco)
-
-
15 pull requests opened.
-
chore: fix ReSpec xref errors w3c/screen-wake-lock#220, by @marcoscaceres.
-
Add myself to the "Acknowledgments" section. w3c/screen-wake-lock#218, by @rakuco.
-
Explain why WakeLock.request() has no "if aborted" step. w3c/screen-wake-lock#217, by @rakuco.
-
Adjust the "Release Wake Lock" algorithm after #209 w3c/screen-wake-lock#216, by @rakuco.
-
Tweak a bit on the description of WakeLock interface w3c/screen-wake-lock#215, by @Honry.
-
Tweak reference to Page Lifecycle's "frozen" definition. w3c/screen-wake-lock#213, by @rakuco.
-
Make page visibility checks use the resposible document. w3c/screen-wake-lock#212, by @rakuco.
-
Make index.html pass tidy's checks after #201 w3c/screen-wake-lock#211, by @rakuco.
-
Fix the checkbox example after #201 w3c/screen-wake-lock#210, by @rakuco.
-
Fix AbortSignal handling in WakeLock.request() after #201 w3c/screen-wake-lock#209, by @rakuco.
-
chore(.travis): use GET instead of HEAD for ReSpec validator w3c/screen-wake-lock#205, by @marcoscaceres.
-
Make WakeLockRequestOptions' signal non-nullable, do not set a default w3c/screen-wake-lock#204, by @rakuco.
-
Do not assign a default value to WakeLockRequestOptions.signal w3c/screen-wake-lock#203, by @rakuco.
-
Move to new static API as agreed upon w3c/screen-wake-lock#201, by @kenchris.
-
Remove query(), fixes #199 w3c/screen-wake-lock#200, by @kenchris.
-
-
14 pull requests merged.
-
chore: fix ReSpec xref errors w3c/screen-wake-lock#220.
-
Explain why WakeLock.request() has no "if aborted" step. w3c/screen-wake-lock#217.
-
Add myself to the "Acknowledgments" section. w3c/screen-wake-lock#218.
-
Make WakeLockRequestOptions' signal non-nullable, do not set a default w3c/screen-wake-lock#204.
-
Adjust the "Release Wake Lock" algorithm after #209 w3c/screen-wake-lock#216.
-
Fix AbortSignal handling in WakeLock.request() after #201 w3c/screen-wake-lock#209.
-
Tweak a bit on the description of WakeLock interface w3c/screen-wake-lock#215.
-
Make page visibility checks use the resposible document. w3c/screen-wake-lock#212.
-
Fix the checkbox example after #201 w3c/screen-wake-lock#210.
-
Tweak reference to Page Lifecycle's "frozen" definition. w3c/screen-wake-lock#213.
-
Make index.html pass tidy's checks after #201 w3c/screen-wake-lock#211.
-
Move to new static API as agreed upon w3c/screen-wake-lock#201.
-
chore(.travis): use GET instead of HEAD for ReSpec validator w3c/screen-wake-lock#205.
-
Remove query(), fixes #199 w3c/screen-wake-lock#200.
-
-
3 pull requests closed.
-
Create PULL_REQUEST_TEMPLATE.md w3c/screen-wake-lock#168.
-
Do not assign a default value to WakeLockRequestOptions.signal w3c/screen-wake-lock#203.
-
Allow to abort a request using an aborted signal w3c/screen-wake-lock#183.
-
-
12 pull requests received 81 new comments.
-
Move to new static API as agreed upon w3c/screen-wake-lock#201 (43 comments by @kenchris, @rakuco, @reillyeon)
-
Fix AbortSignal handling in WakeLock.request() after #201 w3c/screen-wake-lock#209 (7 comments by @kenchris, @rakuco, @reillyeon)
-
Adjust the "Release Wake Lock" algorithm after #209 w3c/screen-wake-lock#216 (6 comments by @kenchris, @rakuco)
-
Make WakeLockRequestOptions' signal non-nullable, do not set a default w3c/screen-wake-lock#204 (5 comments by @marcoscaceres, @rakuco)
-
Make page visibility checks use the resposible document. w3c/screen-wake-lock#212 (3 comments by @kenchris, @rakuco)
-
chore(.travis): use GET instead of HEAD for ReSpec validator w3c/screen-wake-lock#205 (3 comments by @marcoscaceres, @rakuco)
-
Do not assign a default value to WakeLockRequestOptions.signal w3c/screen-wake-lock#203 (3 comments by @kenchris, @marcoscaceres, @rakuco)
-
Tweak a bit on the description of WakeLock interface w3c/screen-wake-lock#215 (1 comment by @rakuco)
-
w3c/sensors
-
1 issue received 3 new comments.
w3c/deviceorientation
-
1 issue received 7 new comments.
-
Add API for requesting permission to receive device motion / orientation events w3c/deviceorientation#57 (7 comments by @cdumez, @micsun-al, @nbutko, @reillyeon)
-
TR publications
-
1 document published.
-
DeviceOrientation Event Specification published as a Working Draft. History of DeviceOrientation Event Specification
-
Participants
-
1 participant joined.
-
Lukasz Olejnik (W3C Invited Experts) joined.
-
-
4 organizations joined.
-
Fraunhofer Gesellschaft joined.
-
CoSMo Software Consulting Pte Ltd joined.
-
Google LLC joined.
-
Ecole Mohammadia d'Ingenieurs Rabat (EMI) joined.
-
GitHub
w3c/screen-wake-lock
-
12 issues opened.
-
Losing reference to a WakeLock object is a bug or intended behavior w3c/screen-wake-lock#199, by @reillyeon.
-
In obtain permission: don't co-opt resultPromise - it's creating a custom permission model w3c/screen-wake-lock#198, by @kenchris.
-
Lifetime of WakeLock w3c/screen-wake-lock#195, by @marcoscaceres.
-
Clarify platform wake lock's internal slots have different contexts w3c/screen-wake-lock#192, by @rakuco.
-
obtain permission seems wrong w3c/screen-wake-lock#187, by @marcoscaceres.
-
WakeLockPermissionDescriptor should be it's own section w3c/screen-wake-lock#186, by @marcoscaceres.
-
Use real instances of things w3c/screen-wake-lock#185, by @marcoscaceres.
-
Need to add "wake-lock" to permissions registry w3c/screen-wake-lock#184, by @marcoscaceres.
-
Rename system to compute or similar w3c/screen-wake-lock#177, by @kenchris.
-
screen wake lock should be able to make use of proximy sensor w3c/screen-wake-lock#175, by @kenchris.
-
Canceling using AbortSignal is a bit weird w3c/screen-wake-lock#171, by @kenchris.
-
Add "geolocation" wake lock w3c/screen-wake-lock#170, by @kenchris.
-
-
7 issues closed.
-
WakeLockPermissionDescriptor should be it's own section w3c/screen-wake-lock#186.
-
Rename system to compute or similar w3c/screen-wake-lock#177.
-
API to get list of active wake locks w3c/screen-wake-lock#133.
-
More diplay power modes w3c/screen-wake-lock#84.
-
What do the wakelocks actually do? w3c/screen-wake-lock#138.
-
Give advice on how UAs should infer consent to take a wakelock w3c/screen-wake-lock#140.
-
Requesting wake locks from Workers w3c/screen-wake-lock#156.
-
-
1 issue reopened.
-
Canceling using AbortSignal is a bit weird w3c/screen-wake-lock#171, by @reillyeon.
-
-
12 issues received 30 new comments.
-
Canceling using AbortSignal is a bit weird w3c/screen-wake-lock#171 (8 comments by @domenic, @kenchris, @reillyeon, @tomayac)
-
screen wake lock should be able to make use of proximy sensor w3c/screen-wake-lock#175 (3 comments by @kenchris, @reillyeon)
-
Add "geolocation" wake lock w3c/screen-wake-lock#170 (3 comments by @kenchris, @reillyeon, @tomayac)
-
Need to add "wake-lock" to permissions registry w3c/screen-wake-lock#184 (2 comments by @kenchris, @marcoscaceres)
-
Introduce rate limiting to prevent wake lock abuse w3c/screen-wake-lock#124 (2 comments by @kenchris, @reillyeon)
-
Give advice on how UAs should infer consent to take a wakelock w3c/screen-wake-lock#140 (1 comment by @kenchris)
-
-
20 pull requests opened.
-
Fix Marcos' issues #186 and #185 w3c/screen-wake-lock#197, by @kenchris.
-
Add more type info w3c/screen-wake-lock#196, by @kenchris.
-
Add back AbortSignal and other misc fixes from review cycles w3c/screen-wake-lock#194, by @kenchris.
-
More editorial fixes w3c/screen-wake-lock#193, by @marcoscaceres.
-
Remove the "outstanding wake lock request" definition. w3c/screen-wake-lock#191, by @rakuco.
-
Stop referencing "feature name" from the Feature Policy spec w3c/screen-wake-lock#190, by @rakuco.
-
examples: Do not make tryKeepScreenAlive() async w3c/screen-wake-lock#189, by @rakuco.
-
Fix formatting in WakeLock.request()'s description w3c/screen-wake-lock#188, by @rakuco.
-
Allow to abort a request using an aborted signal w3c/screen-wake-lock#183, by @kenchris.
-
Editorial: few more fixes w3c/screen-wake-lock#182, by @marcoscaceres.
-
Respec redux w3c/screen-wake-lock#181, by @kenchris.
-
Respec redux w3c/screen-wake-lock#180, by @kenchris.
-
Editorial: update to use more modern ReSpec stuff w3c/screen-wake-lock#179, by @marcoscaceres.
-
Introduce abort() instead of AbortSignal after discussions w3c/screen-wake-lock#178, by @kenchris.
-
chore(.travis.yml): enable ReSpec validation w3c/screen-wake-lock#176, by @xfq.
-
Improve introduction w3c/screen-wake-lock#173, by @kenchris.
-
Add query() method to receive WakeLock instances w3c/screen-wake-lock#172, by @kenchris.
-
Fix comments from Marcos regarding permissions w3c/screen-wake-lock#169, by @kenchris.
-
Create PULL_REQUEST_TEMPLATE.md w3c/screen-wake-lock#168, by @marcoscaceres.
-
-
17 pull requests merged.
-
Fix Marcos' issues #186 and #185 w3c/screen-wake-lock#197.
-
Add more type info w3c/screen-wake-lock#196.
-
Add back AbortSignal and other misc fixes from review cycles w3c/screen-wake-lock#194.
-
More editorial fixes w3c/screen-wake-lock#193.
-
Remove the "outstanding wake lock request" definition. w3c/screen-wake-lock#191.
-
Stop referencing "feature name" from the Feature Policy spec w3c/screen-wake-lock#190.
-
examples: Do not make tryKeepScreenAlive() async w3c/screen-wake-lock#189.
-
Fix formatting in WakeLock.request()'s description w3c/screen-wake-lock#188.
-
Editorial: few more fixes w3c/screen-wake-lock#182.
-
Respec redux w3c/screen-wake-lock#181.
-
Introduce abort() instead of AbortSignal after discussions w3c/screen-wake-lock#178.
-
chore(.travis.yml): enable ReSpec validation w3c/screen-wake-lock#176.
-
Editorial w3c/screen-wake-lock#174.
-
Add query() method to receive WakeLock instances w3c/screen-wake-lock#172.
-
Improve introduction w3c/screen-wake-lock#173.
-
Fix comments from Marcos regarding permissions w3c/screen-wake-lock#169.
-
Add static requestPermission method on Window w3c/screen-wake-lock#167.
-
-
2 pull requests closed.
-
Respec redux w3c/screen-wake-lock#180.
-
Editorial: update to use more modern ReSpec stuff w3c/screen-wake-lock#179.
-
-
1 pull request reopened.
-
Respec redux w3c/screen-wake-lock#180, by @kenchris.
-
-
13 pull requests received 170 new comments.
-
Allow to abort a request using an aborted signal w3c/screen-wake-lock#183 (44 comments by @domenic, @jakearchibald, @kenchris, @marcoscaceres, @reillyeon)
-
Create PULL_REQUEST_TEMPLATE.md w3c/screen-wake-lock#168 (35 comments by @anssiko, @chrisdavidmills, @foolip, @kenchris, @marcoscaceres, @reillyeon, @xfq)
-
Add static requestPermission method on Window w3c/screen-wake-lock#167 (21 comments by @kenchris, @marcoscaceres)
-
chore(.travis.yml): enable ReSpec validation w3c/screen-wake-lock#176 (14 comments by @anssiko, @marcoscaceres, @tobie)
-
Fix Marcos' issues #186 and #185 w3c/screen-wake-lock#197 (12 comments by @anssiko, @kenchris, @marcoscaceres)
-
Editorial: update to use more modern ReSpec stuff w3c/screen-wake-lock#179 (12 comments by @kenchris, @marcoscaceres, @sidvishnoi)
-
Add back AbortSignal and other misc fixes from review cycles w3c/screen-wake-lock#194 (8 comments by @kenchris, @marcoscaceres)
-
Introduce abort() instead of AbortSignal after discussions w3c/screen-wake-lock#178 (8 comments by @kenchris, @reillyeon)
-
Add query() method to receive WakeLock instances w3c/screen-wake-lock#172 (6 comments by @kenchris, @littledan, @reillyeon)
-
Stop referencing "feature name" from the Feature Policy spec w3c/screen-wake-lock#190 (1 comment by @rakuco)
-
w3c/contact-picker
-
1 issue opened.
-
Provide access to contact's icon w3c/contact-picker#13, by @rayankans.
-
-
5 issues received 16 new comments.
-
Provide access to address properties w3c/contact-picker#12 (6 comments by @aarongustafson, @rayankans, @tomayac)
-
Consider Web Intents w3c/contact-picker#11 (5 comments by @aarongustafson, @darobin, @npdoty, @rayankans)
-
Add payerGivenName + payerFamilyName to PaymentAddress w3c/contact-picker#69 (1 comment by @marcoscaceres)
-
-
1 pull request opened.
-
Create a spec skeleton with a few filled out parts. w3c/contact-picker#14, by @rayankans.
-
w3c/deviceorientation
-
1 issue opened.
-
requestPermission() and event handling clarification w3c/deviceorientation#74, by @rakuco.
-
-
1 issue closed.
-
Add non-normative text describing the current deviceorientationabsolute implementation status w3c/deviceorientation#60.
-
-
2 issues received 9 new comments.
-
requestPermission() and event handling clarification w3c/deviceorientation#74 (7 comments by @anssiko, @cdumez, @reillyeon)
-
Add API for requesting permission to receive device motion / orientation events w3c/deviceorientation#57 (2 comments by @EvanBacon, @keithito)
-
-
4 pull requests opened.
-
Make NotAllowedError point to its definition in WebIDL. w3c/deviceorientation#76, by @rakuco.
-
Note implementation experience for permission model w3c/deviceorientation#75, by @anssiko.
-
Remove trailing comma from the PermissionState enum. w3c/deviceorientation#73, by @rakuco.
-
Update spec metadata w3c/deviceorientation#72, by @xfq.
-
-
4 pull requests merged.
-
Make NotAllowedError point to its definition in WebIDL. w3c/deviceorientation#76.
-
Note implementation experience for permission model w3c/deviceorientation#75.
-
Update spec metadata w3c/deviceorientation#72.
-
Note limited implementation experience w3c/deviceorientation#71.
-
-
1 pull request closed.
-
Remove trailing comma from the PermissionState enum. w3c/deviceorientation#73.
-
-
4 pull requests received 6 new comments.
-
Make NotAllowedError point to its definition in WebIDL. w3c/deviceorientation#76 (2 comments by @rakuco)
-
Remove trailing comma from the PermissionState enum. w3c/deviceorientation#73 (2 comments by @rakuco, @reillyeon)
-
w3c/geolocation
-
1 issue received 1 new comment.
-
Support geolocation (especially geofencing) in the "background" w3c/geolocation#214 (1 comment by @hadriann)
-
Lifecycle
-
1 charter started.
-
Chartered until 30 June 2020. Participants had to rejoin under this charter.
-
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 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
-
Proximity Sensor published as a Working Draft. History of Proximity Sensor
-
Participants
-
2 participants joined.
-
Maryam Mehrnezhad (W3C Invited Experts) joined.
-
Fuqiao Xue (W3C) joined.
-
-
4 participants left.
-
Lars Knudsen (W3C Invited Experts) left.
-
Fuqiao Xue (W3C) left.
-
Lukasz Olejnik (W3C Invited Experts) left.
-
Andrey Logvinov (W3C Invited Experts) left.
-
-
1 organization joined.
-
Intel Corporation joined.
-
-
11 organizations left.
-
HTML5 Converged Technology Forum left.
-
Inswave Co., Ltd. left.
-
Privakey, Inc. left.
-
Google LLC left.
-
Ecole Mohammadia d'Ingenieurs Rabat (EMI) left.
-
Intel Corporation left.
-
Orange left.
-
Bocoup left.
-
Mitsubishi Electric Corporation left.
-
CoSMo Software Consulting Pte Ltd left.
-
Fraunhofer Gesellschaft left.
-
GitHub
w3c/screen-wake-lock
-
5 issues opened.
-
Throw "AbortError" DOMException w3c/screen-wake-lock#162, by @Honry.
-
SecurityError vs NotAllowedError w3c/screen-wake-lock#159, by @kenchris.
-
Requesting wake locks from Workers w3c/screen-wake-lock#156, by @reillyeon.
-
Consider making WakeLock constructable w3c/screen-wake-lock#154, by @kenchris.
-
-
8 issues closed.
-
Throw "AbortError" DOMException w3c/screen-wake-lock#162.
-
Subtleties of using Document are not specced w3c/screen-wake-lock#141.
-
Make WakeLock require user gesture before activation w3c/screen-wake-lock#135.
-
SecurityError vs NotAllowedError w3c/screen-wake-lock#159.
-
Consider making WakeLock constructable w3c/screen-wake-lock#154.
-
Low battery while wake lock is on should cancel the lock w3c/screen-wake-lock#132.
-
What if WakeLockRequest is garbage collected? w3c/screen-wake-lock#128.
-
-
1 issue reopened.
-
Give advice on how UAs should infer consent to take a wakelock w3c/screen-wake-lock#140, by @kenchris.
-
-
12 issues received 34 new comments.
-
Subtleties of using Document are not specced w3c/screen-wake-lock#141 (10 comments by @domenic, @kenchris, @reillyeon, @tomayac)
-
Requesting wake locks from Workers w3c/screen-wake-lock#156 (8 comments by @kenchris, @mrunalk, @reillyeon)
-
Give advice on how UAs should infer consent to take a wakelock w3c/screen-wake-lock#140 (2 comments by @Ajedi32, @jyasskin)
-
Consider making WakeLock constructable w3c/screen-wake-lock#154 (2 comments by @kenchris, @reillyeon)
-
What if WakeLockRequest is garbage collected? w3c/screen-wake-lock#128 (2 comments by @anssiko, @kenchris)
-
Make WakeLock require user gesture before activation w3c/screen-wake-lock#135 (1 comment by @kenchris)
-
A broken script shouldn't be able to put the whole system in a broken state until page reloaded, I think something is broken. w3c/screen-wake-lock#151 (1 comment by @reillyeon)
-
-
12 pull requests opened.
-
Add static requestPermission method on Window w3c/screen-wake-lock#167, by @kenchris.
-
Fix Marcos' comments w3c/screen-wake-lock#166, by @kenchris.
-
Modernize Respec usage w3c/screen-wake-lock#165, by @kenchris.
-
Attempt to improve the permission flow/steps w3c/screen-wake-lock#164, by @kenchris.
-
Fix #162 - missing rejection steps w3c/screen-wake-lock#163, by @kenchris.
-
Handle loss of full activity, as well as running in workers w3c/screen-wake-lock#161, by @kenchris.
-
Require user activation w3c/screen-wake-lock#160, by @kenchris.
-
Integrate optional permission prompting w3c/screen-wake-lock#158, by @kenchris.
-
Expose to dedicated workers w3c/screen-wake-lock#157, by @kenchris.
-
Make WakeLock constructable w3c/screen-wake-lock#155, by @kenchris.
-
Handle document visibility w3c/screen-wake-lock#153, by @kenchris.
-
Add info on when the UA may release a lock w3c/screen-wake-lock#152, by @kenchris.
-
-
11 pull requests merged.
-
Fix Marcos' comments w3c/screen-wake-lock#166.
-
Modernize Respec usage w3c/screen-wake-lock#165.
-
Attempt to improve the permission flow/steps w3c/screen-wake-lock#164.
-
Fix #162 - missing rejection steps w3c/screen-wake-lock#163.
-
Handle loss of full activity, as well as running in workers w3c/screen-wake-lock#161.
-
Require user activation w3c/screen-wake-lock#160.
-
Integrate optional permission prompting w3c/screen-wake-lock#158.
-
Expose to dedicated workers w3c/screen-wake-lock#157.
-
Make WakeLock constructable w3c/screen-wake-lock#155.
-
Handle document visibility w3c/screen-wake-lock#153.
-
Add info on when the UA may release a lock w3c/screen-wake-lock#152.
-
-
1 pull request closed.
-
Restrict status reporting for wake lock w3c/screen-wake-lock#125.
-
-
9 pull requests received 68 new comments.
-
Attempt to improve the permission flow/steps w3c/screen-wake-lock#164 (24 comments by @kenchris, @marcoscaceres, @rakuco, @reillyeon)
-
Modernize Respec usage w3c/screen-wake-lock#165 (16 comments by @anssiko, @kenchris, @marcoscaceres)
-
Integrate optional permission prompting w3c/screen-wake-lock#158 (13 comments by @jyasskin, @kenchris, @reillyeon)
-
Add static requestPermission method on Window w3c/screen-wake-lock#167 (7 comments by @kenchris, @reillyeon)
-
Handle loss of full activity, as well as running in workers w3c/screen-wake-lock#161 (1 comment by @reillyeon)
-
Rewrite of most of the algorithms to be much more formal and simple w3c/screen-wake-lock#150 (1 comment by @Honry)
-
w3c/deviceorientation
-
1 issue opened.
-
Add integration with the Permissions API w3c/deviceorientation#70, by @reillyeon.
-
-
3 issues closed.
-
Security and privacy section must be normative w3c/deviceorientation#46.
-
Should the API be exposed only to secure context? w3c/deviceorientation#47.
-
Add API for requesting permission to receive device motion / orientation events w3c/deviceorientation#57.
-
-
3 issues received 18 new comments.
-
Add API for requesting permission to receive device motion / orientation events w3c/deviceorientation#57 (16 comments by @anssiko, @cdumez, @machenmusik, @maryammjd, @nbutko, @neave, @reillyeon)
-
-
3 pull requests opened.
-
Note limited implementation experience w3c/deviceorientation#71, by @anssiko.
-
Add permission request API w3c/deviceorientation#68, by @cdumez.
-
-
2 pull requests merged.
-
Fix typo w3c/deviceorientation#69.
-
Add permission request API w3c/deviceorientation#68.
-
-
2 pull requests received 20 new comments.
-
Add permission request API w3c/deviceorientation#68 (19 comments by @annevk, @anssiko, @cdumez, @domenic, @kenchris, @reillyeon, @wseltzer)
-
w3c/html-media-capture
-
1 issue received 1 new comment.
w3c/sensors
-
1 issue opened.
-
Add API for requesting permission w3c/sensors#388, by @anssiko.
-
-
2 issues received 3 new comments.
-
3 pull requests opened.
-
Expose to dedicated workers w3c/sensors#389, by @anssiko.
-
Fix some links w3c/sensors#387, by @xfq.
-
3 pull requests merged.
-
Fix typo w3c/sensors#390.
-
Expose to dedicated workers w3c/sensors#389.
-
Fix some links w3c/sensors#387.
-
-
2 pull requests received 3 new comments.
w3c/orientation-sensor
-
1 issue opened.
-
TypeError is not a DOMException w3c/orientation-sensor#63, by @kenchris.
-
-
1 issue closed.
-
TypeError is not a DOMException w3c/orientation-sensor#63.
-
-
1 pull request opened.
-
Stop calling TypeError a DOMException w3c/orientation-sensor#64, by @rakuco.
-
-
1 pull request merged.
-
Stop calling TypeError a DOMException w3c/orientation-sensor#64.
-
-
1 pull request received 1 new comment.
w3c/contact-picker
-
1 issue opened.
-
Provide access to address properties w3c/contact-picker#12, by @petele.
-
-
2 issues received 5 new comments.
-
interface ContactInfo: metadata distinguishing email/tel instances? w3c/contact-picker#4 (4 comments by @annevk, @tomayac)
-
Add phonetic name as one of `ContactAddress` properties w3c/contact-picker#70 (1 comment by @marcoscaceres)
-
w3c/magnetometer
-
1 pull request opened.
-
Fix a broken link w3c/magnetometer#52, by @xfq.
-
-
1 pull request merged.
-
Fix a broken link w3c/magnetometer#52.
-
-
1 pull request received 1 new comment.
GitHub
w3c/screen-wake-lock
-
1 issue opened.
-
WakeLockRequest should probably have an associatedLock property w3c/screen-wake-lock#147, by @kenchris.
-
-
3 issues closed.
-
Consider using the platform's standard cancelation primitive, AbortSignal w3c/screen-wake-lock#142.
-
WakeLockRequest should probably have an associatedLock property w3c/screen-wake-lock#147.
-
Duplicate (?) normative requirements w3c/screen-wake-lock#143.
-
-
1 issue received 1 new comment.
-
6 pull requests opened.
-
Rewrite of most of the algorithms to be much more formal and simple w3c/screen-wake-lock#150, by @kenchris.
-
Use internal slots instead of prose w3c/screen-wake-lock#149, by @kenchris.
-
Rewrite getWakeLock() algorithm w3c/screen-wake-lock#148, by @kenchris.
-
Modernize the examples w3c/screen-wake-lock#146, by @kenchris.
-
Update editors w3c/screen-wake-lock#145, by @anssiko.
-
Remove duplicate normative statements w3c/screen-wake-lock#144, by @anssiko.
-
-
6 pull requests merged.
-
Rewrite of most of the algorithms to be much more formal and simple w3c/screen-wake-lock#150.
-
Use internal slots instead of prose w3c/screen-wake-lock#149.
-
Rewrite getWakeLock() algorithm w3c/screen-wake-lock#148.
-
Modernize the examples w3c/screen-wake-lock#146.
-
Update editors w3c/screen-wake-lock#145.
-
Remove duplicate normative statements w3c/screen-wake-lock#144.
-
-
6 pull requests received 32 new comments.
-
Rewrite of most of the algorithms to be much more formal and simple w3c/screen-wake-lock#150 (21 comments by @anssiko, @kenchris, @reillyeon)
-
w3c/ambient-light
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Update Previous Version metadata w3c/ambient-light#57, by @anssiko.
-
-
1 pull request merged.
-
Update Previous Version metadata w3c/ambient-light#57.
-
w3c/deviceorientation
-
2 issues opened.
-
Set up automatic Bikeshed compilation w3c/deviceorientation#67, by @reillyeon.
-
Add integration with Permissions Policy w3c/deviceorientation#64, by @reillyeon.
-
-
1 issue closed.
-
Remove [NoInterfaceObject] w3c/deviceorientation#58.
-
-
5 issues received 53 new comments.
-
Add API for requesting permission to receive device motion / orientation events w3c/deviceorientation#57 (46 comments by @19h, @anssiko, @cdumez, @erikmchut, @geoffreygaren, @griffin2000, @grorg, @lknik, @machenmusik, @neave, @nuthinking, @othermaciej, @reillyeon, @richtr, @samuelweiler, @tangobravo, @TimvanScherpenzeel, @tobie, @tparisi, @zchrykng)
-
Reach consensus on deprecation and removal of de facto standard init*Event() methods w3c/deviceorientation#35 (2 comments by @reillyeon, @smaug----)
-
-
2 pull requests opened.
-
Update index.html to 0dc1aba. w3c/deviceorientation#66, by @engedy.
-
Restrict all interfaces to secure contexts w3c/deviceorientation#65, by @engedy.
-
-
3 pull requests merged.
-
Update index.html to 0dc1aba. w3c/deviceorientation#66.
-
Restrict all interfaces to secure contexts w3c/deviceorientation#65.
-
Remove [NoInterfaceObject] w3c/deviceorientation#63.
-
-
3 pull requests received 10 new comments.
-
Restrict all interfaces to secure contexts w3c/deviceorientation#65 (6 comments by @engedy, @reillyeon)
-
w3c/contact-picker
-
1 issue opened.
-
Add phonetic name as one of `ContactAddress` properties w3c/contact-picker#70, by @agektmr.
-
-
1 issue received 5 new comments.
-
Add phonetic name as one of `ContactAddress` properties w3c/contact-picker#70 (5 comments by @agektmr, @marcoscaceres, @rsolomakhin)
-
w3c/proximity
-
1 pull request opened.
-
Update Previous Version metadata w3c/proximity#38, by @anssiko.
-
-
1 pull request merged.
-
Update Previous Version metadata w3c/proximity#38.
-
w3c/orientation-sensor
-
1 pull request opened.
-
Update Previous Version metadata w3c/orientation-sensor#62, by @anssiko.
-
-
1 pull request merged.
-
Update Previous Version metadata w3c/orientation-sensor#62.
-
w3c/magnetometer
-
1 pull request opened.
-
Update Previous Version metadata w3c/magnetometer#51, by @anssiko.
-
-
1 pull request merged.
-
Update Previous Version metadata w3c/magnetometer#51.
-
w3c/gyroscope
-
1 pull request opened.
-
Update Previous Version metadata w3c/gyroscope#42, by @anssiko.
-
-
1 pull request merged.
-
Update Previous Version metadata w3c/gyroscope#42.
-
w3c/accelerometer
-
1 pull request opened.
-
Update Previous Version metadata w3c/accelerometer#51, by @anssiko.
-
-
1 pull request merged.
-
Update Previous Version metadata w3c/accelerometer#51.
-
w3c/sensors
-
2 issues opened.
-
Non-normative Extensibility section uses normative language w3c/sensors#383, by @anssiko.
-
Define the default allowlist normatively w3c/sensors#382, by @anssiko.
-
-
1 issue closed.
-
Non-normative Extensibility section uses normative language w3c/sensors#383.
-
-
2 issues received 2 new comments.
-
3 pull requests opened.
-
Update Previous Version metadata w3c/sensors#386, by @anssiko.
-
Remove standalone spec of WebDriver Extension API w3c/sensors#385, by @Honry.
-
Clarify normative term usage in the Extensibility section w3c/sensors#384, by @anssiko.
-
-
3 pull requests merged.
-
Update Previous Version metadata w3c/sensors#386.
-
Remove standalone spec of WebDriver Extension API w3c/sensors#385.
-
Clarify normative term usage in the Extensibility section w3c/sensors#384.
-
-
1 pull request received 1 new comment.
w3c/geolocation
-
3 issues opened.
-
Restrict interfaces to secure contexts? w3c/geolocation#25, by @foolip.
-
Callbacks functions don't have a handleEvent operation w3c/geolocation#24, by @foolip.
-
Remove inline issues w3c/geolocation#21, by @anssiko.
-
-
2 issues closed.
-
Remove inline issues w3c/geolocation#21.
-
Remove [NoInterfaceObject] w3c/geolocation#19.
-
-
2 issues received 3 new comments.
-
3 pull requests opened.
-
Rename NavigatorGeolocation* interfaces to Geolocation* w3c/geolocation#23, by @foolip.
-
Drop inline issues w3c/geolocation#22, by @anssiko.
-
Remove [NoInterfaceObject] w3c/geolocation#20, by @anssiko.
-
-
3 pull requests merged.
-
Rename NavigatorGeolocation* interfaces to Geolocation* w3c/geolocation#23.
-
Drop inline issues w3c/geolocation#22.
-
Remove [NoInterfaceObject] w3c/geolocation#20.
-
-
3 pull requests received 25 new comments.
-
Rename NavigatorGeolocation* interfaces to Geolocation* w3c/geolocation#23 (12 comments by @annevk, @anssiko, @foolip, @inexorabletash, @reillyeon)
-
w3c/das-charter
-
1 issue closed.
-
Maintain the Geolocation API Specification w3c/das-charter#76.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Geolocation api w3c/das-charter#77, by @plehegar.
-
-
1 pull request merged.
-
Geolocation api w3c/das-charter#77.
-
-
1 pull request received 6 new comments.
Participants
-
1 organization left.
-
Qualcomm Innovation Center, Inc left.
-
GitHub
w3c/deviceorientation
-
3 issues opened.
-
What is difference with Gyroscope API ? w3c/deviceorientation#61, by @GrosSacASac.
-
Add non-normative text describing the current deviceorientationabsolute implementation status w3c/deviceorientation#60, by @anssiko.
-
Remove [NoInterfaceObject] w3c/deviceorientation#58, by @annevk.
-
-
4 issues closed.
-
Reach consensus on deprecation and removal of de facto standard init*Event() methods w3c/deviceorientation#35.
-
devicemotion: rotationRate is not implemented according to specification w3c/deviceorientation#44.
-
[editorial] Convert the spec source to Bikeshed/ReSpec w3c/deviceorientation#53.
-
What is difference with Gyroscope API ? w3c/deviceorientation#61.
-
-
6 issues received 35 new comments.
-
Add API for requesting permission to receive device motion / orientation events w3c/deviceorientation#57 (22 comments by @andrewmd5, @annevk, @anssiko, @cdumez, @eligrey, @griffin2000, @larsgk, @othermaciej, @reillyeon, @richtr, @rigel-prime, @TimvanScherpenzeel, @zchrykng)
-
[editorial] Convert the spec source to Bikeshed/ReSpec w3c/deviceorientation#53 (4 comments by @anssiko, @mkruisselbrink)
-
Reach consensus on deprecation and removal of de facto standard init*Event() methods w3c/deviceorientation#35 (1 comment by @reillyeon)
-
devicemotion: rotationRate is not implemented according to specification w3c/deviceorientation#44 (1 comment by @reillyeon)
-
-
3 pull requests opened.
-
Remove [NoInterfaceObject] w3c/deviceorientation#63, by @anssiko.
-
Convert spec source into Bikeshed format w3c/deviceorientation#62, by @anssiko.
-
Make security and privacy normative w3c/deviceorientation#59, by @anssiko.
-
-
4 pull requests merged.
-
Convert spec source into Bikeshed format w3c/deviceorientation#62.
-
update rotationRate alpha, beta, gamma description to be the same as implementation w3c/deviceorientation#43.
-
Make security and privacy normative w3c/deviceorientation#59.
-
Add the ondeviceorientationabsolute event handler attribute w3c/deviceorientation#34.
-
-
1 pull request closed.
-
Make security and privacy normative w3c/deviceorientation#49.
-
-
5 pull requests received 19 new comments.
-
Convert spec source into Bikeshed format w3c/deviceorientation#62 (11 comments by @anssiko, @reillyeon)
-
update rotationRate alpha, beta, gamma description to be the same as implementation w3c/deviceorientation#43 (4 comments by @anssiko, @juncaidf)
-
Add the ondeviceorientationabsolute event handler attribute w3c/deviceorientation#34 (2 comments by @anssiko)
-
w3c/sensors
-
1 issue opened.
-
Upstream mock sensor types to corresponding concrete sensor specs w3c/sensors#378, by @Honry.
-
-
1 issue closed.
-
Upstream mock sensor types to corresponding concrete sensor specs w3c/sensors#378.
-
-
1 issue received 5 new comments.
-
Upstream mock sensor types to corresponding concrete sensor specs w3c/sensors#378 (5 comments by @anssiko, @Honry)
-
-
4 pull requests opened.
-
Address how to extend mock sensor type w3c/sensors#381, by @Honry.
-
Remove concrete MockSensorReadingValues dictionary w3c/sensors#380, by @Honry.
-
Export MockSensorType enum w3c/sensors#379, by @Honry.
-
Integrated WebDriver Extension API into to Generic Sensor spec w3c/sensors#377, by @Honry.
-
-
4 pull requests merged.
-
Address how to extend mock sensor type w3c/sensors#381.
-
Remove concrete MockSensorReadingValues dictionary w3c/sensors#380.
-
Export MockSensorType enum w3c/sensors#379.
-
Integrated WebDriver Extension API into to Generic Sensor spec w3c/sensors#377.
-
-
4 pull requests received 11 new comments.
-
Integrated WebDriver Extension API into to Generic Sensor spec w3c/sensors#377 (5 comments by @anssiko, @Honry, @reillyeon)
-
w3c/proximity
-
2 pull requests opened.
-
Rebuild to update the anchor data w3c/proximity#37, by @Honry.
-
Integration of mock sensor type w3c/proximity#36, by @Honry.
-
-
2 pull requests merged.
-
Rebuild to update the anchor data w3c/proximity#37.
-
Integration of mock sensor type w3c/proximity#36.
-
w3c/orientation-sensor
-
2 pull requests opened.
-
Rebuild to update the anchor data w3c/orientation-sensor#61, by @Honry.
-
Integration of mock sensor type w3c/orientation-sensor#60, by @Honry.
-
-
2 pull requests merged.
-
Rebuild to update the anchor data w3c/orientation-sensor#61.
-
Integration of mock sensor type w3c/orientation-sensor#60.
-
w3c/magnetometer
-
2 pull requests opened.
-
Rebuild to update the anchor data w3c/magnetometer#50, by @Honry.
-
Integration of mock sensor type w3c/magnetometer#49, by @Honry.
-
-
2 pull requests merged.
-
Rebuild to update the anchor data w3c/magnetometer#50.
-
Integration of mock sensor type w3c/magnetometer#49.
-
w3c/gyroscope
-
2 pull requests opened.
-
Rebuild to update the anchor data w3c/gyroscope#41, by @Honry.
-
Integration of mock sensor type w3c/gyroscope#40, by @Honry.
-
-
2 pull requests merged.
-
Rebuild to update the anchor data w3c/gyroscope#41.
-
Integration of mock sensor type w3c/gyroscope#40.
-
w3c/accelerometer
-
2 pull requests opened.
-
Rebuild to update the anchor data w3c/accelerometer#50, by @Honry.
-
Integration of mock sensor type w3c/accelerometer#49, by @Honry.
-
-
2 pull requests merged.
-
Rebuild to update the anchor data w3c/accelerometer#50.
-
Integration of mock sensor type w3c/accelerometer#49.
-
w3c/ambient-light
-
1 issue received 3 new comments.
-
Ambient Light Sensors to detect RGB colors w3c/ambient-light#9 (3 comments by @AdaRoseCannon, @anssiko)
-
-
3 pull requests opened.
-
Rebuild to update the anchor data w3c/ambient-light#56, by @Honry.
-
Integration of mock sensor type w3c/ambient-light#54, by @Honry.
-
-
3 pull requests merged.
-
Rebuild to update the anchor data w3c/ambient-light#56.
-
Fix typo w3c/ambient-light#55.
-
Integration of mock sensor type w3c/ambient-light#54.
-
-
1 pull request received 7 new comments.
w3c/geolocation
-
1 issue opened.
-
Remove [NoInterfaceObject] w3c/geolocation#19, by @annevk.
-
-
1 issue received 11 new comments.
-
Remove [NoInterfaceObject] w3c/geolocation#19 (11 comments by @annevk, @anssiko, @kenchris, @reillyeon, @xfq)
-
w3c/das-charter
-
1 issue opened.
-
Maintain the Geolocation API Specification w3c/das-charter#76, by @xfq.
-
-
1 issue received 6 new comments.
w3c/contact-picker
-
2 issues opened.
-
Consider Web Intents w3c/contact-picker#11, by @darobin.
-
Input validation w3c/contact-picker#10, by @finnurbreki.
-
-
2 issues closed.
-
Input validation w3c/contact-picker#10.
-
ContactInfo can be a dictionary w3c/contact-picker#8.
-
-
1 issue reopened.
-
ContactAddress 'region' inconsistencies w3c/contact-picker#65, by @marcoscaceres.
-
-
5 issues received 8 new comments.
-
Consider contact API that does not reveal contact info to the website w3c/contact-picker#7 (4 comments by @beverloo, @Gozala)
-
Consider dictionaries and sequences instead of non-constructible interfaces and frozen arrays w3c/contact-picker#5 (1 comment by @beverloo)
-