Delay the Wayland initialization in the WebProcess for WRT. 18/9018/2
authorJoone Hur <joone.hur@intel.com>
Fri, 30 Aug 2013 21:10:56 +0000 (14:10 -0700)
committerJoone Hur <joone.hur@intel.com>
Tue, 3 Sep 2013 18:11:26 +0000 (11:11 -0700)
commita19b13646d901f3c6d956c36fa152660ab4a6e61
tree25b8d8c1ca4a19d760d1cd3ea3700ac3cfb818e2
parent295ff31c39e4d4e5e40c7af56819321200b6b02d
Delay the Wayland initialization in the WebProcess for WRT.

Wayland initialization should be done in the UIProcess before the WebProcess
starts to do this, but in case of WRT, the WebProcess does this ahead of the UIProcess.
So, we have to initialize the PlatformSurfacePoolTizen in WebProcess::createWebPage,
not WebProcess::initialize because it is triggered by the createWebPage message sent
from the UIProcess, which delays the Wayland initialization in the WebProcess.

This patch fixes the bug below:
WebGL context creation hangs when called from a web app
https://bugs.tizen.org/jira/browse/TIVI-1602

Change-Id: I8c886e9693ec2b398db0700e8de48401999ced52
Source/WebCore/platform/graphics/surfaces/wayland/WaylandDisplay.cpp
Source/WebCore/platform/graphics/surfaces/wayland/WaylandDisplay.h
Source/WebKit2/Shared/WebPageCreationParameters.cpp
Source/WebKit2/Shared/WebPageCreationParameters.h
Source/WebKit2/UIProcess/WebPageProxy.cpp
Source/WebKit2/WebProcess/WebProcess.cpp