Bug 215880
Summary: | [GTK] `webkit_web_extension_send_message_to_context` et al. abusing async semantics | ||
---|---|---|---|
Product: | WebKit | Reporter: | Michael Gratton <mike> |
Component: | WebKitGTK | Assignee: | Nobody <webkit-unassigned> |
Status: | NEW | ||
Severity: | Normal | CC: | bugs-noreply, cgarcia |
Priority: | P3 | Keywords: | Gtk |
Version: | WebKit Nightly Build | ||
Hardware: | PC | ||
OS: | Linux |
Michael Gratton
The docs for the calls `webkit_web_extension_send_message_to_context` and `webkit_web_view_send_message_to_page` state:
> If you don't expect any reply, or you simply want to ignore it, you can pass NULL as callback.
This is probably convenient for people programming in C, but for people programming using vala or language bindings that provide high-level constructs to handle async calls, this is impossible to do. In these cases WebKitGTK will either always emit a "Message foo was not handled" warning, or to silence the warning must always send a response back, even when not required, increasing latency.
Can the warning be removed, or a proper flag introduced, or something?
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Michael Gratton
Also `webkit_web_page_send_message_to_view`.
Carlos Garcia Campos
hmm, I think we need to add send_with_no_reply for bindings then.
Michael Gratton
That would work, but it would also be convenient to be able to specify either/or with a bool or a flag or something.
`send_full` maybe?