On Sun, Apr 20, 2025 at 04:44:32PM +0200, Quentin Rameau wrote:
> Hey Artyom,
>
> > What does it do exactly? I couldn't find a precise description,
> >
> > https://webkitgtk.org/reference/webkit2gtk/2.36.5/WebKitSettings.html#WebKitSettings--enable-javascript-markup
>
> I had kind of the same question, but rather if you have more details
> about the execution limit/domain between both.
>
> My naive understanding is that the JavaScript engine is still active,
> as it is for the webext context.
> What this does would be to not execute remote JS code, only internal.
>
> I think that's fine, as this was kind of happening before anyway,
> and if we can remove that IPC between main and ext through
> ugly glib, the better.
>
> Two remarks (regarding the patchset):
>
> - If we're going to have scrolling in main, let's remove the webext
> entirely as it wouldn't be of use anymore (we can reintroduce it later
> if needed).
> That would mean altering the Makefile too, I could do it if you want.
>
> - Maybe it's not really useful to disable JavaScript (the original one)
> entirely as it's needed for the core feature of being able to scroll.
> Instead, we could substitute it for JavaScriptMarkup directly.
>
> What do you (all) think?
>
OK sounds good to add this option to me then.
--
Kind regards,
Hiltjo
Received on Sun Apr 20 2025 - 16:47:36 CEST