Since then I’ve had the following in ~/.local/share/evolution/webkit-editor-plugins/body-font.js:
'use strict';
var localhostBodyFontPlugin = {
name : "localhostBodyFontPlugin",
setup : function(doc) {
if (doc.body) {
doc.body.setAttribute("style", "font-family: Calibri,sans-serif; font-size: 11.0pt;")
}
}
};
EvoEditor.RegisterPlugin(localhostBodyFontPlugin);
This has been working fine until Arch had the upgrade from 3.44.4 to 3.46.1 hit its repositories. Now it seems to not get executed and I don’t get an error message or unusual output either.
Any ideas what might have broken my plugin? Thanks!
This is kinda interesting. One of the changes in the 3.46.1 is that there had been enabled sandboxing for the WebKitGTK, which prevents access to the home folder, thus the code doesn’t know the plugin exists.
A workaround is to run evolution with the sandboxing off:
$ WEBKIT_FORCE_SANDBOX=0 evolution
You can also add export WEBKIT_FORCE_SANDBOX=0 into the ~/.bashrc or similar file, but it influences every application, which uses WebKitGTK, not only Evolution, in such case.