RESOLVED LATER 125526
[GTK] Remove non-accelerated compositing drawing path for WebKit2 
https://bugs.webkit.org/show_bug.cgi?id=125526
Summary [GTK] Remove non-accelerated compositing drawing path for WebKit2
Martin Robinson
Reported 2013-12-10 11:47:04 PST
We should consider removing the non-AC drawing path for WebKit2. Even if we resort to rendering the page as a single layer, we probably do not need to maintain two ways of transferring the rendered content.
Attachments
Add attachment proposed patch, testcase, etc.
Martin Robinson
Comment 1 2022-04-19 01:13:05 PDT
I'm going to close this bug for now. I think high-level decisions about AC in the GTK port are being made in other bugs.
Michael Catanzaro
Comment 2 2022-04-19 05:28:58 PDT
I understand this is already done for GTK 4 and WPE, but the non-accelerated path remains for GTK 3. Is this correct?
Martin Robinson
Comment 3 2022-04-19 08:07:08 PDT
Adding Carlos, who may be able to answer this question. In any case, perhaps this bug is obsolete either way.
Carlos Garcia Campos
Comment 4 2022-04-19 22:52:21 PDT
The plan for now is to remove the ondemand mode for GTK4, but I'm not sure we can really remove the non accelerated path, because unfortunately there are still cases in which AC mode doesn't work. We made always mode the default in 2.36 and we got a lot of bug reports of things not working :-(
Michael Catanzaro
Comment 5 2022-04-20 05:22:29 PDT
(In reply to Carlos Garcia Campos from comment #4) > The plan for now is to remove the ondemand mode for GTK4, but I'm not sure > we can really remove the non accelerated path, because unfortunately there > are still cases in which AC mode doesn't work. We made always mode the > default in 2.36 and we got a lot of bug reports of things not working :-( Uh, surprise to me. Please review bug #232516 and comment there....
Note You need to log in before you can comment on or make changes to this bug.