Bug 136777

Summary: [WK2][EFL] Drop to use coordinated graphics for EFL WK2
Product: WebKit Reporter: Gyuyoung Kim <gyuyoung.kim>
Component: WebKit EFLAssignee: Gyuyoung Kim <gyuyoung.kim>
Status: RESOLVED WONTFIX    
Severity: Normal CC: Hironori.Fujii, hyuki.kim, jaepark, lucas.de.marchi, mcatanzaro, ossy, yoon
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
WIP none

Description Gyuyoung Kim 2014-09-12 02:17:46 PDT 
As far as I know, no EFL folks agreed to use coordinated graphics. It looks coordinated graphics guys let EFL port to use the coordinated graphics. Nowadays the coordinated graphics has made a lot of issues though, there is no expert on that. So, I would like to drop to use coordinated graphics for EFL port. Patch is coming.
Comment 1 Gyuyoung Kim 2014-09-12 02:24:39 PDT 
Created attachment 238020 [details]
WIP
Comment 2 Csaba Osztrogonác 2015-04-13 04:52:21 PDT 
Do you still want to drop coordinated graphics? 
How else would like to do the UI side compositing?
Comment 3 Gyuyoung Kim 2015-04-13 05:55:15 PDT 
(In reply to comment #2)
> Do you still want to drop coordinated graphics? 
> How else would like to do the UI side compositing?

If coordinated graphics can be maintained, I don't want to drop it. When I filed this bug, the coordinated graphics wasn't managed. If the coordinated graphics looks like to be maintained, I will drop this bug.
Comment 4 KwangHyuk 2015-04-13 06:01:03 PDT 
GyuYoung, do you think that webkit-efl can use ASYNC_SCROLLING ?
Comment 5 Gyuyoung Kim 2015-04-13 06:07:55 PDT 
(In reply to comment #4)
> GyuYoung, do you think that webkit-efl can use ASYNC_SCROLLING ?

Though we have to investigate if we can use it, it seems to me that we may use it  if we drop the coordinated graphics.
Comment 6 Michael Catanzaro 2017-03-11 10:36:48 PST 
Closing this bug because the EFL port has been removed from trunk.

If you feel this bug applies to a different upstream WebKit port and was closed in error, please either update the title and reopen the bug, or leave a comment to request this.