fast/forms/range/slider-mouse-events.html --- /ramdisk/qt-linux-32-release-webkit2/build/layout-test-results/fast/forms/range/slider-mouse-events-expected.txt +++ /ramdisk/qt-linux-32-release-webkit2/build/layout-test-results/fast/forms/range/slider-mouse-events-actual.txt @@ -1,18 +1,13 @@ This tests that slider controls get mousedown, mousemove, input, and mouseup events and properly set its value. mousemove -mousedown +input 0 +input +40 mousemove input -mouseup -40 -mousemove -mousedown +5 input -5 -mousemove -input -mouseup 20 fast/forms/range/slider-onchange-event.html --- /ramdisk/qt-linux-32-release-webkit2/build/layout-test-results/fast/forms/range/slider-onchange-event-expected.txt +++ /ramdisk/qt-linux-32-release-webkit2/build/layout-test-results/fast/forms/range/slider-onchange-event-actual.txt @@ -4,4 +4,6 @@ change input change +input +change
It works for me, the output here on WTR is: Content-Type: text/plain This tests that slider controls get the onchange event and that it is sent after the DOMInput event. input change input change #EOF #EOF #EOF This match the expected file, i.e. the test pass on run-webkit-tests. Would you test it again?
Ah, btw I tested it under r126874
All two test passes on x86-64 Linux Qt Release WebKit2 with r127108.
(In reply to comment #3) > All two test passes on x86-64 Linux Qt Release WebKit2 with r127108. In this case we should unskip them. ;)
Unskip landed in r127133. Thanks for the testing.
Reopen, because they still fail ... It's strange ... I skipped them again. They pass if we run only these tests, but fail if we run all tests. One more DRT/WTR sideeffect bug. :-/ Otherwise I noticed now, these tests are flakey on WK1, but they pass after retry.
fast/forms/range/slider-onchange-event.html now passing on wk2 https://trac.webkit.org/changeset/150892
=== Bulk closing of Qt bugs === If you believe that this bug report is still relevant for a non-Qt port of webkit.org, please re-open it and remove [Qt] from the summary. If you believe that this is still an important QtWebKit bug, please fill a new report at https://bugreports.qt-project.org and add a link to this issue. See http://qt-project.org/wiki/ReportingBugsInQt for additional guidelines.