You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Version 1.0.2592.51 breaks my code, I am stuck at 1.0.2535.41. My program is an email client that loads quill.js in order to allow the user to edit html. I have an html file that I navigate to that loads quill but with the latest webview2 the page no longer loads.
Importance
Blocking. My app's basic functions are not working due to this issue.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
No response
SDK Version
1.0.2592.51
Framework
WPF
Operating System
Windows 10, Windows 11
OS Version
22631.3880
Repro steps
get quill.js and drop the included html file in the same folder as the quill files like quill.core.js.
The available answers to the Regression question don't make any sense to me.
I get a blank page, no exceptions just an empty browser. It is using 'file://' to navigate to a file. Same file loads with previous version of webview2. Same file loads with Edge no problem.
What happened?
Version 1.0.2592.51 breaks my code, I am stuck at 1.0.2535.41. My program is an email client that loads quill.js in order to allow the user to edit html. I have an html file that I navigate to that loads quill but with the latest webview2 the page no longer loads.
Importance
Blocking. My app's basic functions are not working due to this issue.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
No response
SDK Version
1.0.2592.51
Framework
WPF
Operating System
Windows 10, Windows 11
OS Version
22631.3880
Repro steps
get quill.js and drop the included html file in the same folder as the quill files like quill.core.js.
The available answers to the Regression question don't make any sense to me.
quill.zip
page attached.
Repros in Edge Browser
No, issue does not reproduce in the corresponding Edge version
Regression
Don't know
Last working version (if regression)
1.0.2535.41
The text was updated successfully, but these errors were encountered: