- From: Anssi Kostiainen via GitHub <sysbot+gh@w3.org>
- Date: Wed, 10 May 2017 10:43:58 +0000
- To: public-device-apis-log@w3.org
>It would first be good to hear the technical arguments for the different options (which are a different interface or a constructor option). See the response to 4 in https://github.com/w3c/magnetometer/pull/21#issuecomment-292492004 (GH linking to fragments seem broken, so search "alexshalamov commented on Apr 7".) Another benefit is, that a separate constructor makes it easier to drop the feature should we later on figure out we made a mistake, and *especially* makes it easier for web developers to feature detect that. Also, early developer feedback from https://w3c.github.io/accelerometer/ was that using options was confusing for the reasons @alexshalamov outlined in his comment. We initially shipped with [constructor options][1] and later on moved to [separate constructors][2], so we have done some field-testing already. As for the name, proposing `UncalibratedMagnetometer` as a compromise. Going once, going twice, ... ? [1]: https://www.w3.org/TR/2016/WD-accelerometer-20160913/#dictdef-accelerometersensoroptions [2]: https://w3c.github.io/accelerometer/#api -- GitHub Notification of comment by anssiko Please view or discuss this issue at https://github.com/w3c/magnetometer/pull/21#issuecomment-300444865 using your GitHub account
Received on Wednesday, 10 May 2017 10:44:04 UTC