[Webkit-unassigned] [Bug 245059] Web extensions doesn't work

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Sep 12 11:42:39 PDT 2022


https://bugs.webkit.org/show_bug.cgi?id=245059

--- Comment #3 from Michael Catanzaro <mcatanzaro at gnome.org> ---
(In reply to Ashu Sharma from comment #2)
> The problem I guess is, maybe WebKit can't handle few its extensions or it
> lost signal while the system is busy, Or maybe its a linux kernel process
> bug.

Well it's certainly not impossible. If you can provide a code sample that demonstrates the bug, we could maybe take a look. The simpler the better, of course.

> Anyway, as you said the api maybe go away, is there any other way to access
> to DOM? 

You can use webkit_web_view_run_javascript() in the UI process. It's pretty limiting and definitely not a replacement for WebKitWebExtension, but we don't yet know what else to do. (I was just giving you a heads-up that this will be a problem for you in the future: we don't actually have any replacement functionality available yet.)

> Or I needed to edit Webkit source a patched source of webkit2 for
> direct access to DOM exist?

That sounds pretty difficult. I wouldn't recommend trying that.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20220912/d0e0fa00/attachment.htm>


More information about the webkit-unassigned mailing list