[webkit-dev] New iOS versions sending bogus User-Agent build data

Colin Bendell | +1.613.914.3387 colin at bendell.ca
Thu Apr 26 10:48:24 PDT 2018

On 26 April 2018 at 13:18, Konstantin Tokarev <annulen at yandex.ru> wrote:
> 26.04.2018, 20:09, "Colin Bendell | +1.613.914.3387" <colin at bendell.ca>:
>> On 26 April 2018 at 12:23, Konstantin Tokarev <annulen at yandex.ru> 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?
> There will be less information in UA and therefore less reasons for developers
> to do this, instead of using direct feature testing
>> They will still misbehave and break the user experience. However,
>> those of us that are trying to optimize the user experience by working
>> around bugs for specific versions are now handicapped and punished.
> While parsing UA string handicaps and punishes users of alternative user agents.

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 is improving the user experience. I can
give you dozens of examples where we must resort to UA parsing for the
betterment of the user (for all flavors of UAs).

Do you have any alternatives other than "more javascript"?

Again I ask, is there room for compromise where we can expose the
version details in the UA (or some alternative) so that we ensure a
consistent and optimized user experience?


More information about the webkit-dev mailing list