[windows] WebView2 runtime not found #2000
Comments
|
You manually have to install it on some versions of Windows 10. I had to do this on W10 but not W11. See https://developer.microsoft.com/en-gb/microsoft-edge/webview2?form=MA13LH#download |
|
TODO: add download link to error message |
…lipse-platform#2000 When the OS lacks a WebView2 runtime installation, an error is shown once a browser is initialized since Edge is used as the default browser on Windows. This change adds a link to the according FAQ page with information on how to install such a runtime to the error message. Resolves eclipse-platform#2000
…lipse-platform#2000 When the OS lacks a WebView2 runtime installation, an error is shown once a browser is initialized since Edge is used as the default browser on Windows. This change adds a link to the according FAQ page with information on how to install such a runtime to the error message. Resolves eclipse-platform#2000
|
would be terrific to have a kind of fallback to java internal HTML renderer(used in JEditorPane) or so. even if it is outdated and sometimes weird, it lets avoid near-crash errors asking user to terminate the IDE immediately when discovered btw, surpisingly, a near-spamming tab was causing this near-crash failure:
it's extremely bad idea to terminate IDE when near-spamming attempt failed. there definitely must be an option to ENABLE such spontaneous(during 'Deferred early start') browsing attempts from IDE when user wants to, and the behavior must be PROHIBITED by default. and the whole concept: most likely there is a favorite browser user prefers on client machine, so user simply navigates hyperlinks with it never expecting any overclevered software even attempts to duplicate it's functionality(instead of re-using). for many-many reasons there could be no browsers zoo and no Microsoft Edges at all and user may be totally happy - since Eclipse wasn't fail to show lightweight HTML like Javadoc within it's tooltips and opening page of started server(e.g. Tomcat) in default system browser is not a problem for it. so, a simple text message, offering user to navigate some internet link WITH FAVORITE BROWSER is not such troublesome and error-prone and definitely is totally enough - of course, when user WANTS to deal with it at all. |
|
@GooogLeMorons From your post, we have no idea what exactly failed for you. Eclipse relies on browser integration at many places, like Java element information popups, Javadoc, help, welcome page etc.. It's not only about opening a browser to show some web page, for which it might be okay to open some external application. Since you find the overall concept so bad (which is btw the same it has been for years), please propose a better concept, in the best case with a PR demonstrating it. Eclipse has always integrated native browsers. On Linux and MacOS you have WebKit integration. Before using Edge/WebView2, the Internet Explorer engine of Windows was used (and actually you may still use it to get rid of your problems at least as long as it's still available on Windows: https://eclipse.dev/eclipse/news/news.html?file=4.35/platform.html#edgeBrowserDefault). But be aware that Internet Explorer will still be installed in your system and Eclipse will still not use your favorite browser for showing the above mentioned elements (like it did for all the time you are using it), as it does not use the OS default browser. Or did you really have no native engine like WebView2 or Internet Explorer installed so that some elements (like Java element information) use a fallback mechanism to show simple test rendering of HTML? I am only aware of that for specific elements but not for the browser widget in general, but I don't think that there are people who really want to use Eclipse in that way anyway. |
|
well, they say at https://eclipse.dev/eclipse/news/news.html?file=4.35/platform.html#edgeBrowserDefault that Welcome page is using Edge WebView2 now. such a great example the "the same concept it has been for years" works really good, being designed and implemented in good faith! This is the key concept i expect - failure-proof. moreover, some years ago - when it was functional - i've disabled Welcome screen somehow(probably, with an option on it), don't see it any more and don't suffer. This is an optional, but very appreciated concept i expect - capability to isolate or disable a (non-functional) feature. in addition, if i could uninstall Welcome screen, i probably would do it, forget it and focus on the task Eclipse itself is great at: developing code. This is the ideal concept i would love - modularity. so, applying this to "Eclipse IDE for Enterprise Java and Web Developers 2025-06 M1" tab:
as a user, i really hate when a software pretends to know better, what to show me and what to do: open "What's new" in browser, go to some internet location and display stuff appeared there, downloading something and self-updating, etc. when being never asked for it. i believe it must fulfill direct user requests, without any amateur activities: when such activities fail and crash, it looks really unprofessional, really ugly. there can be different points of view: which activities are acceptable, which are appropriate and which are not. but user-friendly capability to turn them on or off is a must. |
|
@GooogLeMorons: Does your Windows username by any chance contain space or special characters? The behavior that things suddenly open in an external browser instead of internally is a known/fixed issue: Let's keep discussions on this issue focused on error handling in case that WebView2 is not installed. |
no, but path is not default: 'd:\IoT.Users\Meow'
tried and got blank tab in default browser again. not sure i did everything properly:
... -> Install version 'Stagging(2025-06)' ->
... Cancel -> Check for updates -> Update -> Restart IDE ->
not sure i'm on build I20250423-0800 after update. is it OK or i did something wrong? |
|
thanks
blank tab in default browser again. where to look, where to dig? |
…form#2000 When using WebView2 as browser engine in SWT without a WebView2 runtime being available on the system, browser initialization fails. In order to more gracefully handle the case that a system has no such runtime installed (like on some Windows 10 systems), this change introduces an automatic fallback to Internet Explorer in case no WebView2 runtime is found. In addition, it shows an error dialog informing about the missing runtime and showing a link to FAQ about it. Fixes eclipse-platform#2000
Describe the bug
When launching Eclipse IDE for Java Developers 2025-03 for the first time an error
happens.
To Reproduce
Start Eclipse for Java Developer 2025-03 on a fresh workspace.
Wait for background procedures to complete.
Expected behavior
No errors.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment:
Additional OS info (e.g. OS version, Linux Desktop, etc)
Windows Server 2019 Datacenter
Version 10.0.17763 Build 17763
JRE/JDK version
java.vendor=Eclipse Adoptium
java.vendor.url=https://adoptium.net/
java.vendor.url.bug=https://github.com/adoptium/adoptium-support/issues
java.vendor.version=Temurin-21.0.6+7
java.version=21.0.6
Version since
org.eclipse.e4.ui.css.swt (0.15.500.v20241219-0802) "Eclipse CSS SWT Support" [Active]
org.eclipse.e4.ui.css.swt.theme (0.14.500.v20250213-1508) "Eclipse CSS SWT Theme Support" [Active]
org.eclipse.e4.ui.swt.win32 (1.2.300.v20240416-0658) "Eclipse UI WIN32 Enhancements" [Resolved]
org.eclipse.e4.ui.workbench.addons.swt (1.5.600.v20241107-2150) "Eclipse e4 Workbench Add-ons" [Active]
org.eclipse.e4.ui.workbench.renderers.swt (0.16.700.v20250212-1224) "Eclipse e4 Workbench SWT Renderer" [Active]
org.eclipse.e4.ui.workbench.swt (0.17.700.v20250123-0706) "Eclipse e4 Workbench SWT" [Active]
org.eclipse.jface.databinding (1.15.300.v20240424-0444) "JFace Data Binding for SWT and JFace" [Resolved]
org.eclipse.swt (3.129.0.v20250221-1734) "Standard Widget Toolkit" [Resolved]
org.eclipse.swt.win32.win32.x86_64 (3.129.0.v20250221-1734) "Standard Widget Toolkit for Windows on x86_64" [Resolved]
Workaround (or) Additional context
None
The text was updated successfully, but these errors were encountered: