125526 2013-12-10 11:47:04 -0800 [GTK] Remove non-accelerated compositing drawing path for WebKit2 2022-04-20 05:22:29 -0700 1 1 1 Unclassified WebKit WebKitGTK 528+ (Nightly build) Unspecified Unspecified RESOLVED LATER https://bugs.webkit.org/show_bug.cgi?id=232516 P2 Normal --- 1 mrobinson webkit-unassigned alex bugs-noreply cgarcia mcatanzaro oldest_to_newest 958441 0 mrobinson 2013-12-10 11:47:04 -0800 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. 1862462 1 mrobinson 2022-04-19 01:13:05 -0700 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. 1862504 2 mcatanzaro 2022-04-19 05:28:58 -0700 I understand this is already done for GTK 4 and WPE, but the non-accelerated path remains for GTK 3. Is this correct? 1862549 3 mrobinson 2022-04-19 08:07:08 -0700 Adding Carlos, who may be able to answer this question. In any case, perhaps this bug is obsolete either way. 1862830 4 cgarcia 2022-04-19 22:52:21 -0700 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 :-( 1862895 5 mcatanzaro 2022-04-20 05:22:29 -0700 (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....