One more thing that hasn't been mentioned yet: we'll need a UI process replacement for WebKitWebPage::send-request. Hopefully this won't slow down HTTP requests too much; I guess there's probably enough IPC involved already that it hopefully won't be significant.

On Wed, Jul 30 2025 at 02:19:45 PM +02:00:00, Carlos Garcia Campos via webkit-dev <[email protected]> wrote:
 > > > Form autofilling

 We’re prototyping some solutions
 using _WKContentWorldConfiguration.allowAutofill and
 .allowElementUserInfo.  Are those solutions generic enough that they
 could be used for your autofill implementations as well?


I'm not sure, I guess people more involved in Epiphany can tell. I
think Epiphany is the only app using this and the implementation is all
in javascript, the only thing needed from the C API is the signal that
notifies when form controls are associated. I think we could move that
notification (didAssociateFormControls) to the UI process and use run
javascript from the web view. The same probably applies to the password
manager that uses willSubmitForm and willSendSubmitEvent.

Sounds good. I'm reasonably confident that this plan will work.

* Console messages: we removed this API but had to bring it back
because users requested it.

Can we just move the API to the UI process?

* Editor: I don't think there's any application using this.

I didn't even know this existed. There are 0 applications using WebKitWebFrame according to Debain codesearch, so it's surely safe to remove.

* User messages: this is used by several applications, we would need to
check how to replace it.

Yes, this will require some work. Shame, because it's itself a newer API. Oh well. I guess we need some way to send messages directly to JavaScript instead.



_______________________________________________
webkit-dev mailing list
[email protected]
https://lists.webkit.org/mailman/listinfo/webkit-dev

Reply via email to