WebKitTestRunner needs layoutTestController.setWindowIsKey
<rdar://problem/8213853>
*** Bug 69397 has been marked as a duplicate of this bug. ***
Created attachment 109992 [details] Patch
Created attachment 110012 [details] Patch which fixes Windows
Comment on attachment 110012 [details] Patch which fixes Windows Attachment 110012 [details] did not pass gtk-ews (gtk): Output: http://queues.webkit.org/results/9998003
Comment on attachment 110012 [details] Patch which fixes Windows View in context: https://bugs.webkit.org/attachment.cgi?id=110012&action=review > Tools/ChangeLog:9 > + Since this does window-level stuff, it now has to be asynchronous, so add I don’t understand that. Can’t it be a synchronous call from the web process to the UI process?
(In reply to comment #6) > (From update of attachment 110012 [details]) > View in context: https://bugs.webkit.org/attachment.cgi?id=110012&action=review > > > Tools/ChangeLog:9 > > + Since this does window-level stuff, it now has to be asynchronous, so add > > I don’t understand that. Can’t it be a synchronous call from the web process to the UI process? It could, and I guess we don't care for testing-only methods. I was following Joh's lead on the addChromeInputField stuff.
Created attachment 110395 [details] Patch
http://trac.webkit.org/changeset/97081