-
Notifications
You must be signed in to change notification settings - Fork 160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Edge: Operation timed out on evaluate() #1919
Labels
edge
Edge Browser
Comments
Hi colleagues
|
amartya4256
added a commit
to vi-eclipse/eclipse.platform.swt
that referenced
this issue
Apr 1, 2025
This commit cotributes to executing the registered listeners of Edge browser on Browser callbacks in a asynchronous fashion making sure no WebView related task is executed while a WebView callback is already executing making sure there's no deadlock. contributes to eclipse-platform#1771 and eclipse-platform#1919
amartya4256
added a commit
to vi-eclipse/eclipse.platform.swt
that referenced
this issue
Apr 1, 2025
This commit cotributes to executing the registered listeners of Edge browser on Browser callbacks in a asynchronous fashion making sure no WebView related task is executed while a WebView callback is already executing making sure there's no deadlock. contributes to eclipse-platform#1771 and eclipse-platform#1919
amartya4256
added a commit
to vi-eclipse/eclipse.platform.swt
that referenced
this issue
Apr 2, 2025
This commit cotributes to executing the registered listeners of Edge browser on Browser callbacks in a asynchronous fashion making sure no WebView related task is executed while a WebView callback is already executing making sure there's no deadlock. contributes to eclipse-platform#1771 and eclipse-platform#1919
fedejeanne
pushed a commit
to vi-eclipse/eclipse.platform.swt
that referenced
this issue
Apr 3, 2025
This commit cotributes to executing the registered listeners of Edge browser on Browser callbacks in a asynchronous fashion making sure no WebView related task is executed while a WebView callback is already executing making sure there's no deadlock. contributes to eclipse-platform#1771 and eclipse-platform#1919
fedejeanne
pushed a commit
to vi-eclipse/eclipse.platform.swt
that referenced
this issue
Apr 3, 2025
This commit cotributes to executing the registered listeners of Edge browser on Browser callbacks in a asynchronous fashion making sure no WebView related task is executed while a WebView callback is already executing making sure there's no deadlock. contributes to eclipse-platform#1771 and eclipse-platform#1919
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I started an application that contains a
RichTextEditor
and get an error on startup:Might be a duplicate of #1771
To Reproduce
org.eclipse.nebula.widgets.richtext.example
org.eclipse.nebula.widgets.richtext.example.RichTextEditorExample
main
methodNote:
You first need to locally fix
org.eclipse.nebula.widgets.richtext.RichTextEditor#setBounds(int, int, int , int)
and replace line 757 withThe call stack in SWT Control was changed which now leads to a StackOverflowError as reported in EclipseNebula/nebula#631. While trying to fix this, I came across this issue. I need to find a way to verify if the fix works before I actually can push it.
Expected behavior
A shell should open and show the RichTextEditor.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment:
Additional OS info (e.g. OS version, Linux Desktop, etc)
JRE/JDK version
Version since
Eclipse or SWT version since when the behavior is seen [e.g. 4.23]
Workaround (or) Additional context
Add any other context about the problem here.
Any known workarounds for the problem?
The text was updated successfully, but these errors were encountered: