W3C home > Mailing lists > Public > whatwg@whatwg.org > October 2014

Re: [whatwg] Adding a property to navigator for getting device model

From: Mounir Lamouri <mounir@lamouri.fr>
Date: Thu, 02 Oct 2014 20:57:19 +1000
Message-Id: <1412247439.2982180.174302497.4DB29013@webmail.messagingengine.com>
To: Jonas Sicking <jonas@sicking.cc>
Cc: WHAT Working Group <whatwg@whatwg.org>
On Wed, 1 Oct 2014, at 19:43, Jonas Sicking wrote:
> On Wed, Oct 1, 2014 at 2:27 AM, Mounir Lamouri <mounir@lamouri.fr> wrote:
> > On Wed, 1 Oct 2014, at 15:01, Jonas Sicking wrote:
> >> On Tue, Sep 30, 2014 at 4:40 AM, Mounir Lamouri <mounir@lamouri.fr>
> >> wrote:
> >> > On Wed, 24 Sep 2014, at 11:54, Jonas Sicking wrote:
> >> >> Thoughts?
> >> >
> >> > Do you have any data that makes you think that those websites would stop
> >> > using UA sniffing but start using navigator.deviceModel if they had that
> >> > property available?
> >>
> >> I know that the Cordova module for exposing this information is one of
> >> the most popular Cordova modules, so that's a pretty good indication.
> >> But I don't have data directly from websites.
> >
> > When you were pointing that websites currently do UA sniffing is it on
> > the client side of the server side?
> 
> I'd imagine UA sniffing happens more often on the server side, though
> I suspect it varies with the reason why people do it.
> 
> But the Cordova API is client side, so there's definitely desire to
> have it there too.

Isn't Cordova experience feedback a bit out of scope if usually
developers do UA sniffing on the server side? It seems that such a
feature would mostly benefit web sites that already entirely live on the
client side and might be more inclined to do feature detection.

-- Mounir
Received on Thursday, 2 October 2014 10:57:47 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:24 UTC