[webkit-dev] Upstreaming Support for W3C Sensor API
abarth at webkit.org
Fri Mar 16 14:15:56 PDT 2012
Historically, the WebKit project hasn't had the warmest relationship
with the DAP working group, and we've tended to be conservative about
which DAP APIs we merge into trunk. The Sensor API appears to be
fairly early in its lifecycle. As far as I can tell, it hasn't even
reached FPWD, which means, among other things, that the W3C patent
process hasn't started. These factors lead me to think that we should
wait a bit before landing the feature in trunk.
You might consider implementing this feature as a WebCore Module
<https://trac.webkit.org/wiki/Modules>. If you go that route, the
implementation should be fairly loosely coupled with the rest of
WebCore, which means implementing the feature first on GitHub (a la
<https://trac.webkit.org/wiki/UsingGitHub>) might be a good choice.
This approach will give you a chance to experiment with an
implementation and receive feedback from the WebKit community without
being blocked on merging your feature into trunk.
2012/3/16 Adam Barth <abarth at webkit.org>:
> The specification appears to be here:
> Has this specification reached FPWD yet? http://www.w3.org/TR/sensor/
> returns a 404.
> 2012/3/16 Dominik Röttsches <dominik.rottsches at linux.intel.com>:
>> Hello webkit-dev,
>> We would like to upstream our implementation of W3C Sensor API .
>> 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.
>> Your feedback is welcome.
>> For reference, we created meta bug
>> Dominik Röttsches
>> webkit-dev mailing list
>> webkit-dev at lists.webkit.org
More information about the webkit-dev