It allows to open links in new windows, and it handles popups too.
Created attachment 119606 [details] Patch
Comment on attachment 119606 [details] Patch Attachment 119606 [details] did not pass chromium-ews (chromium-xvfb): Output: http://queues.webkit.org/results/10910795 New failing tests: http/tests/inspector/resource-parameters.html http/tests/inspector-enabled/console-clear-arguments-on-frame-remove.html
(In reply to comment #2) > (From update of attachment 119606 [details]) > Attachment 119606 [details] did not pass chromium-ews (chromium-xvfb): > Output: http://queues.webkit.org/results/10910795 > > New failing tests: > http/tests/inspector/resource-parameters.html > http/tests/inspector-enabled/console-clear-arguments-on-frame-remove.html this looks unrelated to the patch.
Comment on attachment 119606 [details] Patch It looks ok to me, just one concern, what about the estimated-load-progress and title properties notifications in the new window? I think they should be handled like in the parent browser window.
(In reply to comment #4) > (From update of attachment 119606 [details]) > It looks ok to me, just one concern, what about the estimated-load-progress and title properties notifications in the new window? I think they should be handled like in the parent browser window. It's exactly the same, they are connected in constructed method of the BrowserWindow, or what do you mean?
Comment on attachment 119606 [details] Patch You're right indeed :)
Committed r103904: <http://trac.webkit.org/changeset/103904>