W3C home > Mailing lists > Public > public-device-apis@w3.org > September 2012

Re: When should a Device API be exposed? Re: Atmospheric pressure sensosr API

From: Tobie Langel <tobie@fb.com>
Date: Sat, 8 Sep 2012 20:17:21 +0000
To: "Carr, Wayne" <wayne.carr@intel.com>
CC: Doug Turner <doug.turner@gmail.com>, Marcos Caceres <w3c@marcosc.com>, "Tran, Dzung D" <dzung.d.tran@intel.com>, "public-device-apis@w3.org" <public-device-apis@w3.org>
Message-ID: <1AE988FB-FC74-4AD5-A4DD-875C3701B779@fb.com>
On Sep 8, 2012, at 20:01, "Carr, Wayne" <wayne.carr@intel.com> wrote:

> I assumed Marcos meant just the onxxx attribute on Window (not addEventListener which always is there).  All of these type specs add onxxx on Window.  For fingerprinting reasons, it seems you don't want it there just when there is a sensor.   So either always there for all of these type specs, or don't use that at all and just use addEventListener.  (this is about all of these, not this draft in particular).

How do we reconcile developers relying on feature detection and avoiding device fingerprinting at the same time?

Received on Saturday, 8 September 2012 20:17:44 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:53:55 UTC