Devices and Sensors Working Group - Activity in 2014
No matches.
TR publications
-
2 documents published.
-
Vibration API published as a Proposed Recommendation. History of Vibration API
-
Battery Status API published as a Candidate Recommendation Snapshot. History of Battery Status API
-
Participants
-
1 organization joined.
-
Universidade Federal de Alagoas joined.
-
-
1 organization left.
-
TAPQUO S.L. left.
-
GitHub
w3c/deviceorientation
-
1 issue opened.
-
Security considerations w3c/deviceorientation#13, by @marcoscaceres.
-
Participants
-
1 participant joined.
-
Tobie Langel (W3C Invited Experts) joined.
-
GitHub
w3c/sensors
-
12 issues opened.
-
Allowing data batching when poll frequency < sensor frequency w3c/sensors#13, by @tobie.
-
Expose sensors to workers w3c/sensors#12, by @tobie.
-
What precisely, do we mean by "generic"? w3c/sensors#10, by @tobie.
-
Should sensors be singleton? w3c/sensors#8, by @tobie.
-
Sensor discovery w3c/sensors#7, by @tobie.
-
Agree on coarseness of frequency option w3c/sensors#6, by @tobie.
-
Have a good feature detection story w3c/sensors#5, by @tobie.
-
Provide a way of tying sensor requests to animation frames w3c/sensors#4, by @tobie.
-
Provide polyfills for retro-fitted sensors. w3c/sensors#3, by @tobie.
-
Handle sensors with multiple values w3c/sensors#2, by @tobie.
-
Retrofit existing sensor APIs w3c/sensors#1, by @tobie.
-
-
1 issue reopened.
-
Agree on coarseness of frequency option w3c/sensors#6, by @tobie.
-
-
10 issues received 79 new comments.
-
Agree on coarseness of frequency option w3c/sensors#6 (14 comments by @borismus, @richtr, @rwaldron, @tobie)
-
Should sensor EventTarget be immediately available or should they be accessed through a promise? w3c/sensors#9 (12 comments by @borismus, @richtr, @rwaldron, @tobie)
-
Allowing data batching when poll frequency < sensor frequency w3c/sensors#13 (6 comments by @borismus, @rwaldron, @tobie)
-
Provide a way of tying sensor requests to animation frames w3c/sensors#4 (6 comments by @domenic, @richtr, @rwaldron, @tobie)
-
Handle sensors with multiple values w3c/sensors#2 (5 comments by @borismus, @richtr, @rwaldron, @tobie)
-
1 pull request opened.
-
Add contributing.md. w3c/sensors#11, by @anssiko.
-
-
1 pull request merged.
-
Add contributing.md. w3c/sensors#11.
-
TR publications
-
1 document published.
-
Media Capture Depth Stream Extensions published as a First Public Working Draft. History of Media Capture Depth Stream Extensions
-
GitHub
w3c/screen-wake-lock
-
1 issue opened.
-
Do we really need a way to get actual wake lock status? w3c/screen-wake-lock#43, by @boiler23.
-
-
1 issue closed.
-
allow iframes to use the wakelock api w3c/screen-wake-lock#40.
-
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
Update the specification to reflect suggestions in issue #39 w3c/screen-wake-lock#42, by @andrey-logvinov.
-
Update the specification to reflect suggestions in issue #39 w3c/screen-wake-lock#41, by @andrey-logvinov.
-
-
1 pull request merged.
-
Update the specification to reflect suggestions in issue #39 w3c/screen-wake-lock#42.
-
-
1 pull request closed.
-
Update the specification to reflect suggestions in issue #39 w3c/screen-wake-lock#41.
-
-
2 pull requests received 3 new comments.
-
Update the specification to reflect suggestions in issue #39 w3c/screen-wake-lock#41 (2 comments by @andrey-logvinov, @boiler23)
-
Update the specification to reflect suggestions in issue #39 w3c/screen-wake-lock#42 (1 comment by @boiler23)
-
TR publications
-
2 documents published.
-
HTML Media Capture published as a Candidate Recommendation Snapshot. History of HTML Media Capture
-
Vibration API published as a Candidate Recommendation Snapshot. History of Vibration API
-
Participants
-
2 organizations joined.
-
Tencent joined.
-
OpenJS Foundation joined.
-
-
2 organizations left.
-
4D left.
-
Cox Communications, Inc. left.
-
GitHub
w3c/screen-wake-lock
-
1 issue opened.
-
allow iframes to use the wakelock api w3c/screen-wake-lock#40, by @marcoscaceres.
-
-
2 issues received 21 new comments.
-
Update spec to match WHATWG discussion w3c/screen-wake-lock#39 (19 comments by @andrey-logvinov, @boiler23, @domenic, @marcoscaceres, @mounirlamouri)
-
allow iframes to use the wakelock api w3c/screen-wake-lock#40 (2 comments by @boiler23, @marcoscaceres)
-
w3c/deviceorientation
-
1 issue opened.
-
Add way of getting current orientation w3c/deviceorientation#11, by @marcoscaceres.
-
-
2 issues received 13 new comments.
-
Define the relationship between device orientation/motion events and screen orientation in the spec w3c/deviceorientation#4 (10 comments by @marcoscaceres, @richtr)
-
Add way of getting current orientation w3c/deviceorientation#11 (3 comments by @marcoscaceres, @richtr)
-
-
1 pull request opened.
-
Add deviceorientation and devicemotion feature detection conformance requirement w3c/deviceorientation#12, by @richtr.
-
-
1 pull request received 11 new comments.
-
Add deviceorientation and devicemotion feature detection conformance requirement w3c/deviceorientation#12 (11 comments by @mvano, @richtr)
-
TR publications
-
1 document published.
-
Battery Status API published as a Last Call Working Draft. History of Battery Status API
-
GitHub
w3c/deviceorientation
-
1 issue opened.
-
[Callback] extended attributes w3c/deviceorientation#9, by @anssiko.
-
-
1 issue received 3 new comments.
-
Define the relationship between device orientation/motion events and screen orientation in the spec w3c/deviceorientation#4 (3 comments by @marcoscaceres, @richtr)
-
-
1 pull request opened.
-
Add screen-adjusted device orientation attributes to DeviceOrientationEvent interface w3c/deviceorientation#10, by @richtr.
-
-
1 pull request merged.
-
Update specification boilerplate w3c/deviceorientation#8.
-
-
2 pull requests received 2 new comments.
-
Add 'Handling Screen Orientation Changes' annex to specification w3c/deviceorientation#7 (1 comment by @richtr)
-
w3c/screen-wake-lock
-
20 issues opened.
-
Update spec to match WHATWG discussion w3c/screen-wake-lock#39, by @marcoscaceres.
-
CSS or JS? w3c/screen-wake-lock#38, by @marcoscaceres.
-
WakeLock needs to inherit from EventTarget w3c/screen-wake-lock#36, by @marcoscaceres.
-
`isHeld()` should probably be something like `getLocks()` w3c/screen-wake-lock#32, by @marcoscaceres.
-
Broken link to WAKE-LOCK-USECASES w3c/screen-wake-lock#29, by @boiler23.
-
wakeLock.isHeld() should probably be asynchronous? w3c/screen-wake-lock#28, by @boiler23.
-
Racy promises need to be dealt with... w3c/screen-wake-lock#26, by @marcoscaceres.
-
Lifecycle of release and regain ... is hard. w3c/screen-wake-lock#24, by @marcoscaceres.
-
README link broke w3c/screen-wake-lock#22, by @marcoscaceres.
-
Wake locks are lost, but not "changed" w3c/screen-wake-lock#21, by @marcoscaceres.
-
Spec should use 'noLegacyStyle: true' w3c/screen-wake-lock#20, by @marcoscaceres.
-
WakeLock interface: redundant text w3c/screen-wake-lock#19, by @marcoscaceres.
-
Example 2 is wrong w3c/screen-wake-lock#18, by @marcoscaceres.
-
WakeLockChange event is not well specified w3c/screen-wake-lock#17, by @marcoscaceres.
-
Attributes and methods should be algorithmic w3c/screen-wake-lock#16, by @marcoscaceres.
-
Examples should be at the start of the document w3c/screen-wake-lock#15, by @marcoscaceres.
-
WakeLockChange event should be moved w3c/screen-wake-lock#14, by @marcoscaceres.
-
Use cases section w3c/screen-wake-lock#13, by @marcoscaceres.
-
Header links w3c/screen-wake-lock#12, by @marcoscaceres.
-
Rename repo w3c/screen-wake-lock#11, by @marcoscaceres.
-
-
15 issues closed.
-
CSS or JS? w3c/screen-wake-lock#38.
-
`isHeld()` should probably be something like `getLocks()` w3c/screen-wake-lock#32.
-
WakeLock needs to inherit from EventTarget w3c/screen-wake-lock#36.
-
Broken link to WAKE-LOCK-USECASES w3c/screen-wake-lock#29.
-
WakeLockChange event is not well specified w3c/screen-wake-lock#17.
-
Examples should be at the start of the document w3c/screen-wake-lock#15.
-
WakeLockChange event should be moved w3c/screen-wake-lock#14.
-
Attributes and methods should be algorithmic w3c/screen-wake-lock#16.
-
Spec should use 'noLegacyStyle: true' w3c/screen-wake-lock#20.
-
Header links w3c/screen-wake-lock#12.
-
Use cases section w3c/screen-wake-lock#13.
-
Example 2 is wrong w3c/screen-wake-lock#18.
-
WakeLock interface: redundant text w3c/screen-wake-lock#19.
-
README link broke w3c/screen-wake-lock#22.
-
Rename repo w3c/screen-wake-lock#11.
-
-
2 issues reopened.
-
Lifecycle of release and regain ... is hard. w3c/screen-wake-lock#24, by @marcoscaceres.
-
Wake locks are lost, but not "changed" w3c/screen-wake-lock#21, by @marcoscaceres.
-
-
12 issues received 72 new comments.
-
Wake locks are lost, but not "changed" w3c/screen-wake-lock#21 (20 comments by @boiler23, @marcoscaceres, @mounirlamouri)
-
Lifecycle of release and regain ... is hard. w3c/screen-wake-lock#24 (14 comments by @boiler23, @marcoscaceres, @mounirlamouri)
-
Update spec to match WHATWG discussion w3c/screen-wake-lock#39 (10 comments by @boiler23, @marcoscaceres, @mounirlamouri)
-
`isHeld()` should probably be something like `getLocks()` w3c/screen-wake-lock#32 (7 comments by @boiler23, @marcoscaceres, @mounirlamouri)
-
wakeLock.isHeld() should probably be asynchronous? w3c/screen-wake-lock#28 (4 comments by @boiler23, @marcoscaceres, @mounirlamouri)
-
Racy promises need to be dealt with... w3c/screen-wake-lock#26 (4 comments by @boiler23, @marcoscaceres, @mounirlamouri)
-
-
10 pull requests opened.
-
WakeLock inherits EventTarget (closes #36) w3c/screen-wake-lock#37, by @marcoscaceres.
-
Has and get current locks (closes #32) w3c/screen-wake-lock#35, by @marcoscaceres.
-
Described automatic release/regaining locks (closes #24) w3c/screen-wake-lock#34, by @marcoscaceres.
-
Made the return type explicit on promise w3c/screen-wake-lock#33, by @marcoscaceres.
-
Specified "onlost" attribute of WakeLock w3c/screen-wake-lock#31, by @boiler23.
-
Fixed ReSpec warnings w3c/screen-wake-lock#30, by @boiler23.
-
Fixed up event doc structure (closes #14, #15, #17, #21) w3c/screen-wake-lock#27, by @marcoscaceres.
-
Moved to using noLegacyStyle (closes #20, #16) w3c/screen-wake-lock#25, by @marcoscaceres.
-
Initial cleanup of doc w3c/screen-wake-lock#23, by @marcoscaceres.
-
Clarified in more detail how wakeLock.release() should work w3c/screen-wake-lock#10, by @boiler23.
-
-
11 pull requests merged.
-
Has and get current locks (closes #32) w3c/screen-wake-lock#35.
-
WakeLock inherits EventTarget (closes #36) w3c/screen-wake-lock#37.
-
Described automatic release/regaining locks (closes #24) w3c/screen-wake-lock#34.
-
Made the return type explicit on promise w3c/screen-wake-lock#33.
-
Specified "onlost" attribute of WakeLock w3c/screen-wake-lock#31.
-
Fixed ReSpec warnings w3c/screen-wake-lock#30.
-
Fixed up event doc structure (closes #14, #15, #17, #21) w3c/screen-wake-lock#27.
-
Moved to using noLegacyStyle (closes #20, #16) w3c/screen-wake-lock#25.
-
Initial cleanup of doc w3c/screen-wake-lock#23.
-
Clarified in more detail how wakeLock.release() should work w3c/screen-wake-lock#10.
-
Another approach to API w3c/screen-wake-lock#9.
-
-
8 pull requests received 23 new comments.
-
Moved to using noLegacyStyle (closes #20, #16) w3c/screen-wake-lock#25 (6 comments by @boiler23, @marcoscaceres)
-
Specified "onlost" attribute of WakeLock w3c/screen-wake-lock#31 (4 comments by @boiler23, @marcoscaceres)
-
Described automatic release/regaining locks (closes #24) w3c/screen-wake-lock#34 (3 comments by @boiler23)
-
Fixed up event doc structure (closes #14, #15, #17, #21) w3c/screen-wake-lock#27 (1 comment by @boiler23)
-
Clarified in more detail how wakeLock.release() should work w3c/screen-wake-lock#10 (1 comment by @marcoscaceres)
-
Participants
-
1 participant left.
-
Jinsong Wang (W3C) left.
-
GitHub
w3c/screen-wake-lock
-
1 issue closed.
-
Clarify use case: "watch video without screen dimming (or worse, locking)" w3c/screen-wake-lock#1.
-
-
1 issue received 1 new comment.
-
Clarify use case: "watch video without screen dimming (or worse, locking)" w3c/screen-wake-lock#1 (1 comment by @marcoscaceres)
-
-
4 pull requests opened.
-
Another approach to API w3c/screen-wake-lock#9, by @boiler23.
-
Example updated to be less confusing w3c/screen-wake-lock#8, by @boiler23.
-
Fix typo and grammar w3c/screen-wake-lock#7, by @toddmotto.
-
Initial TR draft w3c/screen-wake-lock#6, by @boiler23.
-
-
2 pull requests merged.
-
Fix typo and grammar w3c/screen-wake-lock#7.
-
Initial TR draft w3c/screen-wake-lock#6.
-
-
1 pull request closed.
-
Example updated to be less confusing w3c/screen-wake-lock#8.
-
-
3 pull requests received 36 new comments.
-
Another approach to API w3c/screen-wake-lock#9 (25 comments by @boiler23, @marcoscaceres, @mounirlamouri)
-
Example updated to be less confusing w3c/screen-wake-lock#8 (10 comments by @boiler23, @marcoscaceres)
-
w3c/geolocation
-
1 pull request opened.
-
First draft of use cases, simplified geofencing proposal. w3c/geolocation#1, by @cwilso.
-
TR publications
-
3 documents published.
-
Ambient Light Events published as a Last Call Working Draft. History of Ambient Light Events
-
HTML Media Capture published as a Last Call Working Draft. History of HTML Media Capture
-
Vibration API published as a Last Call Working Draft. History of Vibration API
-
GitHub
w3c/screen-wake-lock
-
3 pull requests opened.
-
README.md updated (added my alternative proposal reference) w3c/screen-wake-lock#5, by @boiler23.
-
clarified use case for score-keeping app w3c/screen-wake-lock#4, by @sethladd.
-
More similar to Firefox OS approach w3c/screen-wake-lock#3, by @boiler23.
-
-
3 pull requests merged.
-
README.md updated (added my alternative proposal reference) w3c/screen-wake-lock#5.
-
clarified use case for score-keeping app w3c/screen-wake-lock#4.
-
More similar to Firefox OS approach w3c/screen-wake-lock#3.
-
-
1 pull request closed.
-
Add new use case w3c/screen-wake-lock#2.
-
-
4 pull requests received 8 new comments.
-
More similar to Firefox OS approach w3c/screen-wake-lock#3 (4 comments by @boiler23, @marcoscaceres)
-
README.md updated (added my alternative proposal reference) w3c/screen-wake-lock#5 (1 comment by @marcoscaceres)
-
Participants
-
1 organization joined.
-
Yandex joined.
-
GitHub
w3c/screen-wake-lock
-
1 issue opened.
-
Clarify use case: "watch video without screen dimming (or worse, locking)" w3c/screen-wake-lock#1, by @marcoscaceres.
-
-
1 pull request opened.
-
Add new use case w3c/screen-wake-lock#2, by @sethladd.
-
-
1 pull request received 3 new comments.
TR publications
-
1 document published.
-
The Network Information API published as a Note. History of The Network Information API
-
GitHub
w3c/deviceorientation
-
2 pull requests opened.
-
Update specification boilerplate w3c/deviceorientation#8, by @richtr.
-
Add 'Handling Screen Orientation Changes' annex to specification w3c/deviceorientation#7, by @richtr.
-
-
1 pull request merged.
-
Add additional worked examples... w3c/deviceorientation#5.
-
-
2 pull requests received 5 new comments.
-
Add 'Handling Screen Orientation Changes' annex to specification w3c/deviceorientation#7 (1 comment by @richtr)
GitHub
w3c/deviceorientation
-
2 issues opened.
-
webkitCompassHeading / webkitCompassAccuracy w3c/deviceorientation#6, by @richtr.
-
Define the relationship between device orientation/motion events and screen orientation in the spec w3c/deviceorientation#4, by @richtr.
-
-
1 pull request opened.
-
Add additional worked examples... w3c/deviceorientation#5, by @richtr.
-
-
1 pull request received 47 new comments.
TR publications
-
2 documents published.
-
Vibration API published as a Last Call Working Draft. History of Vibration API
-
Network Service Discovery published as a Working Draft. History of Network Service Discovery
-
Participants
-
1 organization left.
-
Mobile Web Forum left.
-
GitHub
w3c/deviceorientation
-
3 pull requests opened.
-
Fix angle ranges in the spec. w3c/deviceorientation#3, by @timvolodine.
-
Add project README.md w3c/deviceorientation#2, by @richtr.
-
Minor editorial updates w3c/deviceorientation#1, by @richtr.
-
-
3 pull requests merged.
-
Fix angle ranges in the spec. w3c/deviceorientation#3.
-
Add project README.md w3c/deviceorientation#2.
-
Minor editorial updates w3c/deviceorientation#1.
-
-
2 pull requests received 5 new comments.
TR publications
-
6 documents published.
-
Calendar API published as a Note. History of Calendar API
-
Pick Contacts Intent published as a Note. History of Pick Contacts Intent
-
Pick Media Intent published as a Note. History of Pick Media Intent
-
The Messaging API published as a Note. History of The Messaging API
-
The System Information API published as a Note. History of The System Information API
-
Web Intents Addendum - Local Services published as a Note. History of Web Intents Addendum - Local Services
-
Participants
-
1 organization joined.
-
Mitsubishi Electric Corporation joined.
-