RichTextEditor Exception on Windows when using default Edge browser (Milestone 3.2)

[pazi146]

Using Edge causes an uncaught exception when using RichTextEditor. Editor is usable and otherwise unaffected.

Using: Nebula All Mature Widgets SDK 3.2.0.202503211629 (from updates/milestone/latest)

Temporary fix: use VM argument: -Dorg.eclipse.swt.browser.DefaultType=IE

Stack Trace:
!MESSAGE Unhandled event loop exception !STACK 0 org.eclipse.swt.SWTException: Waiting for Edge operation to terminate timed out at org.eclipse.swt.browser.Edge.createTimeOutException(Edge.java:525) at org.eclipse.swt.browser.Edge.processOSMessagesUntil(Edge.java:520) at org.eclipse.swt.browser.Edge.callAndWait(Edge.java:287) at org.eclipse.swt.browser.Edge.evaluate(Edge.java:902) at org.eclipse.swt.browser.WebBrowser.evaluate(WebBrowser.java:405) at org.eclipse.swt.browser.Browser.evaluate(Browser.java:665) at org.eclipse.swt.browser.Browser.evaluate(Browser.java:614) at org.eclipse.nebula.widgets.richtext.RichTextEditor$3.completed(RichTextEditor.java:285) at org.eclipse.swt.browser.Edge.lambda$45(Edge.java:1109) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:40) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:132) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4094) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3710) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1151) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1042) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153) at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:668) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:576) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:173) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:178) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:208) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:149) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:115) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:467) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:298) at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103) at java.base/java.lang.reflect.Method.invoke(Method.java:580) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:670) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:607) at org.eclipse.equinox.launcher.Main.run(Main.java:1492) at org.eclipse.equinox.launcher.Main.main(Main.java:1465)

[fipro78]

Issue in SWT, see eclipse-platform/eclipse.platform.swt#1919

[pazi146]

Thank you for the quick answer