tree 812d54eb2ae5c231097e8633c3d9cbfbe04f1153
parent a56c5b55c9ec05607ae31a2f3865406d2288980f
author Nikita Nemkin <nikita@nemkin.ru> 1645286890 +0500
committer Alexander Kurtakov <akurtako@redhat.com> 1647526721 -0400

Bug 573616 - [GTK] BrowserFunction only work in first browser instance (Part 2)

Implement BrowserFunction calls with synchronous XMLHttpRequests
to a custom protocol handler.

SWT registers a custom protocol handler (swt://) and BrowserFunction
calls from JavaScript to Java are performed by issuing HTTP requests
using this protocol. The function to call and its arguments are JSON
encoded in the request URI. Function return value is JSON encoded
in the response body.

JSON codec created for the Edge integration on Windows is reused.

For early and reliable JavaScript injection after page navigation
and reload, BrowserFunction scripts are registered with the user
content manager API. This prevents race conditions compared to using
execute() from the LocationListener.changing or ProgressListener.completed.

An automated test (test_BrowserFunction_multiprocess) is included
to verify correct BrowserFunction operation across multiple Browser
instances and page reloads.

Change-Id: I33f97ee5710b561b4c3a71e1567ae21814ac43ee
Reviewed-on: https://git.eclipse.org/r/c/platform/eclipse.platform.swt/+/191032
Tested-by: Alexander Kurtakov <akurtako@redhat.com>
Reviewed-by: Alexander Kurtakov <akurtako@redhat.com>