RESOLVED FIXED 106345
[GTK][WK2] platform/gtk/accessibility/input-slider.html is failing
https://bugs.webkit.org/show_bug.cgi?id=106345
Summary [GTK][WK2] platform/gtk/accessibility/input-slider.html is failing
Zan Dobersek
Reported 2013-01-08 10:26:22 PST
The platform/gtk/accessibility/input-slider.html layout test is failing on GTK WK2 port. Here's the diff: --- /home/zan/Dev/webkit/webkit/WebKitBuild/Release/layout-test-results/platform/gtk/accessibility/input-slider-expected.txt +++ /home/zan/Dev/webkit/webkit/WebKitBuild/Release/layout-test-results/platform/gtk/accessibility/input-slider-actual.txt @@ -1,4 +1,4 @@ - 825 + 500 @@ -11,14 +11,14 @@ ** Increment the slider, test slider value and div set on 'update' event RUN(sliderAXObject.increment()) -EXPECTED (sliderInput.value == '55') OK -EXPECTED (valueDiv.innerText == '55') OK +EXPECTED (sliderInput.value == '55'), OBSERVED '0' FAIL +EXPECTED (valueDiv.innerText == '55'), OBSERVED '0' FAIL ** Decrement the slider, test slider value and div set on 'update' event RUN(sliderInput.value = 22) RUN(sliderAXObject.decrement()) -EXPECTED (sliderInput.value == '17') OK -EXPECTED (valueDiv.innerText == '17') OK +EXPECTED (sliderInput.value == '17'), OBSERVED '0' FAIL +EXPECTED (valueDiv.innerText == '17'), OBSERVED '0' FAIL ** Change slider range RUN(sliderInput.setAttribute('max', 1000)) @@ -29,12 +29,12 @@ ** Re-test incrementing the slider RUN(sliderInput.value = 600) RUN(sliderAXObject.increment()) -EXPECTED (sliderInput.value == '625') OK -EXPECTED (valueDiv.innerText == '625') OK +EXPECTED (sliderInput.value == '625'), OBSERVED '500' FAIL +EXPECTED (valueDiv.innerText == '625'), OBSERVED '500' FAIL ** Re-test decrementing the slider RUN(sliderInput.value = 850) RUN(sliderAXObject.decrement()) -EXPECTED (sliderInput.value == '825') OK -EXPECTED (valueDiv.innerText == '825') OK +EXPECTED (sliderInput.value == '825'), OBSERVED '500' FAIL +EXPECTED (valueDiv.innerText == '825'), OBSERVED '500' FAIL
Attachments
Mario Sanchez Prada
Comment 1 2013-09-30 03:56:23 PDT
This test is now consistently passing in WK2 after r156541, so I'm removing it from the the TestExpectations file.
Note You need to log in before you can comment on or make changes to this bug.