Bug 81352
| Summary: | Add support for W3C Sensor API | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Dominik Röttsches (drott) <d-r> |
| Component: | WebCore JavaScript | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | brandon, bugzilla, dinu.jacob, donggwan.kim, eoconnor, jknotten, kennyluck, kisaragi.effective, kvserr, mcatanzaro, peter, shezbaig.wk |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | |||
| Bug Blocks: | 78947 | ||
Dominik Röttsches (drott)
We would like to upstream our implementation of W3C Sensor API [1].
As we are aware that this is a young specification, we propose to have it default #ifdef-disabled.
However, we believe it could be useful for certain ports or useful for being accessed by Chrome extensions.
Let's use this as meta bug for tracking.
[1] http://dvcs.w3.org/hg/dap/raw-file/tip/sensor-api/Overview.html
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Brandon McConnell
Any update on this ticket and this one which I think is related?: https://bugs.webkit.org/show_bug.cgi?id=145268
Michael Catanzaro
Looks like the latest version of this spec is https://www.w3.org/TR/generic-sensor/
The first step would be to request a standards position at https://github.com/WebKit/standards-positions
kisaragi.effective
It has rejected: https://github.com/WebKit/standards-positions/issues/347