[ macOS wk2 ] fast/forms/auto-fill-button/caps-lock-indicator-should-be-visible-after-hiding-auto-fill-strong-password-button.html is a flaky failure 
https://bugs.webkit.org/show_bug.cgi?id=215304
Summary [ macOS wk2 ] fast/forms/auto-fill-button/caps-lock-indicator-should-be-visib...
Hector Lopez
Reported 2020-08-07 17:20:11 PDT
fast/forms/auto-fill-button/caps-lock-indicator-should-be-visible-after-hiding-auto-fill-strong-password-button.html This test is a flaky failure on macOS wk2 according to history. The first occurrence of failure is at r252008 but seems a one off. Test is more consistently flakiness is on macOS Catalina wk2 Release with the first occurrence at r260568 History: https://results.webkit.org/?suite=layout-tests&test=fast%2Fforms%2Fauto-fill-button%2Fcaps-lock-indicator-should-be-visible-after-hiding-auto-fill-strong-password-button.html&limit=50000 Diff: The actual image includes the text cursor or caret. Please see attachments or link here: https://build.webkit.org/results/Apple-Catalina-Release-WK2-Tests/r265393%20(7699)/fast/forms/auto-fill-button/caps-lock-indicator-should-be-visible-after-hiding-auto-fill-strong-password-button-diffs.html
Attachments
Expected image (21.76 KB, image/png)
2020-08-07 17:20 PDT, Hector Lopez 		no flags
Details
Actual image (21.77 KB, image/png)
2020-08-07 17:21 PDT, Hector Lopez 		no flags
Details
Diff image (2.24 KB, image/png)
2020-08-07 17:21 PDT, Hector Lopez 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Hector Lopez
Comment 1 2020-08-07 17:20:47 PDT
Created attachment 406231 [details] Expected image
Hector Lopez
Comment 2 2020-08-07 17:21:21 PDT
Created attachment 406232 [details] Actual image
Hector Lopez
Comment 3 2020-08-07 17:21:44 PDT
Created attachment 406233 [details] Diff image
Radar WebKit Bug Importer
Comment 4 2020-08-07 17:22:42 PDT
<rdar://problem/66707574>
Hector Lopez
Comment 5 2020-08-07 17:36:43 PDT
Test expectations changed while investigated: https://trac.webkit.org/changeset/265402/webkit
Note You need to log in before you can comment on or make changes to this bug.