-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
HybridWebView: Support controlling F12 browser dev tools #22305
Labels
area-controls-hybridwebview
HybridWebView control
s/triaged
Issue has been reviewed
t/enhancement ☀️
New feature or request
Milestone
Comments
Eilon
added
t/enhancement ☀️
New feature or request
area-controls-hybridwebview
HybridWebView control
labels
May 8, 2024
Eilon
added a commit
that referenced
this issue
Oct 1, 2024
…wser dev tools Previously the browser dev tools were always enabled for HybridWebView. Now it's optional. Fixes #22305
Fixed in #25047 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area-controls-hybridwebview
HybridWebView control
s/triaged
Issue has been reviewed
t/enhancement ☀️
New feature or request
In the initial PR for HybridWebView, the F12/browser dev tools are always enabled. This needs to be off by default (because production apps generally need it off), but then there needs to be a way to configure it to be on in debug builds. BlazorWebView has a pattern for this, so we could consider that, or some alternative option.
The text was updated successfully, but these errors were encountered: