The test in LayoutTests/media/track/track-cue-rendering.html no longer passes. It did very recently (at most 48 hours ago). Here's the output diff: --- /Users/antoine/Builds/Release/layout-test-results/media/track/track-cue-rendering-expected.txt +++ /Users/antoine/Builds/Release/layout-test-results/media/track/track-cue-rendering-actual.txt @@ -34,22 +34,22 @@ Test the cue display colors and font. RUN(video.width = 320) RUN(video.height = 240) -EXPECTED (getComputedStyle(textTrackDisplayElement(video)).fontSize == '12px') OK +EXPECTED (getComputedStyle(textTrackDisplayElement(video)).fontSize == '12px'), OBSERVED '24px' FAIL RUN(video.width = 640) RUN(video.height = 480) -EXPECTED (getComputedStyle(textTrackDisplayElement(video)).fontSize == '24px') OK +EXPECTED (getComputedStyle(textTrackDisplayElement(video)).fontSize == '24px'), OBSERVED '48px' FAIL RUN(video.width = 1280) RUN(video.height = 960) -EXPECTED (getComputedStyle(textTrackDisplayElement(video)).fontSize == '48px') OK +EXPECTED (getComputedStyle(textTrackDisplayElement(video)).fontSize == '48px'), OBSERVED '96px' FAIL RUN(video.width = 2560) RUN(video.height = 1440) -EXPECTED (getComputedStyle(textTrackDisplayElement(video)).fontSize == '72px') OK +EXPECTED (getComputedStyle(textTrackDisplayElement(video)).fontSize == '72px'), OBSERVED '144px' FAIL EXPECTED (getComputedStyle(textTrackDisplayElement(video)).fontFamily == 'sans-serif') OK EXPECTED (getComputedStyle(textTrackDisplayElement(video)).color == 'rgb(255, 255, 255)') OK -EXPECTED (getComputedStyle(textTrackDisplayElement(video, 'display').firstChild).backgroundColor == 'rgba(0, 0, 0, 0.796875)'), OBSERVED 'rgba(0, 0, 0, 0.8)' FAIL +EXPECTED (getComputedStyle(textTrackDisplayElement(video, 'display').firstChild).backgroundColor == 'rgba(0, 0, 0, 0.796875)'), OBSERVED 'rgba(0, 0, 0, 0)' FAIL END OF TEST
<rdar://problem/12825429>
It appears that this test has been flaky: http://webkit-test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=media%2Ftrack%2Ftrack-cue-rendering.html
Hm... I guess we should file a bug new instead.