If a new page has to be created through the UI client in regard to a message sent by the WebChromeClient, and that new page does not need to be scriptable from the current one than the client (i.e. the browser application) may wants to create a new context for that page. An example of that situation is when the user clicks on the "open link in new window" context menu item (and the new page's domain is different from the current one). This possibility could make the (non-shared) secondary process model more useful.
Created attachment 80926 [details] Patch
Attachment 80926 [details] did not pass style-queue: Failed to run "['Tools/Scripts/check-webkit-style', '--diff-files', u'Source/WebKit2/ChangeLog', u'Source/WebKit..." exit_code: 1 Source/WebKit2/UIProcess/API/qt/ClientImpl.h:48: The parameter name "page" adds no information, so it should be removed. [readability/parameter_name] [5] Source/WebKit2/UIProcess/API/qt/ClientImpl.h:48: The parameter name "modifiers" adds no information, so it should be removed. [readability/parameter_name] [5] Source/WebKit2/UIProcess/API/qt/ClientImpl.h:48: The parameter name "mouseButton" adds no information, so it should be removed. [readability/parameter_name] [5] Total errors found: 3 in 13 files If any of these errors are false positives, please file a bug against check-webkit-style.
Comment on attachment 80926 [details] Patch We are not ready to support the multiple process model at this time. Right now we only want WebKit2 to support a single process for all the pages running in a single context. We will be adding support for multiple processes at some point in the future.
Marking this as WONTFIX for now, as this is not the approach we will be taking for multiple processes when the time comes.
Attachment 80926 [details] did not build on win: Build output: http://queues.webkit.org/results/7685940