For chromium it fails on the debug bots and the windows bots: http://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=animations%2Ffirst-letter-play-state.html. So far it's failing on at least one GTK bot as well: http://test-results.appspot.com/dashboards/flakiness_dashboard.html#group=%40ToT%20-%20webkit.org&tests=animations%2Ffirst-letter-play-state.html The output looks something like the following for all the failures: FAIL - "left" property for "box1" element at 0.1s expected: 200 but saw: 239.59207153320312 FAIL - "left" property for "box1" element at 0.13s expected: 200 but saw: 239.59207153320312 The largest values for left that I saw was on Chromium Linux debug: 264.8
This test is time sensitive, we are using a setTimeout and animation-play-state with a small time value.
Test does not exist on WebKit Source (searched to find the commit, which deleted but couldn't find). Plus this was for 'Chromium' fork.