Bug 213753

Summary: Update the user agent on iPadOS to use 11 to match macOS Safari
Product: WebKit Reporter: Matt Gilligan <matthew_gilligan>
Component: WebCore Misc.Assignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: achristensen, conrad_shultz, matthew_gilligan, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: iPhone / iPad   
OS: Unspecified   
Attachments:
Description Flags
Patch
none
Patch none

Matt Gilligan
Reported 2020-06-29 13:58:32 PDT
Update the user agent on iPadOS to use 11 to match macOS Safari
Attachments
Patch (1.77 KB, patch)
2020-06-29 15:23 PDT, Matt Gilligan 		no flags
DetailsFormatted DiffDiff
Patch (1.71 KB, patch)
2020-07-06 07:19 PDT, Matt Gilligan 		no flags
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Matt Gilligan
Comment 1 2020-06-29 13:59:13 PDT
<rdar://problem/64706928>
Matt Gilligan
Comment 2 2020-06-29 15:23:40 PDT
Created attachment 403125 [details] Patch
Alex Christensen
Comment 3 2020-07-01 10:25:02 PDT
Comment on attachment 403125 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=403125&action=review Could we have a better process for synchronizing these than just manually updating after we announce new operating systems? > Source/WebCore/ChangeLog:10 > + No new tests -- no new or changed functionality. This is not true. There is definitely changed functionality.
Matt Gilligan
Comment 4 2020-07-01 13:43:21 PDT
There is a bug tracking automating these updates: https://bugs.webkit.org/show_bug.cgi?id=207500 It might be possible to do something similar to rdar://problem/44566710, but it's probably too late for 14.0.
Matt Gilligan
Comment 5 2020-07-06 07:19:19 PDT
Created attachment 403591 [details] Patch
EWS
Comment 6 2020-07-06 09:48:55 PDT
Committed r263970: <https://trac.webkit.org/changeset/263970> All reviewed patches have been landed. Closing bug and clearing flags on attachment 403591 [details].
Note You need to log in before you can comment on or make changes to this bug.