etraisnel2
commented
1 year ago SWT's implementation of Edge Browser doesn't support calling evaluate in BrowserFunction and ends up not responding Since most of the custom buttons and action in the richtext editor use evaluate (which executes synchronously some code, opposite of "execute"), lots of functionalities are impacted and the editor is mostly broken . It seems however that the first calls are properly executed (see initEditor, which is executed inside a ProgressListener.complete ). It is listed as a limitation and there are no official workaround for the moment See [https://stackoverflow.com/questions/71129155/why-does-swt-edge-browser-stuck-on-browser-evaluate] [https://bugs.eclipse.org/bugs/show_bug.cgi?id=578017] [https://bugs.eclipse.org/bugs/show_bug.cgi?id=578016] [https://github.com/eclipse-platform/eclipse.platform.swt/issues/339#issuecomment-1225675203]
Since Microsoft announced end of support for Internet Explorer, it was initially planned to use edge as web browser for richtext views However, there are currently bugs in the SWT Edge implementation and it's not possible to use the richtext widgets as we intend to.
In order to overcome this issue, we must force the richtext widgets to use Internet Explorer (on WIndows only), and yet keep the default browser for other components (opening a html file using the internal browser shall use edge)