Newly added layout test media/click-volume-bar-not-pausing.html is failing on EFL port after r148131. --- /home/buildslave-1/webkit-buildslave/efl-linux-64-release-wk2/build/layout-test-results/media/click-volume-bar-not-pausing-expected.txt +++ /home/buildslave-1/webkit-buildslave/efl-linux-64-release-wk2/build/layout-test-results/media/click-volume-bar-not-pausing-actual.txt @@ -1,11 +1,2 @@ -Click on volume bar on a MediaDocument does not pause. +FAIL: Timed out waiting for notifyDone to be called - -EVENT(playing) -EXPECTED (mediaElement.volume == '1') OK -EXPECTED (mediaElement.paused == 'false') OK -EVENT(volumechange) -EXPECTED (mediaElement.volume != '1') OK -EXPECTED (mediaElement.paused == 'false') OK -END OF TEST -
Link to the failure on bot. http://build.webkit.org/results/EFL%20Linux%2064-bit%20Release%20WK2/r148741%20%287524%29/media/click-volume-bar-not-pausing-diff.txt
The purpose of the test is testing that clicking on the volume bar does not pause the media. The revision was handled in bug 112548 behind the test is the following: 1. Create a MediaDocument (a regular ones does not have that problem). 2. Get it playing. In normal circumstances it does, but it some cases it doesn't so we force a pause and a play to get the PLAYING event. We check the pause and volume. 3. Force a click on the volume bar. For that we hover the mute button, which should make the volume bar show up and then we send a click to the center of the volume bar. Then the mouse event should go down to the volume bar mouse handler, be marked as default handled and not passed to the MediaDocument which would pause the media in case it gets the event. If the test is timing out it can be because it is either not getting the playing or volumechange events. The first could be caused because of some race condition and the second because the click doesn't reach the volume bar. I hope this helps.
Closing this bug because the EFL port has been removed from trunk. If you feel this bug applies to a different upstream WebKit port and was closed in error, please either update the title and reopen the bug, or leave a comment to request this.