| commit | a56c5b55c9ec05607ae31a2f3865406d2288980f | [log] [tgz] |
|---|---|---|
| author | Nikita Nemkin <nikita@nemkin.ru> | Sat Feb 19 16:19:04 2022 +0500 |
| committer | Alexander Kurtakov <akurtako@redhat.com> | Thu Mar 17 10:18:41 2022 -0400 |
| tree | b4a219e6ae06006178aafee91e5b936c08d1b764 | |
| parent | c4d47a36c98fb73ce1c4be38df907dc309168c5b [diff] |
Bug 573616 - [GTK] BrowserFunction only work in first browser instance (Part 1) Remove existing BrowserFunction implementation. To provide synchronous BrowserFunction calls from JavaScript to Java, SWT loads a native browser extension and communicates with it via a private D-Bus. Existing implementation assumes a single instance of the browser extension, but newer WebKitGTK versions create a separate process per view, resulting in multiple extension instances. The follow-up patch will provide an alternative BrowserFunction implementation based on the XMLHttpRequest. Change-Id: I74ce4ba944833ef205c409f197c5d22d2cae51fe Reviewed-on: https://git.eclipse.org/r/c/platform/eclipse.platform.swt/+/191031 Reviewed-by: Alexander Kurtakov <akurtako@redhat.com> Tested-by: Alexander Kurtakov <akurtako@redhat.com>
Thanks for your interest in this project.
See the following description for how to contribute a feature or a bug fix to SWT.
Information regarding source code management, builds, coding standards, and more and be found under the following link.
Before your contribution can be accepted by the project, you need to create and electronically sign the Eclipse Foundation Contributor License Agreement (CLA).
Contact the project developers via the project's “dev” list.
This project uses Bugzilla to track ongoing development and issues.
Be sure to search for existing bugs before you create another one. Remember that contributions are always welcome!