fast/text-autosizing/ios/idempotentmode/idempotent-autosizing-after-changing-initial-scale.html Description: This test is failing consistently on iPadOS wk2 Debug. The test appears to have regressed with the introduction of the changes in r261940. History: https://results.webkit.org/?suite=layout-tests&test=fast%2Ftext-autosizing%2Fios%2Fidempotentmode%2Fidempotent-autosizing-after-changing-initial-scale.html&platform=ios&model=iPad%20(5th%20generation)&limit=50000 Diff: --- /Volumes/Data/slave/ipados-simulator-13-release-tests-wk2/build/layout-test-results/fast/text-autosizing/ios/idempotentmode/idempotent-autosizing-after-changing-initial-scale-expected.txt +++ /Volumes/Data/slave/ipados-simulator-13-release-tests-wk2/build/layout-test-results/fast/text-autosizing/ios/idempotentmode/idempotent-autosizing-after-changing-initial-scale-actual.txt @@ -8,17 +8,17 @@ After changing initial scale to 0.5 none auto -8px 13px -12px 17px -14px 19px -16px 19px +8px 8px +12px 12px +14px 14px +16px 16px 20px 20px After changing initial scale to 0.75 none auto -8px 10px -12px 14px -14px 16px +8px 8px +12px 12px +14px 14px 16px 16px 20px 20px
<rdar://problem/63729887>
I am able to reproduce the failures with r261940, but cannot reproduce the issue with r261939 using the following command (adjusting the checkout to match the commit): --ipad-simulator --debug --iterations 99 --exit-after-n-failures 3 -f fast/text-autosizing/ios/idempotentmode/idempotent-autosizing-after-changing-initial-scale.html r261940: [3/99] fast/text-autosizing/ios/idempotentmode/idempotent-autosizing-after-changing-initial-scale.html failed unexpectedly (text diff) [4/99] fast/text-autosizing/ios/idempotentmode/idempotent-autosizing-after-changing-initial-scale.html failed unexpectedly (text diff) [5/99] fast/text-autosizing/ios/idempotentmode/idempotent-autosizing-after-changing-initial-scale.html failed unexpectedly (text diff) Exiting early after 3 failures. 3 tests run. r261939: All 99 tests ran as expected.
I have marked this test as failing while this issue is investigated. https://trac.webkit.org/changeset/262256/webkit
Looks like Myles filed a new bug to fix this. *** This bug has been marked as a duplicate of bug 212564 ***