-
Notifications
You must be signed in to change notification settings - Fork 54
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
[Problem/Bug]: NavigateToString() fails with large content page that has embedded image (data: src) #4251
Comments
Ugh - I guess I should look at the documentation first. Looks like it is limited to 2mb in size. Is there any reason why this is limited to this size? |
Also it would be nice if this API could throw a better error message that actually says that the page is too large. Not exactly difficult to figure out the length of a string... |
@yildirimcagri-msft do you have any idea about this? |
#1355 btw this is the same issue here as well. |
Do refer to this #1355 for a solution using WebResourceRequested. |
As far as I can tell that doesn't solve either of the problems. There are two problems actually:
I haven't tried to fix NavigateToString() since that has a fairly easy workaround by navigating to file, but the I'm going to open a separate issue because the |
What happened?
I'm generating a simpe page to display output from an OpenAI generated image and using a data:image/png;b64 data stream to display the image. If I dump the HTML page with the embedded image to file and display it in any browser or in the WebView it works fine. However, if I display the same page that doesn't have external dependencies using
NavigateToString()
it fails.Importance
Important. My app's user experience is significantly compromised.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
120.0.2210.77
SDK Version
1.0.2088.41
Framework
WPF
Operating System
Windows 11
OS Version
22631.2861
Repro steps
Something along the lines of this:
Repros in Edge Browser
No
Regression
Don't know
Last working version (if regression)
No response
The text was updated successfully, but these errors were encountered: