On Tue, Jul 15, 2014 at 7:34 PM, Hanno Schlichting <[email protected]> wrote: > On 15.07.2014, at 22:34 , Kyle Huey <[email protected]> wrote: >> On Tue, Jul 15, 2014 at 12:51 PM, Blake Kaplan <[email protected]> wrote: >>> On Mon, Jul 14, 2014 at 9:04 PM, Tim Chien <[email protected]> wrote: >>> >>>> I am not objecting anything, but I am interested to know why aren't we >>>> creating a DOM::Wifi module but a FirefoxOS::Wifi module? >>> >>> I discussed this briefly with khuey yesterday and the distinction basically >>> came down to the fact that the wifi code exists to talk directly to the >>> driver, select networks, and related tasks (with a little bit of glue to >>> expose the functionality to certain web pages). All of those things are OS >>> specific. > > Aren’t we using those Wifi API’s as part of the geolocation code? On Firefox > desktop we pretty much only use WiFi lookups as a basis for geolocation, as > there’s typically no cell modem or GPS available. > > This code is part of dom/system/NetworkGeolocationProvider.js, so also lives > in the DOM area. > > Hanno
We're talking about the stuff in dom/wifi. You're not using that, AFAIK. This code is only built on b2g. - Kyle _______________________________________________ governance mailing list [email protected] https://lists.mozilla.org/listinfo/governance
