On Fri, Sep 6, 2019 at 10:00, Carlos Garcia Campos <cgar...@igalia.com>
wrote:
El vie, 06-09-2019 a las 09:07 +1000, Michael Gratton escribió:
When displaying conversations, Geary uses a WebKitWebView per
message.
Isn't it possible to use a single web view?
That used to be the case, but it's not workable in general for a bunch
of reasons, including having CSS from different messages clobber each
other and not being able to use GTK widgets for message chrome.
As such, single processes per WebKitWebView just isn't scalable. Can
shared-secondary-process mode be brought back? If not, is there
anything in place to mitigate this?
For 2.26 you can set the env var WEBKIT_USE_SINGLE_WEB_PROCESS=1. This
is a temporary solution, only available in 2.26, to give apps more
time
to adapt to the multiprocess model.
Yep, the mention of that in the release notes is what made me realise
it had been depreciated. Will get onto it, cheers.
There's another option that might make sense in the case of geary if
using a web view per message is the best option, which is making all
web views in the same conversation related (See
https://webkitgtk.org/reference/webkit2gtk/unstable/WebKitWebView.html#WebKitWebView--related-view
) All related web views will share the same web process.
That's good to know, thanks. Will look into it for the next cycle.
//Mike
--
⊨ Michael Gratton, Percept Wrangler.
⚙ <http://mjog.vee.net/>
_______________________________________________
webkit-gtk mailing list
webkit-gtk@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-gtk
