WebKitTestRunner needs to implement layoutTestController.setPageVisibility()
Created attachment 131936 [details] Patch
Created attachment 133371 [details] Patch
Comment on attachment 133371 [details] Patch Attachment 133371 [details] did not pass win-ews (win): Output: http://queues.webkit.org/results/12122232
Comment on attachment 133371 [details] Patch Attachment 133371 [details] did not pass qt-wk2-ews (qt): Output: http://queues.webkit.org/results/12116369
Comment on attachment 133371 [details] Patch Attachment 133371 [details] did not pass gtk-ews (gtk): Output: http://queues.webkit.org/results/12123321
Comment on attachment 133371 [details] Patch Attachment 133371 [details] did not pass gtk-ews (gtk): Output: http://queues.webkit.org/results/12122292
Created attachment 135599 [details] Patch
Comment on attachment 135599 [details] Patch Attachment 135599 [details] did not pass win-ews (win): Output: http://queues.webkit.org/results/12327003
Comment on attachment 135599 [details] Patch Attachment 135599 [details] did not pass gtk-ews (gtk): Output: http://queues.webkit.org/results/12327029
Created attachment 135643 [details] Patch
Comment on attachment 135643 [details] Patch Clearing flags on attachment: 135643 Committed r113235: <http://trac.webkit.org/changeset/113235>
All reviewed patches have been landed. Closing bug.
It seems this patch broke some test with Qt WK2 bots: fast/events/page-visibility-transition-test.html fast/events/page-visibility-iframe-propagation-test.html http://build.webkit.sed.hu/results/x86-64%20Linux%20Qt%20Release%20WebKit2%20%28Amazon%20EC2%29/r113305%20%28798%29/results.html
(In reply to comment #13) > It seems this patch broke some test with Qt WK2 bots: > fast/events/page-visibility-transition-test.html > fast/events/page-visibility-iframe-propagation-test.html > > http://build.webkit.sed.hu/results/x86-64%20Linux%20Qt%20Release%20WebKit2%20%28Amazon%20EC2%29/r113305%20%28798%29/results.html I will have a look, thanks. At a first glance, I don't get how the other Page Visibility layout tests can be working and these ones not if they all make use of the same layouttestcontroller functions...