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

[Brent Fulgham]

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 you mind documenting those items in a Bugzilla report? We are interested 
in specific use cases that suffer with a frozen user agent string, and what 
(apparently bad) techniques you need to use to work around it.

Thanks,

-Brent



___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

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

[Ricky Young]

I can totally understand your intentions, it feels like that in 2018 UA should
not be a relevant piece of information, and especially not be a factor in the
decision if a server should serve a website to a certain request.

But UA is how the Internet currently works. Correct me if I'm wrong, but it 
feels
like you are trying to change the Internet. Are you trying to get rid of it for 
good?

I understand that these kind of drastic, revolutionary, changes might take 
casualties,
I feel like the industry was not given a chance to adopt to this change.
 

Sent: Thursday, April 26, 2018 at 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 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 agent is to
make it difficult for websites to determine the operating system
version.

We already have to deal with enough serious web compatibility problems
caused by the rest of the information in the user agent. I'm pleased
that the version number is now stable -- that's a huge improvement --
but I won't be happy until Safari and other major browsers start
sending fully-randomized UAs, or else a stub or blank UA
("Mozilla/5.0").

Michael
 
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

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

[Colin Bendell]

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 by Colin in this thread).

Thanks for the catch. I had missed this commit. This is helpful.

On 26 April 2018 at 15:40, Michael Catanzaro  wrote:
> I would say it's the most serious web compatibility problem that exists
> today. Our users complain and blame us when important websites are broken in
> WebKit because of it. I have personally wasted days [1] of [2] development
> [3] effort [4] playing with WebKit's user agent quirks to get important
> websites to work properly.

Yea, I get that. The current state of the UA is terrible. It's really
an archeological map of browser evolution. It's like going on a
first-date and the first thing you talk about is your family tree, and
how great-grandpa-andreesen who is all but estranged from the family.
It is a tad embarrassing :)

On 26 April 2018 at 15:40, Michael Catanzaro  wrote:
> On Thu, Apr 26, 2018 at 12:48 PM, Colin Bendell  wrote:
>> 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?
>
> I don't know. I wish there was, but I don't think so. If you have any
> suggestions, that'd be great, but I think it's going to be extremely
> difficult or impossible to solve this problem in a way that makes everyone
> happy.

I was only partially joking about the need for a UA2 spec. Perhaps it
is time to bring this to one of the w3c working groups. I'll take it
off this thread though :)

/colin
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

[webkit-dev] why webkitgtk called "wayland" or "x11“ graphic backed directly?

[tugouxp]

Hi:
 i am a new beginner of of webkit,  i meet a problem when i review the code of 
webkitgtk-2.18.6. in directory


./webkitgtk-2.18.6/Source/WebCore/platform/graphic


i see there are two graphic backend "PlatformDisplayX11" and 
"PlatformDisplayWayland" are inherited from webcore class PlatformDisplay,  my 
questions is, 
why webkit call the x11 or wayland directly without through the GTK graphic 
interface?  the graphic backend should be the GTK right?   so in my believe,  
it should be the GTK lib not the webkit call  wayland or x11, where am i wrong?


x11/PlatformDisplayX11.h:38:class PlatformDisplayX11 final : public 
PlatformDisplay {
wayland/PlatformDisplayWayland.h:37:class PlatformDisplayWayland : public 
PlatformDisplay {


thanks for your kindly support and i much appreciate.
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev