-
Notifications
You must be signed in to change notification settings - Fork 51
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
[Feature]: Allow the option of not to adding Window.gc #4378
Comments
Could you let us know which sites you are trying to access? |
@lflores-ms I'm wondering this might be something relevant to the UA work that you are working on |
I'm very sorry. I just checked, and I'm not getting blocked now. If/when it happens again, I'll let you know. I'd like to keep this request open for the time being, however. |
okay! sounds good. In the meantime, I will close this feature request. |
Describe the feature/enhancement you need
I would like the option to not have WebView2 add Window.gc. As stated by Manuel Caballero in https://stackoverflow.com/questions/72147601/detecting-webview2-vs-standalone-edge-browser, the presence of Window.gc allows a website to easily distinguish whether it is being accessed by Edge or WebView2.
The scenario/use case where you would use this feature
My WebView2 is being blocked by some sites that I can access with Edge. Therefore, I really need to be able to not have WebView2 create the Window.gc (and anything else which would not be present in Edge) which I believe is preventing access to these sites.
I use other options, including those described in https://github.com/MicrosoftEdge/WebView2Feedback/issues/3678 to deal with the memory leak in WebView2 without using the garbage collector.
How important is this request to you?
Critical. My app's basic functions wouldn't work without it.
Suggested implementation
No response
What does your app do? Is there a pending deadline for this request?
The app lets the user access a web page and download data from it. I hate to create false deadlines, but I haven't been able to figure out a work-around, so my app has limited functionality until this is implemented.
The text was updated successfully, but these errors were encountered: