Hi Colin,
> On Apr 26, 2018, at 8:57 AM, Colin Bendell | +1.613.914.3387
> wrote:
>
> […] images to a device. I have a laundry list of other examples where the
> server might actually know more than the client to prevent a) a broken
> user experience and b) prevent cellular data waste.
Would y
6:22 PM
From: "Michael Catanzaro"
To: "Ricky Young"
Cc: "Anne van Kesteren" , "webkit-dev@lists.webkit.org"
Subject: Re: [webkit-dev] New iOS versions sending bogus User-Agent build data
On Thu, Apr 26, 2018 at 7:15 AM, Ricky Young wrote:
> I guess
On 26 April 2018 at 14:25, Ali Juma wrote:
> It's worth noting that https://bugs.webkit.org/show_bug.cgi?id=182629 added
> back the OS version to the UA string, at least on trunk (the reasons given
> there, in https://bugs.webkit.org/show_bug.cgi?id=182629#c6, sound exactly
> like those mentioned
On Thu, Apr 26, 2018 at 12:48 PM, Colin Bendell | +1.613.914.3387
wrote:
Can you give me an example where UA parsing is punishing users of
alternative user agents? Is this a theoretical problem, or a
widespread problem? I'm not asking to be divisive, but because I know
for a fact that UA parsing
It's worth noting that https://bugs.webkit.org/show_bug.cgi?id=182629 added
back the OS version to the UA string, at least on trunk (the reasons given
there, in https://bugs.webkit.org/show_bug.cgi?id=182629#c6, sound exactly
like those mentioned by Colin in this thread).
On Thu, Apr 26, 2018 at 1
On 26 April 2018 at 13:18, Konstantin Tokarev wrote:
> 26.04.2018, 20:09, "Colin Bendell | +1.613.914.3387" :
>> On 26 April 2018 at 12:23, Konstantin Tokarev wrote:
>>> Not to mention those evil people who reject page loading for user agents
>>> they don't (want to) support
>>
>> How does lock
26.04.2018, 20:09, "Colin Bendell | +1.613.914.3387" :
> On 26 April 2018 at 12:23, Konstantin Tokarev wrote:
>> Not to mention those evil people who reject page loading for user agents
>> they don't (want to) support
>
> How does locking the UA solve the misbehaving parsers in the wild?
Ther
On 26 April 2018 at 12:23, Konstantin Tokarev wrote:
> 26.04.2018, 19:16, "Michael Catanzaro" :
>> On Thu, Apr 26, 2018 at 11:13 AM, Michael Catanzaro
>> wrote:
>>> By fixing the WebKit bug, of course. And in the meantime you can work
>>> around it on the server side by not using 
26.04.2018, 19:16, "Michael Catanzaro" :
> On Thu, Apr 26, 2018 at 11:13 AM, Michael Catanzaro
> wrote:
>> By fixing the WebKit bug, of course. And in the meantime you can work
>> around it on the server side by not using , right?
>
> Consider the other perspective on this problem
On Thu, Apr 26, 2018 at 11:13 AM, Michael Catanzaro
wrote:
By fixing the WebKit bug, of course. And in the meantime you can work
around it on the server side by not using , right?
Consider the other perspective on this problem. If other servers look
at the WebKit version in the U
On Thu, Apr 26, 2018 at 10:57 AM, Colin Bendell | +1.613.914.3387
wrote:
How do we navigate this?
By fixing the WebKit bug, of course. And in the meantime you can work
around it on the server side by not using , right?
Michael
___
webkit-dev mail
I'm running into this issue right now with the locked UA. Here are the
challenges:
1. ios 11.3 safari bug broke despite advertising
`accept: video/*` in the request. (see bug 185029). I now need to use
UA detection to patch versions of a response based on existing bugs.
In short, we as an industry
On Thu, Apr 26, 2018 at 7:15 AM, Ricky Young wrote:
I guess that soon it won't be possible to determine iOS version
distribution using User-Agent sniffing. Right? Is there an
alternative for the browser to tell the iOS version?
Hi,
The very point of no longer sending the verison in the user
ant to access this information?
>
> Sent: Thursday, April 26, 2018 at 1:54 PM
> From: "Anne van Kesteren"
> To: "Ricky Young"
> Cc: "Konstantin Tokarev" , "webkit-dev@lists.webkit.org"
>
> Subject: Re: [webkit-dev] New iOS versions sendin
uot;Ricky Young"
Cc: "Konstantin Tokarev" , "webkit-dev@lists.webkit.org"
Subject: Re: [webkit-dev] New iOS versions sending bogus User-Agent build data
On Thu, Apr 26, 2018 at 12:30 PM, Ricky Young wrote:
> I read the report and still find it hard to understand,
On Thu, Apr 26, 2018 at 12:30 PM, Ricky Young wrote:
> I read the report and still find it hard to understand, if "User Agent
> sniffing is a terrible way to determine whether a browser supports certain
> features", what is the correct way of doing it?
https://developer.mozilla.org/en-US/docs/L
ct way of doing it?
Sent: Thursday, April 26, 2018 at 1:16 PM
From: "Konstantin Tokarev"
To: "Ricky Young" , "webkit-dev@lists.webkit.org"
Subject: Re: [webkit-dev] New iOS versions sending bogus User-Agent build data
26.04.2018, 13:08, "Ricky Young"
26.04.2018, 13:08, "Ricky Young" :
> Until iOS 11.3, User-Agent build data contained the build that corresponds to
> the device (e.g. Mobile/15D100 if the requesting device was running iOS
> 11.2.6).
>
> Since iOS 11.3 was released I noticed that the User-Agent that is reported to
> the brower
Until iOS 11.3, User-Agent build data contained the build that corresponds to the device (e.g. Mobile/15D100 if the requesting device was running iOS 11.2.6).
Since iOS 11.3 was released I noticed that the User-Agent that is reported to the brower is reporting a bogus build, i.e Mobile/15E148, r
19 matches
Mail list logo
