Bug 288247
Summary: | Remove User Agent Override for espn.com | ||
---|---|---|---|
Product: | WebKit | Reporter: | Karl Dubost <karlcow> |
Component: | WebKit Misc. | Assignee: | Karl Dubost <karlcow> |
Status: | RESOLVED FIXED | ||
Severity: | Normal | CC: | schill1025, webkit-bug-importer |
Priority: | P2 | Keywords: | InRadar |
Version: | WebKit Nightly Build | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
URL: | http://espn.com/ | ||
See Also: | https://bugs.webkit.org/show_bug.cgi?id=263619 |
Karl Dubost
Currently the Chrome UA override in place for espn.com seems to break the user experience of ESPN.
Let's remove it and work with the ESPN team on how to give a good user experience for Safari users.
https://developer.apple.com/forums/thread/774994
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Graham
Hi Karl, thanks for opening this bug. I can work with you on improving ESPN experience. Can you let me know when the Chrome UA override can be removed?
Graham
(In reply to Graham from comment #1)
> Hi Karl, thanks for opening this bug. I can work with you on improving ESPN
> experience. Can you let me know when the Chrome UA override can be removed?
I do see the E+ playback issue when I have 'Disable site-specific hacks' checked. I am working with internal teams to get this resolved
Karl Dubost
Hi Graham, thanks for the status update.
That's very cool
I will prepare a patch myself to remove the espn UA override, and hold it until there is a resolution.
Radar WebKit Bug Importer
<rdar://problem/145520927>
Graham
hey Karl, our team has validated that E+ playback is working as expected in Safari when using 'Disable site-specific hacks'. We are ready for removal of the UA override.
Thank you!
Karl Dubost
This is great. I will land the patch.
It should be available in the next Safari release. I don't have an exact date yet.
Thanks a lot for the quick turnaround. This is super helpful.
Karl Dubost
Patch is landed on Safari.
User Agent overrides for desktop happens on Safari side of the code.
I will close the bug here. :)
(There is an intent to move this mechanism on the WebKit Side so it becomes more visible for companies. Bug 263619 but not yet fully planned.)
Graham
Thanks Karl. So we will see this change reflected in Safari 18.3?