Example: <meta name="viewport" content="width=device-width, initial-scale=0.94, minimum-scale=0.94"> Expected minimum and initial scales: 0.94 Observed minimum and initial scales: 0.9415 (tested on iPhone SE simulator)
<rdar://problem/45744786>
Created attachment 353679 [details] Patch
Comment on attachment 353679 [details] Patch Attachment 353679 [details] did not pass mac-wk2-ews (mac-wk2): Output: https://webkit-queues.webkit.org/results/9826500 New failing tests: http/tests/security/anchor-download-block-crossorigin.html
Created attachment 353682 [details] Archive of layout-test-results from ews104 for mac-sierra-wk2 The attached test failures were seen while running run-webkit-tests on the mac-wk2-ews. Bot: ews104 Port: mac-sierra-wk2 Platform: Mac OS X 10.12.6
Comment on attachment 353679 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=353679&action=review > Source/WebCore/ChangeLog:3 > + [iOS] Viewport tag with minimum-scale sometimes causes the minimum scale to be close to the specified value This should say "close to but not exactly" or something. This also doesn't seem to describe the real user-facing impact of the bug.
Comment on attachment 353679 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=353679&action=review >> Source/WebCore/ChangeLog:3 >> + [iOS] Viewport tag with minimum-scale sometimes causes the minimum scale to be close to the specified value > > This should say "close to but not exactly" or something. > > This also doesn't seem to describe the real user-facing impact of the bug. Sounds good — changed the title to reflect the real user-facing impact.
Created attachment 353710 [details] Patch for landing
Comment on attachment 353710 [details] Patch for landing Clearing flags on attachment: 353710 Committed r237743: <https://trac.webkit.org/changeset/237743>