[Webkit-unassigned] [Bug 97651] [EFL] Make PageClient accessible to both WebKit and WebKit2

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=97651





--- Comment #9 from Regina Chung <heejin.r.chung at samsung.com>  2012-10-15 02:39:04 PST ---
(In reply to comment #7)
> > > > I could not find usage of this value.
> > > Better question (answer in changelog) why is this different code path needed for webkit1? Could it use the same one as webkit2 (fake evas) or is there any advantages to this new approach?
> > 
> > In WebKit2 a GraphicsContext3D is created for Accelerated Compositing(AC), and another for WebGL (if needed). 
> > When creating the evas gl context for WebGL we create it as a shared context with ACs evas gl context, so we can use the evas created for webview for both of them.
> > Thus no need for a fake evas.
> You answered the opposite question. I know you dont need the fake evas, but would it make any difference if you did use it?

Actually that was a typo :( 
I ment WebKit doesn't need the fake evas (But Webkit2 does). Sorry about that.
WebKit HAS to use the evas created for webview when creating a GC3D for AC, otherwise the composited webpage won't get rendered into the webview.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.