Devices and Sensors Working Group - Activity in 2020
No matches.
Lifecycle
-
1 charter started.
-
Chartered until 30 November 2022. Participants had to rejoin under this charter.
-
TR publications
-
1 document published.
-
The Screen Fold API published as a First Public Working Draft. History of The Screen Fold API
-
Participants
-
1 participant joined.
-
Jorge Coronel (Google LLC) joined.
-
-
5 organizations joined.
-
CoSMo Software Consulting Pte Ltd joined.
-
Fraunhofer Gesellschaft joined.
-
Google LLC joined.
-
Ecole Mohammadia d'Ingenieurs Rabat (EMI) joined.
-
Intel Corporation joined.
-
-
9 organizations left.
-
Fiserv left.
-
Samsung Electronics Co., Ltd. left.
-
Bocoup left.
-
Mitsubishi Electric Corporation left.
-
Fraunhofer Gesellschaft left.
-
CoSMo Software Consulting Pte Ltd left.
-
Google LLC left.
-
Ecole Mohammadia d'Ingenieurs Rabat (EMI) left.
-
Intel Corporation left.
-
GitHub
w3c/vibration
-
1 issue opened.
w3c/device-posture
-
4 issues opened.
-
Broken link w3c/device-posture#51, by @xfq.
-
Improve fingerprinting of screen fold changes w3c/device-posture#46, by @darktears.
-
Fold Angle fingerprinting concerns and its usefulness w3c/device-posture#45, by @darktears.
-
What should be @media and {not} (screen-fold-posture) behavior. w3c/device-posture#44, by @darktears.
-
-
2 issues closed.
-
Broken link w3c/device-posture#51.
-
What should be @media and {not} (screen-fold-posture) behavior. w3c/device-posture#44.
-
-
3 issues received 7 new comments.
-
What should be @media and {not} (screen-fold-posture) behavior. w3c/device-posture#44 (4 comments by @darktears, @lilles)
-
Fold Angle fingerprinting concerns and its usefulness w3c/device-posture#45 (1 comment by @darktears)
-
-
6 pull requests opened.
-
update affiliation for Diego w3c/device-posture#52, by @diekus.
-
Validation fixes w3c/device-posture#50, by @xfq.
-
ReSpec fix w3c/device-posture#49, by @xfq.
-
Fix typo in the Security and Privacy section. w3c/device-posture#48, by @darktears.
-
Add an example to feature detect the fold posture media feature. w3c/device-posture#47, by @darktears.
-
Upgrade spec status to ED w3c/device-posture#43, by @anssiko.
-
-
6 pull requests merged.
-
Validation fixes w3c/device-posture#50.
-
ReSpec fix w3c/device-posture#49.
-
Add an example to feature detect the fold posture media feature. w3c/device-posture#47.
-
Fix typo in the Security and Privacy section. w3c/device-posture#48.
-
Improve the Privacy and Security section. w3c/device-posture#42.
-
Upgrade spec status to ED w3c/device-posture#43.
-
-
1 pull request reopened.
-
Add an example to feature detect the fold posture media feature. w3c/device-posture#47, by @kenchris.
-
-
6 pull requests received 10 new comments.
-
Add an example to feature detect the fold posture media feature. w3c/device-posture#47 (2 comments by @darktears, @kenchris)
-
Improve the Privacy and Security section. w3c/device-posture#42 (2 comments by @anssiko, @darktears)
w3c/das-wg
-
2 pull requests opened.
-
Add Screen Fold API FPWD w3c/das-wg#36, by @anssiko.
-
Update to Charter 2020 w3c/das-wg#35, by @anssiko.
-
-
2 pull requests merged.
-
Add Screen Fold API FPWD w3c/das-wg#36.
-
Update to Charter 2020 w3c/das-wg#35.
-
-
1 pull request received 1 new comment.
w3c/das-charter
-
8 issues closed.
-
DASWG: Drop Generic Sensor API w3c/das-charter#106.
-
DASWG: Drop Orientation Sensor in favor of existing APIs w3c/das-charter#104.
-
DASWG: Drop Geolocation Sensor in favor of existing APIs w3c/das-charter#103.
-
DASWG: Leave Fold Angle in WICG for now and collaborate with CSS w3c/das-charter#102.
-
DASWG: Leave System WakeLock API in WICG until there is a second implementer w3c/das-charter#101.
-
DASWG: Drop Ambient light sensor API for privacy and lack of implementer support w3c/das-charter#100.
-
DASWG: Drop Proximity sensor API for privacy and lack of implementer support w3c/das-charter#99.
-
DASWG: Drop Battery API for privacy and lack of implementer support w3c/das-charter#98.
-
-
9 issues received 16 new comments.
-
DASWG: Drop Geolocation Sensor in favor of existing APIs w3c/das-charter#103 (8 comments by @annevk, @anssiko, @plehegar, @xfq)
-
DASWG: Drop Network Information API because it is harmful to the web w3c/das-charter#105 (1 comment by @xfq)
-
DASWG: Leave Fold Angle in WICG for now and collaborate with CSS w3c/das-charter#102 (1 comment by @xfq)
-
DASWG: Leave System WakeLock API in WICG until there is a second implementer w3c/das-charter#101 (1 comment by @xfq)
-
DASWG: Drop Ambient light sensor API for privacy and lack of implementer support w3c/das-charter#100 (1 comment by @xfq)
-
DASWG: Drop Proximity sensor API for privacy and lack of implementer support w3c/das-charter#99 (1 comment by @xfq)
-
DASWG: Drop Battery API for privacy and lack of implementer support w3c/das-charter#98 (1 comment by @xfq)
-
w3c/geolocation
-
1 issue received 5 new comments.
-
errorCallback parameter to getPosition() and watchPosition() is nullable in all major browser engines w3c/geolocation#61 (5 comments by @anssiko, @bzbarsky, @reillyeon)
-
w3c/screen-wake-lock
-
1 issue received 2 new comments.
w3c/ambient-light
-
1 issue received 7 new comments.
-
Request for Ambient Light Sensor web developer feedback w3c/ambient-light#64 (7 comments by @anssiko, @tomayac, @willmorgan)
-
w3c/battery
-
3 issues opened.
-
private browsing mode: upgrade recommendation w3c/battery#29, by @samuelweiler.
-
add more discussion of sec and priv analysis; split sections w3c/battery#28, by @samuelweiler.
-
make privacy mitigations normative w3c/battery#27, by @samuelweiler.
-
w3c/gyroscope
-
1 issue opened.
-
define normative privacy mitigation(s) w3c/gyroscope#45, by @samuelweiler.
-
w3c/accelerometer
-
1 issue opened.
-
define normative privacy mitigation w3c/accelerometer#57, by @samuelweiler.
-
w3c/deviceorientation
-
1 pull request opened.
-
Add a note explaining how the coordinate system differs from the CSS one. w3c/deviceorientation#92, by @rakuco.
-
-
1 pull request merged.
-
Add a note explaining how the coordinate system differs from the CSS one. w3c/deviceorientation#92.
-
-
1 pull request received 3 new comments.
-
Add a note explaining how the coordinate system differs from the CSS one. w3c/deviceorientation#92 (3 comments by @anssiko, @rakuco)
-
Lifecycle
-
1 charter extension.
-
Charter extended until 30 November 2020.
-
Participants
-
1 organization left.
-
Mozilla Foundation left.
-
GitHub
w3c/geolocation
-
1 issue opened.
-
1 issue received 4 new comments.
-
errorCallback parameter to getPosition() and watchPosition() is nullable in all major browser engines w3c/geolocation#61 (4 comments by @anssiko, @bzbarsky, @reillyeon)
-
w3c/device-posture
-
2 pull requests opened.
-
Improve the Privacy and Security section. w3c/device-posture#42, by @darktears.
-
Update CSS to improve doc readability w3c/device-posture#41, by @anssiko.
-
-
1 pull request merged.
-
Update CSS to improve doc readability w3c/device-posture#41.
-
-
1 pull request received 7 new comments.
-
Improve the Privacy and Security section. w3c/device-posture#42 (7 comments by @anssiko, @darktears, @kenchris)
-
w3c/das-charter
-
3 pull requests opened.
-
Add a Tentative Deliverables section w3c/das-charter#109, by @xfq.
-
Use new patent policy in the charter w3c/das-charter#108, by @xfq.
-
Add CSSWG to the Coordination section w3c/das-charter#107, by @xfq.
-
-
3 pull requests merged.
-
Add a Tentative Deliverables section w3c/das-charter#109.
-
Use new patent policy in the charter w3c/das-charter#108.
-
Add CSSWG to the Coordination section w3c/das-charter#107.
-
-
2 pull requests received 8 new comments.
-
Add a Tentative Deliverables section w3c/das-charter#109 (7 comments by @anssiko, @plehegar, @reillyeon)
-
w3c/deviceorientation
-
2 issues opened.
-
DeviceMotionEvent atttributes can't be null per current IDL w3c/deviceorientation#91, by @saschanaz.
-
Convert DeviceMotionEventAcceleration/RotationRate to dictionaries w3c/deviceorientation#89, by @saschanaz.
-
-
1 issue closed.
-
Convert DeviceMotionEventAcceleration/RotationRate to dictionaries w3c/deviceorientation#89.
-
-
2 issues received 4 new comments.
-
DeviceMotionEvent atttributes can't be null per current IDL w3c/deviceorientation#91 (3 comments by @bzbarsky, @saschanaz)
-
Convert DeviceMotionEventAcceleration/RotationRate to dictionaries w3c/deviceorientation#89 (1 comment by @saschanaz)
-
-
1 pull request opened.
-
Convert Acceleration/RotationRate interfaces to dictionaries w3c/deviceorientation#90, by @saschanaz.
-
-
1 pull request closed.
-
Convert Acceleration/RotationRate interfaces to dictionaries w3c/deviceorientation#90.
-
-
1 pull request reopened.
-
Convert Acceleration/RotationRate interfaces to dictionaries w3c/deviceorientation#90, by @saschanaz.
-
-
2 pull requests received 5 new comments.
-
Convert Acceleration/RotationRate interfaces to dictionaries w3c/deviceorientation#90 (4 comments by @anssiko, @mkruisselbrink, @saschanaz)
-
w3c/proximity
-
1 issue opened.
-
Add an explicit use cases and requirements section w3c/proximity#43, by @xfq.
-
Participants
-
1 participant joined.
-
Marcos Caceres (W3C) joined.
-
-
1 participant left.
-
Diego Gonzalez-Zuniga (Microsoft Corporation) left.
-
GitHub
w3c/sensors
-
1 pull request opened.
-
Rename Feature Policy to Permissions Policy w3c/sensors#407, by @clelland.
-
-
1 pull request merged.
-
Rename Feature Policy to Permissions Policy w3c/sensors#407.
-
-
1 pull request received 1 new comment.
w3c/das-wg
-
1 issue received 14 new comments.
-
Devices and Sensors WG - TPAC 2020 agenda w3c/das-wg#31 (14 comments by @anssiko, @cynthia, @lknik, @marcoscaceres, @nondebug, @roderickc, @toreini, @xfq)
-
-
1 pull request opened.
-
Improve font readability w3c/das-wg#34, by @anssiko.
-
-
1 pull request merged.
-
Improve font readability w3c/das-wg#34.
-
-
1 pull request received 1 new comment.
w3c/ambient-light
-
2 issues opened.
-
Request for Ambient Light Sensor web developer feedback w3c/ambient-light#64, by @anssiko.
-
Consider making granularity of the data normative w3c/ambient-light#63, by @cynthia.
-
-
1 issue received 1 new comment.
-
Request for Ambient Light Sensor web developer feedback w3c/ambient-light#64 (1 comment by @tomayac)
-
w3c/system-wake-lock
-
2 issues opened.
-
System Wake Lock explainer w3c/system-wake-lock#6, by @anssiko.
-
Use case: in-browser training w3c/system-wake-lock#5, by @anssiko.
-
w3c/das-charter
-
1 issue received 1 new comment.
-
DASWG: Drop Network Information API because it is harmful to the web w3c/das-charter#105 (1 comment by @xfq)
-
w3c/proximity
-
1 issue closed.
-
Published spec out of date w3c/proximity#41.
-
-
1 issue received 1 new comment.
w3c/device-posture
-
2 pull requests opened.
-
Fix custom styles w3c/device-posture#40, by @anssiko.
-
Update configuration, fix ReSpec errors and warnings w3c/device-posture#39, by @anssiko.
-
-
2 pull requests merged.
-
Fix custom styles w3c/device-posture#40.
-
Update configuration, fix ReSpec errors and warnings w3c/device-posture#39.
-
w3c/contact-picker
-
1 issue opened.
-
Matching ContactAddress fields to autofill attributes w3c/contact-picker#71, by @jcayzac.
-
-
1 issue received 6 new comments.
-
Matching ContactAddress fields to autofill attributes w3c/contact-picker#71 (6 comments by @ianbjacobs, @jcayzac, @mnoorenberghe, @rsolomakhin)
-
w3c/screen-wake-lock
-
1 pull request merged.
-
Make "type" an optional parameter for WakeLock.request(). w3c/screen-wake-lock#291.
-
-
1 pull request received 2 new comments.
-
Make "type" an optional parameter for WakeLock.request(). w3c/screen-wake-lock#291 (2 comments by @marcoscaceres, @rakuco)
-
w3c/battery
-
1 issue received 1 new comment.
w3c/orientation-sensor
-
1 issue opened.
-
Head orientation tracking w3c/orientation-sensor#68, by @anssiko.
-
TR publications
-
1 document published.
-
Screen Wake Lock API published as a Working Draft. History of Screen Wake Lock API
-
Participants
-
2 participants joined.
-
Laura Morinigo (Samsung Electronics Co., Ltd.) joined.
-
Peter Burrows (Fiserv) joined.
-
-
1 organization joined.
-
Fiserv joined.
-
GitHub
w3c/screen-wake-lock
-
2 issues opened.
-
Add explainer to the spec repo w3c/screen-wake-lock#284, by @rakuco.
-
Recommend some UI indicator for when wake lock is active w3c/screen-wake-lock#282, by @David-Chadwick.
-
-
5 issues closed.
-
New shortname w3c/screen-wake-lock#257.
-
Do not use allow="screen-wake-lock" for iframes w3c/screen-wake-lock#277.
-
Add explainer to the spec repo w3c/screen-wake-lock#284.
-
Hide failure to acquire a screen wake lock w3c/screen-wake-lock#247.
-
[meta] web-platform-tests w3c/screen-wake-lock#111.
-
-
6 issues received 19 new comments.
-
User prompts to show an active screen-lock should have an associated domain w3c/screen-wake-lock#278 (6 comments by @jumde, @marcoscaceres, @rakuco, @reillyeon)
-
Recommend some UI indicator for when wake lock is active w3c/screen-wake-lock#282 (3 comments by @kenchris, @reillyeon, @tomayac)
-
10 pull requests opened.
-
explainer: Link to issues where System Wake Locks were discussed. w3c/screen-wake-lock#292, by @rakuco.
-
Make "type" an optional parameter for WakeLock.request(). w3c/screen-wake-lock#291, by @rakuco.
-
Update the Changes section w3c/screen-wake-lock#290, by @xfq.
-
chore: add lang="en" w3c/screen-wake-lock#289, by @xfq.
-
explainer: Expand on why WakeLock.request() still requires an argument. w3c/screen-wake-lock#288, by @rakuco.
-
editorial: Reword the Security and Privacy Considerations section. w3c/screen-wake-lock#287, by @rakuco.
-
Add an Explainer document to the repository. w3c/screen-wake-lock#286, by @rakuco.
-
Stop checking if "acquire the wake lock" succeeds. w3c/screen-wake-lock#285, by @rakuco.
-
Ensure the release operation is valid WebIDL w3c/screen-wake-lock#283, by @realityforge.
-
editorial: Link WakeLockSentinel.released to its corresponding test. w3c/screen-wake-lock#281, by @rakuco.
-
-
8 pull requests merged.
-
explainer: Link to issues where System Wake Locks were discussed. w3c/screen-wake-lock#292.
-
chore: add lang="en" w3c/screen-wake-lock#289.
-
Update the Changes section w3c/screen-wake-lock#290.
-
editorial: Reword the Security and Privacy Considerations section. w3c/screen-wake-lock#287.
-
Add an Explainer document to the repository. w3c/screen-wake-lock#286.
-
Stop checking if "acquire the wake lock" succeeds. w3c/screen-wake-lock#285.
-
editorial: Link WakeLockSentinel.released to its corresponding test. w3c/screen-wake-lock#281.
-
editorial: Add internal slots to WakeLockSentinel. w3c/screen-wake-lock#280.
-
-
2 pull requests closed.
-
explainer: Expand on why WakeLock.request() still requires an argument. w3c/screen-wake-lock#288.
-
Ensure the release operation is valid WebIDL w3c/screen-wake-lock#283.
-
-
7 pull requests received 63 new comments.
-
Add an Explainer document to the repository. w3c/screen-wake-lock#286 (46 comments by @anssiko, @kenchris, @larsgk, @marcoscaceres, @rakuco, @reillyeon, @tomayac)
-
explainer: Expand on why WakeLock.request() still requires an argument. w3c/screen-wake-lock#288 (7 comments by @domenic, @marcoscaceres, @rakuco, @reillyeon)
-
editorial: Reword the Security and Privacy Considerations section. w3c/screen-wake-lock#287 (3 comments by @marcoscaceres, @rakuco)
-
Stop checking if "acquire the wake lock" succeeds. w3c/screen-wake-lock#285 (3 comments by @rakuco, @reillyeon)
-
Ensure the release operation is valid WebIDL w3c/screen-wake-lock#283 (2 comments by @realityforge, @reillyeon)
-
w3c/das-wg
-
1 issue received 4 new comments.
-
Devices and Sensors WG - TPAC 2020 agenda w3c/das-wg#31 (4 comments by @anssiko, @marcoscaceres, @maryammjd, @toreini)
-
-
1 pull request opened.
-
Add Screen Wake Lock API WD w3c/das-wg#33, by @anssiko.
-
-
1 pull request merged.
-
Add Screen Wake Lock API WD w3c/das-wg#33.
-
w3c/system-wake-lock
-
1 issue opened.
-
Request for System Wake Lock use cases w3c/system-wake-lock#4, by @anssiko.
-
-
2 issues received 4 new comments.
-
Privacy consideration about tracking location w3c/system-wake-lock#3 (2 comments by @anssiko, @hadriann)
w3c/sensors
-
1 issue closed.
-
Pressure sensor support? w3c/sensors#370.
-
-
1 issue received 4 new comments.
w3c/geolocation
-
2 issues opened.
-
I can't find step 6? w3c/geolocation#60, by @Alastair-L.
-
Add explainer to the spec repo w3c/geolocation#59, by @xfq.
-
-
1 issue closed.
-
I can't find step 6? w3c/geolocation#60.
-
-
1 issue received 2 new comments.
w3c/device-posture
-
2 issues opened.
-
Support for single/multi-Screen folds, off-center folds, and multiple folds in a single Screen. w3c/device-posture#38, by @michaelwasserman.
-
Supporting asymmetric shaped displays w3c/device-posture#37, by @chris480.
-
-
1 issue received 4 new comments.
-
Support for single/multi-Screen folds, off-center folds, and multiple folds in a single Screen. w3c/device-posture#38 (4 comments by @kenchris)
-
w3c/battery
-
1 issue received 1 new comment.
Participants
-
1 participant left.
-
Marcos Caceres (W3C) left.
-
GitHub
w3c/screen-wake-lock
-
7 issues opened.
-
User prompts to show an active screen-lock should have an associated domain w3c/screen-wake-lock#278, by @jumde.
-
Do not use allow="screen-wake-lock" for iframes w3c/screen-wake-lock#277, by @jumde.
-
Be able to query if there are any screen wake-lock object active for the current page w3c/screen-wake-lock#273, by @PaulKinlan.
-
sentinel.released boolean w3c/screen-wake-lock#272, by @jakearchibald.
-
release() linking to wrong algorithm? w3c/screen-wake-lock#271, by @jakearchibald.
-
[meta] Wide review tracker w3c/screen-wake-lock#270, by @xfq.
-
Set up ReSpec autopublish w3c/screen-wake-lock#268, by @marcoscaceres.
-
-
5 issues closed.
-
sentinel.released boolean w3c/screen-wake-lock#272.
-
release() linking to wrong algorithm? w3c/screen-wake-lock#271.
-
Set up ReSpec autopublish w3c/screen-wake-lock#268.
-
Add "geolocation" wake lock w3c/screen-wake-lock#170.
-
Update the reference to Feature Policy w3c/screen-wake-lock#264.
-
-
9 issues received 23 new comments.
-
Be able to query if there are any screen wake-lock object active for the current page w3c/screen-wake-lock#273 (6 comments by @jakearchibald, @PaulKinlan, @reillyeon, @tomayac)
-
sentinel.released boolean w3c/screen-wake-lock#272 (5 comments by @jakearchibald, @marcoscaceres, @rakuco, @tomayac)
-
Add "geolocation" wake lock w3c/screen-wake-lock#170 (3 comments by @marcoscaceres, @rakuco, @tomayac)
-
User prompts to show an active screen-lock should have an associated domain w3c/screen-wake-lock#278 (2 comments by @reillyeon, @tomayac)
-
-
6 pull requests opened.
-
editorial: Add internal slots to WakeLockSentinel. w3c/screen-wake-lock#280, by @rakuco.
-
Add WakeLockSentinel.released. w3c/screen-wake-lock#279, by @rakuco.
-
Editorial: Align with Web IDL specification w3c/screen-wake-lock#276, by @autokagami.
-
Reference the "release a wake lock" algorithm in WakeLockSentinel.release() w3c/screen-wake-lock#275, by @rakuco.
-
Editorial: Run tidy on index.html. w3c/screen-wake-lock#274, by @rakuco.
-
Add a Changes section w3c/screen-wake-lock#269, by @xfq.
-
-
6 pull requests merged.
-
Add WakeLockSentinel.released. w3c/screen-wake-lock#279.
-
Editorial: Align with Web IDL specification w3c/screen-wake-lock#276.
-
Reference the "release a wake lock" algorithm in WakeLockSentinel.release() w3c/screen-wake-lock#275.
-
Editorial: Run tidy on index.html. w3c/screen-wake-lock#274.
-
Add a Changes section w3c/screen-wake-lock#269.
-
Editorial: s/Feature Policy/Permissions Policy w3c/screen-wake-lock#266.
-
-
4 pull requests received 21 new comments.
-
Add WakeLockSentinel.released. w3c/screen-wake-lock#279 (14 comments by @jakearchibald, @kenchris, @marcoscaceres, @rakuco)
-
Editorial: s/Feature Policy/Permissions Policy w3c/screen-wake-lock#266 (3 comments by @marcoscaceres, @rakuco)
-
w3c/das-charter
-
5 issues received 13 new comments.
-
DASWG: Drop Battery API for privacy and lack of implementer support w3c/das-charter#98 (6 comments by @lknik, @marcoscaceres, @reillyeon, @tomayac)
-
DASWG: Drop Ambient light sensor API for privacy and lack of implementer support w3c/das-charter#100 (3 comments by @Joe-Palmer, @samuelweiler)
-
DASWG: Drop Geolocation Sensor in favor of existing APIs w3c/das-charter#103 (2 comments by @annevk, @xfq)
-
DASWG: Leave System WakeLock API in WICG until there is a second implementer w3c/das-charter#101 (1 comment by @samuelweiler)
-
w3c/das-wg
-
1 issue opened.
-
Devices and Sensors WG - TPAC 2020 agenda w3c/das-wg#31, by @anssiko.
-
-
1 issue received 4 new comments.
-
Devices and Sensors WG - TPAC 2020 agenda w3c/das-wg#31 (4 comments by @anssiko, @lknik, @npdoty, @tomayac)
-
-
1 pull request opened.
-
Add Screen Fold API w3c/das-wg#32, by @anssiko.
-
-
1 pull request merged.
-
Add Screen Fold API w3c/das-wg#32.
-
w3c/system-wake-lock
-
1 issue received 7 new comments.
-
Privacy consideration about tracking location w3c/system-wake-lock#3 (7 comments by @EricMwobobia, @jyasskin, @samuelweiler, @xfq)
-
w3c/deviceorientation
-
1 issue received 17 new comments.
-
Move fingerprintable APIs behind permissions w3c/deviceorientation#85 (17 comments by @anssiko, @maryammjd, @pes10k, @reillyeon, @shartoo)
-
-
1 pull request received 3 new comments.
-
Drop duplicate PermissionState definition w3c/deviceorientation#88 (3 comments by @foolip, @rakuco, @reillyeon)
-
w3c/sensors
-
1 pull request opened.
-
Editorial: Align with Web IDL specification w3c/sensors#406, by @autokagami.
-
-
1 pull request merged.
-
Editorial: Align with Web IDL specification w3c/sensors#406.
-
w3c/orientation-sensor
-
1 pull request opened.
-
Editorial: Align with Web IDL specification w3c/orientation-sensor#67, by @autokagami.
-
-
1 pull request merged.
-
Editorial: Align with Web IDL specification w3c/orientation-sensor#67.
-
w3c/geolocation
-
5 issues opened.
-
Security review: General observations w3c/geolocation#57, by @magnus-git.
-
Section 6: Non-normative but containing implementation requirements? w3c/geolocation#56, by @magnus-git.
-
Section 4.5.6: Value for speed for stationary device w3c/geolocation#55, by @magnus-git.
-
Section 3: Why only "SHOULD" for protection of privacy? w3c/geolocation#54, by @magnus-git.
-
Section 1: Editorial - possible syntax error w3c/geolocation#53, by @magnus-git.
-
-
2 issues closed.
-
Section 4.5.6: Value for speed for stationary device w3c/geolocation#55.
-
Section 1: Editorial - possible syntax error w3c/geolocation#53.
-
-
9 issues received 14 new comments.
-
Section 3: Why only "SHOULD" for protection of privacy? w3c/geolocation#54 (2 comments by @reillyeon, @samuelweiler)
-
Section 6: Non-normative but containing implementation requirements? w3c/geolocation#56 (2 comments by @reillyeon, @samuelweiler)
-
Section 4.5.6: Value for speed for stationary device w3c/geolocation#55 (2 comments by @reillyeon, @samuelweiler)
-
Change text for description of GeolocationPositionError.message attribute w3c/geolocation#50 (2 comments by @chaals, @xfq)
-
How to specify desired accuracy / resolution of data? w3c/geolocation#49 (1 comment by @samuelweiler)
-
1 pull request opened.
-
Editorial: Align with Web IDL specification w3c/geolocation#58, by @autokagami.
-
-
1 pull request merged.
-
Editorial: Align with Web IDL specification w3c/geolocation#58.
-
-
1 pull request received 1 new comment.
w3c/device-posture
-
1 issue opened.
-
Move this repo into W3C space? w3c/device-posture#36, by @xfq.
-
-
1 issue closed.
-
Move this repo into W3C space? w3c/device-posture#36.
-
-
1 issue received 6 new comments.
w3c/contact-picker
-
2 issues received 5 new comments.
-
Add phonetic name as one of `ContactAddress` properties w3c/contact-picker#70 (4 comments by @agektmr, @eternalharvest, @xfq)
-
Add payerGivenName + payerFamilyName to PaymentAddress w3c/contact-picker#69 (1 comment by @eternalharvest)
-
Lifecycle
-
1 charter extension.
-
Charter extended until 31 October 2020.
-
GitHub
w3c/das-charter
-
9 issues opened.
-
DASWG: Drop Generic Sensor API w3c/das-charter#106, by @annevk.
-
DASWG: Drop Network Information API because it is harmful to the web w3c/das-charter#105, by @tantek.
-
DASWG: Drop Orientation Sensor in favor of existing APIs w3c/das-charter#104, by @tantek.
-
DASWG: Drop Geolocation Sensor in favor of existing APIs w3c/das-charter#103, by @tantek.
-
DASWG: Leave Fold Angle in WICG for now and collaborate with CSS w3c/das-charter#102, by @tantek.
-
DASWG: Leave System WakeLock API in WICG until there is a second implementer w3c/das-charter#101, by @tantek.
-
DASWG: Drop Ambient light sensor API for privacy and lack of implementer support w3c/das-charter#100, by @tantek.
-
DASWG: Drop Proximity sensor API for privacy and lack of implementer support w3c/das-charter#99, by @tantek.
-
DASWG: Drop Battery API for privacy and lack of implementer support w3c/das-charter#98, by @tantek.
-
-
9 issues received 39 new comments.
-
DASWG: Drop Battery API for privacy and lack of implementer support w3c/das-charter#98 (25 comments by @anssiko, @marcoscaceres, @pes10k, @reillyeon, @xfq)
-
DASWG: Drop Geolocation Sensor in favor of existing APIs w3c/das-charter#103 (4 comments by @annevk, @anssiko, @hober, @marcoscaceres)
-
DASWG: Leave Fold Angle in WICG for now and collaborate with CSS w3c/das-charter#102 (4 comments by @anssiko, @diekus-zz, @torgo, @xfq)
-
DASWG: Drop Proximity sensor API for privacy and lack of implementer support w3c/das-charter#99 (1 comment by @anssiko)
-
DASWG: Drop Ambient light sensor API for privacy and lack of implementer support w3c/das-charter#100 (1 comment by @anssiko)
-
DASWG: Leave System WakeLock API in WICG until there is a second implementer w3c/das-charter#101 (1 comment by @anssiko)
-
DASWG: Drop Orientation Sensor in favor of existing APIs w3c/das-charter#104 (1 comment by @anssiko)
-
DASWG: Drop Network Information API because it is harmful to the web w3c/das-charter#105 (1 comment by @anssiko)
-
w3c/geolocation
-
1 issue opened.
-
Change text for description of GeolocationPositionError.message attribute w3c/geolocation#50, by @himorin.
-
-
4 issues received 43 new comments.
-
Suggest permission lifetimes? w3c/geolocation#69 (15 comments by @cwilso, @IreneKnapp, @marcoscaceres, @maryammjd, @pes10k, @reillyeon, @yoavweiss)
-
Change text for description of GeolocationPositionError.message attribute w3c/geolocation#50 (14 comments by @marcoscaceres, @r12a, @reillyeon, @xfq)
-
How to specify desired accuracy / resolution of data? w3c/geolocation#49 (8 comments by @anssiko, @marcoscaceres, @pes10k, @samuelweiler)
-
Require user activation to use API w3c/geolocation#48 (6 comments by @engedy, @IreneKnapp, @kdzwinel, @marcoscaceres, @pes10k)
-
-
2 pull requests opened.
-
Editorial: s/feature policy/permissions policy w3c/geolocation#52, by @marcoscaceres.
-
Editorial: fix up .message text w3c/geolocation#51, by @marcoscaceres.
-
-
2 pull requests merged.
-
Add sections, markup fixes, nits w3c/geolocation#46.
-
Editorial: s/feature policy/permissions policy w3c/geolocation#52.
-
-
2 pull requests received 10 new comments.
w3c/screen-wake-lock
-
2 issues opened.
-
Update the reference to Feature Policy w3c/screen-wake-lock#264, by @xfq.
-
Publish a new Candidate Recommendation w3c/screen-wake-lock#262, by @jyasskin.
-
-
2 issues received 18 new comments.
-
Need maximum screen brightness mode w3c/screen-wake-lock#129 (15 comments by @CheloXL, @hadriann, @marcoscaceres, @reillyeon)
-
Publish a new Candidate Recommendation w3c/screen-wake-lock#262 (3 comments by @marcoscaceres, @reillyeon, @xfq)
-
-
4 pull requests opened.
-
Chore: put in bugzilla link w3c/screen-wake-lock#267, by @marcoscaceres.
-
Editorial: s/Feature Policy/Permissions Policy w3c/screen-wake-lock#266, by @marcoscaceres.
-
Use the `group` configuration option w3c/screen-wake-lock#265, by @xfq.
-
Chore: Mark Introduction as non-normative w3c/screen-wake-lock#263, by @xfq.
-
-
3 pull requests merged.
-
Chore: put in bugzilla link w3c/screen-wake-lock#267.
-
Use the `group` configuration option w3c/screen-wake-lock#265.
-
Chore: Mark Introduction as non-normative w3c/screen-wake-lock#263.
-
-
3 pull requests received 6 new comments.
-
Editorial: s/Feature Policy/Permissions Policy w3c/screen-wake-lock#266 (4 comments by @marcoscaceres, @reillyeon, @sidvishnoi)
-
w3c/battery
-
2 issues opened.
-
Update the reference to Feature Policy w3c/battery#26, by @xfq.
-
Add an explicit use cases and requirements section w3c/battery#25, by @anssiko.
-
-
1 issue received 3 new comments.
w3c/deviceorientation
-
2 issues received 2 new comments.
-
PermissionState is already defined in Permission API w3c/deviceorientation#82 (1 comment by @foolip)
-
1 pull request opened.
-
Drop duplicate PermissionState definition w3c/deviceorientation#88, by @foolip.
-
w3c/sensors
-
1 issue opened.
-
Update the reference to Feature Policy w3c/sensors#405, by @xfq.
-
w3c/device-posture
-
3 pull requests opened.
-
Polyfill demo w3c/device-posture#35, by @diekus-zz.
-
Add settings widget w3c/device-posture#34, by @kenchris.
-
Polyfill the CSS media features w3c/device-posture#33, by @kenchris.
-
-
3 pull requests merged.
-
Polyfill demo w3c/device-posture#35.
-
Add settings widget w3c/device-posture#34.
-
Polyfill the CSS media features w3c/device-posture#33.
-
w3c/ambient-light
-
2 pull requests merged.
-
Typo fix w3c/ambient-light#62.
-
Add a new editor w3c/ambient-light#59.
-
w3c/system-wake-lock
-
1 issue opened.
-
Use case: Fitness App w3c/system-wake-lock#2, by @CheloXL.
-
-
1 issue closed.
-
Where is the proposed specification located? w3c/system-wake-lock#1.
-
-
1 issue received 2 new comments.
-
Where is the proposed specification located? w3c/system-wake-lock#1 (2 comments by @CheloXL, @reillyeon)
-
Participants
-
2 participants joined.
-
Christine Perey (W3C Invited Experts) joined.
-
Nick Doty (W3C Invited Experts) joined.
-
GitHub
w3c/system-wake-lock
-
1 issue opened.
-
Where is the proposed specification located? w3c/system-wake-lock#1, by @JakeChampion.
-
-
1 issue received 3 new comments.
-
Where is the proposed specification located? w3c/system-wake-lock#1 (3 comments by @anssiko, @JakeChampion, @reillyeon)
-
w3c/geolocation
-
6 issues opened.
-
How to specify desired accuracy / resolution of data? w3c/geolocation#49, by @pes10k.
-
Require user activation to use API w3c/geolocation#48, by @pes10k.
-
Suggest permission lifetimes? w3c/geolocation#69, by @pes10k.
-
Watch process refers to undefined step 6 w3c/geolocation#44, by @DavidWiesner.
-
[meta] Wide review tracker - FPWD w3c/geolocation#43, by @xfq.
-
Publish as FPWD w3c/geolocation#42, by @marcoscaceres.
-
-
1 issue closed.
-
Watch process refers to undefined step 6 w3c/geolocation#44.
-
-
4 issues received 26 new comments.
-
Suggest permission lifetimes? w3c/geolocation#69 (10 comments by @anssiko, @marcoscaceres, @pes10k, @reillyeon)
-
Publish as FPWD w3c/geolocation#42 (10 comments by @anssiko, @marcoscaceres, @plehegar, @reillyeon, @xfq)
-
Require user activation to use API w3c/geolocation#48 (4 comments by @marcoscaceres, @pes10k, @reillyeon)
-
Watch process refers to undefined step 6 w3c/geolocation#44 (2 comments by @anssiko, @marcoscaceres)
-
-
2 pull requests opened.
-
Add sections, markup fixes, nits w3c/geolocation#46, by @marcoscaceres.
-
Editorial: fix jump to undefined step w3c/geolocation#45, by @marcoscaceres.
-
-
1 pull request merged.
-
Editorial: fix jump to undefined step w3c/geolocation#45.
-
-
2 pull requests received 7 new comments.
w3c/device-posture
-
23 issues opened.
-
Add link to the polyfill and explainer w3c/device-posture#32, by @anssiko.
-
rename spec? w3c/device-posture#30, by @diekus-zz.
-
Add "no-fold" as the first enumeration item w3c/device-posture#29, by @kenchris.
-
Don't say approximately w3c/device-posture#28, by @kenchris.
-
Use degree symbol w3c/device-posture#27, by @kenchris.
-
Explain in introduction the target form factors w3c/device-posture#26, by @anssiko.
-
What does ]0-110[ landscape-primary etc map to? w3c/device-posture#24, by @kenchris.
-
Make portrait-primary etc link to definition on screen orientation spec w3c/device-posture#23, by @kenchris.
-
should devices/angles/postures change based on the orientation of the hinge? w3c/device-posture#22, by @diekus-zz.
-
what happens if there is no fold present? w3c/device-posture#21, by @diekus-zz.
-
group media queries in section w3c/device-posture#20, by @diekus-zz.
-
add examples w3c/device-posture#19, by @diekus-zz.
-
add images to explain the posture table w3c/device-posture#18, by @diekus-zz.
-
explain the determination of a posture based on angle values and screen orientations w3c/device-posture#17, by @diekus-zz.
-
Make sure that the posture-values-table doesnt have gaps w3c/device-posture#16, by @diekus-zz.
-
Review media query section and value w3c/device-posture#15, by @diekus-zz.
-
complete the posture mapping table w3c/device-posture#13, by @kenchris.
-
Order the enums the same way w3c/device-posture#12, by @kenchris.
-
environment variable might be useless w3c/device-posture#11, by @kenchris.
-
Improve images w3c/device-posture#8, by @kenchris.
-
Improve README.md w3c/device-posture#7, by @kenchris.
-
Add posture explainations w3c/device-posture#5, by @kenchris.
-
Add CSS parts w3c/device-posture#4, by @kenchris.
-
-
22 issues closed.
-
Review media query section and value w3c/device-posture#15.
-
Add link to the polyfill and explainer w3c/device-posture#32.
-
explain the determination of a posture based on angle values and screen orientations w3c/device-posture#17.
-
add examples w3c/device-posture#19.
-
Make sure that the posture-values-table doesnt have gaps w3c/device-posture#16.
-
complete the posture mapping table w3c/device-posture#13.
-
add images to explain the posture table w3c/device-posture#18.
-
Don't say approximately w3c/device-posture#28.
-
What does ]0-110[ landscape-primary etc map to? w3c/device-posture#24.
-
Add CSS parts w3c/device-posture#4.
-
Make portrait-primary etc link to definition on screen orientation spec w3c/device-posture#23.
-
should devices/angles/postures change based on the orientation of the hinge? w3c/device-posture#22.
-
what happens if there is no fold present? w3c/device-posture#21.
-
Use degree symbol w3c/device-posture#27.
-
Add "no-fold" as the first enumeration item w3c/device-posture#29.
-
rename spec? w3c/device-posture#30.
-
Explain in introduction the target form factors w3c/device-posture#26.
-
group media queries in section w3c/device-posture#20.
-
Add posture explainations w3c/device-posture#5.
-
Order the enums the same way w3c/device-posture#12.
-
Improve README.md w3c/device-posture#7.
-
Improve images w3c/device-posture#8.
-
-
18 issues received 24 new comments.
-
what happens if there is no fold present? w3c/device-posture#21 (5 comments by @diekus-zz, @kenchris)
-
Explain in introduction the target form factors w3c/device-posture#26 (2 comments by @anssiko, @diekus-zz)
-
explain the determination of a posture based on angle values and screen orientations w3c/device-posture#17 (1 comment by @diekus-zz)
-
Make portrait-primary etc link to definition on screen orientation spec w3c/device-posture#23 (1 comment by @diekus-zz)
-
should devices/angles/postures change based on the orientation of the hinge? w3c/device-posture#22 (1 comment by @kenchris)
-
-
6 pull requests opened.
-
Add polyfill and minidemo w3c/device-posture#31, by @kenchris.
-
Fix respec errors w3c/device-posture#25, by @kenchris.
-
Screen fold angle media query w3c/device-posture#14, by @diekus-zz.
-
Add screen-fold-posture MQ w3c/device-posture#10, by @kenchris.
-
adds postures image w3c/device-posture#9, by @diekus-zz.
-
Add example w3c/device-posture#6, by @kenchris.
-
-
6 pull requests merged.
-
Add polyfill and minidemo w3c/device-posture#31.
-
Fix respec errors w3c/device-posture#25.
-
Screen fold angle media query w3c/device-posture#14.
-
adds postures image w3c/device-posture#9.
-
Add screen-fold-posture MQ w3c/device-posture#10.
-
Add example w3c/device-posture#6.
-
w3c/deviceorientation
-
1 issue opened.
-
Device motion sampling frequency w3c/deviceorientation#87, by @marcoscaceres.
-
-
1 issue closed.
-
Move fingerprintable APIs behind permissions w3c/deviceorientation#85.
-
-
1 pull request opened.
-
limit precision to mitigate sensor calibration fingerprinting w3c/deviceorientation#86, by @npdoty.
-
-
1 pull request merged.
-
limit precision to mitigate sensor calibration fingerprinting w3c/deviceorientation#86.
-
-
1 pull request received 9 new comments.
-
limit precision to mitigate sensor calibration fingerprinting w3c/deviceorientation#86 (9 comments by @anssiko, @marcoscaceres, @npdoty, @reillyeon)
-
w3c/battery
-
1 issue received 1 new comment.
w3c/magnetometer
-
1 issue reopened.
-
Security and Privacy Considerations w3c/magnetometer#2, by @anssiko.
-
-
1 issue received 5 new comments.
-
1 pull request opened.
-
Update security/privacy considerations with MagSpy w3c/magnetometer#56, by @lknik.
-
-
1 pull request merged.
-
Update security/privacy considerations with MagSpy w3c/magnetometer#56.
-
-
1 pull request received 2 new comments.
-
Update security/privacy considerations with MagSpy w3c/magnetometer#56 (2 comments by @anssiko, @lknik)
-
w3c/das-charter
-
1 issue opened.
-
Contact Picker API w3c/das-charter#97, by @anssiko.
-
w3c/screen-wake-lock
-
1 issue received 5 new comments.
-
Anyone implementing "system" lock? w3c/screen-wake-lock#232 (5 comments by @marcoscaceres, @mitchellwills, @mounirlamouri, @reillyeon, @tomayac)
-
Participants
-
3 participants joined.
-
Diego Gonzalez-Zuniga (Microsoft Corporation) joined.
-
Heejin Chung (Samsung Electronics Co., Ltd.) joined.
-
Laszlo Gombos (Samsung Electronics Co., Ltd.) joined.
-
-
1 organization joined.
-
Samsung Electronics Co., Ltd. joined.
-
GitHub
w3c/geolocation
-
5 issues closed.
-
Disable geolocation by default in cross-origin iframes w3c/geolocation#10.
-
Callbacks functions don't have a handleEvent operation w3c/geolocation#24.
-
Algorithms should integrate permission handling w3c/geolocation#37.
-
Consider adding Position.floorLevel w3c/geolocation#15.
-
Background Geolocation via Service Workers w3c/geolocation#13.
-
-
4 issues received 6 new comments.
-
Disable geolocation by default in cross-origin iframes w3c/geolocation#10 (3 comments by @engedy, @marcoscaceres)
-
-
3 pull requests opened.
-
Add feature policy support w3c/geolocation#41, by @marcoscaceres.
-
chore: update ReSpec usage w3c/geolocation#40, by @marcoscaceres.
-
fix: callbacks are not EventHandlers w3c/geolocation#39, by @marcoscaceres.
-
-
3 pull requests merged.
-
Add feature policy support w3c/geolocation#41.
-
chore: update ReSpec usage w3c/geolocation#40.
-
fix: callbacks are not EventHandlers w3c/geolocation#39.
-
-
2 pull requests received 5 new comments.
w3c/das-wg
-
1 pull request opened.
-
Align milestones with the proposed charter w3c/das-wg#30, by @anssiko.
-
-
1 pull request merged.
-
Align milestones with the proposed charter w3c/das-wg#30.
-
w3c/device-posture
-
3 pull requests opened.
-
Add algos to update the value and link to screen orientation lock w3c/device-posture#3, by @kenchris.
-
Add algos to update the value and link to screen orientation lock w3c/device-posture#2, by @kenchris.
-
Removed most wakelock stuff and added algos w3c/device-posture#1, by @kenchris.
-
-
2 pull requests merged.
-
Add algos to update the value and link to screen orientation lock w3c/device-posture#3.
-
Removed most wakelock stuff and added algos w3c/device-posture#1.
-
-
1 pull request closed.
-
Add algos to update the value and link to screen orientation lock w3c/device-posture#2.
-
w3c/contact-picker
-
1 issue opened.
-
[QUESTION] Why is the API not working in Vue.js w3c/contact-picker#32, by @tafelnl.
-
-
1 issue closed.
-
[QUESTION] Why is the API not working in Vue.js w3c/contact-picker#32.
-
-
1 issue received 3 new comments.
-
[QUESTION] Why is the API not working in Vue.js w3c/contact-picker#32 (3 comments by @rayankans, @tafelnl, @tomayac)
-
w3c/wake-lock
-
1 pull request opened.
-
Redirect immediately w3c/wake-lock#2, by @tidoust.
-
-
1 pull request merged.
-
Redirect immediately w3c/wake-lock#2.
-
w3c/deviceorientation
-
1 issue closed.
-
Update to constructor operations w3c/deviceorientation#80.
-
-
1 issue received 1 new comment.
GitHub
w3c/das-charter
-
4 issues opened.
-
Mention Web of Things WG in Coordination w3c/das-charter#93, by @xfq.
-
missing "will"? w3c/das-charter#89, by @samuelweiler.
-
move test-as-you-commit text? w3c/das-charter#88, by @samuelweiler.
-
consensual? w3c/das-charter#87, by @samuelweiler.
-
-
9 issues closed.
-
Mention Web of Things WG in Coordination w3c/das-charter#93.
-
move test-as-you-commit text? w3c/das-charter#88.
-
missing "will"? w3c/das-charter#89.
-
consensual? w3c/das-charter#87.
-
Web HID w3c/das-charter#80.
-
Any new sensor API? w3c/das-charter#4.
-
Integrate WebNFC w3c/das-charter#29.
-
Network Information status? w3c/das-charter#78.
-
Goals and Scope editorial w3c/das-charter#83.
-
-
2 issues reopened.
-
move test-as-you-commit text? w3c/das-charter#88, by @samuelweiler.
-
missing "will"? w3c/das-charter#89, by @samuelweiler.
-
-
8 issues received 26 new comments.
-
Mention Web of Things WG in Coordination w3c/das-charter#93 (8 comments by @anssiko, @ashimura, @plehegar)
-
-
8 pull requests opened.
-
Update DASCharter-2020.html w3c/das-charter#96, by @wseltzer.
-
Mention Web of Things WG in Coordination w3c/das-charter#95, by @xfq.
-
Editorial and typo fixes w3c/das-charter#94, by @wseltzer.
-
Move test-as-you-commit text to Success Criteria w3c/das-charter#92, by @xfq.
-
Editorial: Scope typo fix w3c/das-charter#91, by @xfq.
-
W3M review w3c/das-charter#90, by @anssiko.
-
Limit the spec to be upstreamed to HTML Media Capture w3c/das-charter#86, by @xfq.
-
Charter 2020 editorial w3c/das-charter#85, by @anssiko.
-
-
9 pull requests merged.
-
Update DASCharter-2020.html w3c/das-charter#96.
-
Mention Web of Things WG in Coordination w3c/das-charter#95.
-
Move test-as-you-commit text to Success Criteria w3c/das-charter#92.
-
Editorial and typo fixes w3c/das-charter#94.
-
Editorial: Scope typo fix w3c/das-charter#91.
-
W3M review w3c/das-charter#90.
-
Limit the spec to be upstreamed to HTML Media Capture w3c/das-charter#86.
-
Charter 2020 editorial w3c/das-charter#85.
-
Charter 2020 w3c/das-charter#84.
-
-
6 pull requests received 18 new comments.
-
Mention Web of Things WG in Coordination w3c/das-charter#95 (7 comments by @anssiko, @ashimura, @mlagally, @mmccool, @sebastiankb, @xfq)
-
w3c/das-wg
-
1 pull request opened.
-
Split Wake Lock API into Screen Wake Lock API & System Wake Lock API w3c/das-wg#29, by @anssiko.
-
-
1 pull request merged.
-
1 pull request closed.
-
Update the shortname of wake-lock w3c/das-wg#28.
-
-
1 pull request received 1 new comment.
w3c/contact-picker
-
1 issue closed.
-
We REALLY need this! w3c/contact-picker#20.
-
-
1 issue received 1 new comment.
w3c/screen-wake-lock
-
1 issue closed.
-
Link tests to spec w3c/screen-wake-lock#258.
-
-
1 issue received 2 new comments.
-
2 pull requests opened.
-
chore: update test links w3c/screen-wake-lock#261, by @Honry.
-
Proof-read after #255. w3c/screen-wake-lock#260, by @rakuco.
-
-
2 pull requests merged.
-
chore: update test links w3c/screen-wake-lock#261.
-
Proof-read after #255. w3c/screen-wake-lock#260.
-
-
2 pull requests received 6 new comments.
w3c/ambient-light
-
1 issue closed.
-
Update to constructor operations w3c/ambient-light#60.
-
-
1 issue received 1 new comment.
w3c/wake-lock
-
1 pull request merged.
-
Adapt w3c.json to repo status w3c/wake-lock#1.
-
GitHub
w3c/das-charter
-
5 issues opened.
-
Goals and Scope editorial w3c/das-charter#83, by @anssiko.
-
Success criteria - already released APIs w3c/das-charter#82, by @svgeesus.
-
Split Wake Lock API spec into two? w3c/das-charter#79, by @anssiko.
-
Network Information status? w3c/das-charter#78, by @anssiko.
-
-
2 issues closed.
-
Success criteria - already released APIs w3c/das-charter#82.
-
Split Wake Lock API spec into two? w3c/das-charter#79.
-
-
2 issues reopened.
-
Any new sensor API? w3c/das-charter#4, by @anssiko.
-
Integrate WebNFC w3c/das-charter#29, by @anssiko.
-
-
6 issues received 12 new comments.
-
2 pull requests opened.
-
Charter 2020 w3c/das-charter#84, by @anssiko.
-
Split Wake Lock API spec into two w3c/das-charter#81, by @xfq.
-
-
1 pull request merged.
-
Split Wake Lock API spec into two w3c/das-charter#81.
-
-
1 pull request received 10 new comments.
w3c/wake-lock
-
1 pull request opened.
-
Adapt w3c.json to repo status w3c/wake-lock#1, by @dontcallmedom.
-
-
1 pull request received 2 new comments.
w3c/screen-wake-lock
-
4 issues opened.
-
Link tests to spec w3c/screen-wake-lock#258, by @marcoscaceres.
-
New shortname w3c/screen-wake-lock#257, by @marcoscaceres.
-
Add a note to the spec about fingerprinting w3c/screen-wake-lock#256, by @caraitto.
-
Consider dropping wakeLock from WorkerNavigator w3c/screen-wake-lock#254, by @bholley.
-
-
4 issues closed.
-
Anyone implementing "system" lock? w3c/screen-wake-lock#232.
-
Break specification into levels w3c/screen-wake-lock#253.
-
Consider dropping wakeLock from WorkerNavigator w3c/screen-wake-lock#254.
-
Add a note to the spec about fingerprinting w3c/screen-wake-lock#256.
-
-
1 issue reopened.
-
Add a note to the spec about fingerprinting w3c/screen-wake-lock#256, by @caraitto.
-
-
7 issues received 14 new comments.
-
Add a note to the spec about fingerprinting w3c/screen-wake-lock#256 (2 comments by @caraitto, @reillyeon)
-
Consider dropping wakeLock from WorkerNavigator w3c/screen-wake-lock#254 (2 comments by @bholley, @reillyeon)
-
Anyone implementing "system" lock? w3c/screen-wake-lock#232 (2 comments by @marcoscaceres, @reillyeon)
-
2 pull requests opened.
-
Update the shortname w3c/screen-wake-lock#259, by @xfq.
-
Convert to purely screen wake lock w3c/screen-wake-lock#255, by @marcoscaceres.
-
-
2 pull requests merged.
-
Update the shortname w3c/screen-wake-lock#259.
-
Convert to purely screen wake lock w3c/screen-wake-lock#255.
-
-
2 pull requests received 35 new comments.
-
Convert to purely screen wake lock w3c/screen-wake-lock#255 (31 comments by @anssiko, @Honry, @marcoscaceres, @rakuco, @reillyeon)
-
w3c/das-wg
-
1 pull request opened.
-
Update the shortname of wake-lock w3c/das-wg#28, by @xfq.
-
w3c/html-media-capture
-
1 issue opened.
-
The empty string is not defined as a conforming value for the capture attribute w3c/html-media-capture#34, by @sideshowbarker.
-
-
1 issue closed.
-
The empty string is not defined as a conforming value for the capture attribute w3c/html-media-capture#34.
-
-
2 issues received 4 new comments.
-
The empty string is not defined as a conforming value for the capture attribute w3c/html-media-capture#34 (3 comments by @anssiko, @sideshowbarker)
-
-
1 pull request opened.
-
Define the empty string as a conforming value w3c/html-media-capture#35, by @anssiko.
-
-
1 pull request merged.
-
Define the empty string as a conforming value w3c/html-media-capture#35.
-
w3c/deviceorientation
-
1 issue received 1 new comment.
w3c/accelerometer
-
1 pull request opened.
-
Images optimized w3c/accelerometer#56, by @Druhin13.
-
-
1 pull request merged.
-
Images optimized w3c/accelerometer#56.
-
-
1 pull request received 2 new comments.
GitHub
w3c/screen-wake-lock
-
2 issues opened.
-
Break specification into levels w3c/screen-wake-lock#253, by @reillyeon.
-
Add example usage of onrelease event. w3c/screen-wake-lock#250, by @scheib.
-
-
1 issue closed.
-
Add example usage of onrelease event. w3c/screen-wake-lock#250.
-
-
4 issues received 20 new comments.
-
Break specification into levels w3c/screen-wake-lock#253 (7 comments by @anssiko, @hadriann, @marcoscaceres, @reillyeon)
-
Add example usage of onrelease event. w3c/screen-wake-lock#250 (7 comments by @marcoscaceres, @rakuco, @scheib)
-
Anyone implementing "system" lock? w3c/screen-wake-lock#232 (4 comments by @marcoscaceres, @reillyeon)
-
Need maximum screen brightness mode w3c/screen-wake-lock#129 (2 comments by @brainfoolong, @marcoscaceres)
-
-
2 pull requests opened.
-
editorial: Use new HTML activation model w3c/screen-wake-lock#252, by @rakuco.
-
Update and modernize example #2. w3c/screen-wake-lock#251, by @rakuco.
-
-
2 pull requests merged.
-
Update and modernize example #2. w3c/screen-wake-lock#251.
-
editorial: Use new HTML activation model w3c/screen-wake-lock#252.
-
-
2 pull requests received 11 new comments.
-
editorial: Use new HTML activation model w3c/screen-wake-lock#252 (6 comments by @mustaqahmed, @rakuco)
-
w3c/magnetometer
-
1 pull request opened.
-
Amend png image fallback code w3c/magnetometer#55, by @tidoust.
-
-
1 pull request merged.
-
Amend png image fallback code w3c/magnetometer#55.
-
w3c/accelerometer
-
1 issue opened.
-
device calibration of accelerometers may reveal precise hardware fingerprint w3c/accelerometer#54, by @npdoty.
-
-
1 issue closed.
-
Image fallback code fails very badly if *both* images error w3c/accelerometer#48.
-
-
1 issue received 1 new comment.
-
Image fallback code fails very badly if *both* images error w3c/accelerometer#48 (1 comment by @anssiko)
-
-
1 pull request opened.
-
Amend PNG image fallback code w3c/accelerometer#55, by @tidoust.
-
-
1 pull request merged.
-
Amend PNG image fallback code w3c/accelerometer#55.
-
-
1 pull request received 1 new comment.
w3c/geolocation
-
1 issue received 3 new comments.
-
Support geolocation (especially geofencing) in the "background" w3c/geolocation#214 (3 comments by @fernap3, @stefanloerwald, @tomayac)
-
w3c/sensors
-
1 issue opened.
-
1 issue received 1 new comment.
-
device fingerprinting may also refer to the factory (or other) calibration of the device w3c/sensors#404 (1 comment by @reillyeon)
-
w3c/contact-picker
-
1 issue opened.
-
Acknowledge the history of contact API proposals w3c/contact-picker#30, by @jyasskin.
-
-
1 issue closed.
-
Acknowledge the history of contact API proposals w3c/contact-picker#30.
-
-
1 pull request opened.
-
Add a section on previous attempts and the differences w3c/contact-picker#31, by @rayankans.
-
-
1 pull request merged.
-
Add a section on previous attempts and the differences w3c/contact-picker#31.
-
-
1 pull request received 3 new comments.
-
Add a section on previous attempts and the differences w3c/contact-picker#31 (3 comments by @beverloo, @rayankans)
-
w3c/deviceorientation
-
1 issue received 3 new comments.
-
Move fingerprintable APIs behind permissions w3c/deviceorientation#85 (3 comments by @maryammjd, @npdoty, @pes10k)
-
GitHub
w3c/geolocation
-
1 issue received 3 new comments.
-
Support geolocation (especially geofencing) in the "background" w3c/geolocation#214 (3 comments by @jeantil, @josephrocca, @tomayac)
-
w3c/screen-wake-lock
-
1 issue opened.
-
Navigation and maintaining locks w3c/screen-wake-lock#249, by @martinthomson.
-
-
1 issue received 1 new comment.
w3c/deviceorientation
-
1 issue received 9 new comments.
-
Move fingerprintable APIs behind permissions w3c/deviceorientation#85 (9 comments by @anssiko, @npdoty, @pes10k, @reillyeon)
-
w3c/sensors
-
1 pull request opened.
-
Fix up the focused area restrictions. w3c/sensors#403, by @jyasskin.
-
-
1 pull request received 2 new comments.