Skip to content
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 configuration to enable F12/browser dev tools #23663

Closed
Eilon opened this issue Jul 17, 2024 · 1 comment
Closed

HybridWebView configuration to enable F12/browser dev tools #23663

Eilon opened this issue Jul 17, 2024 · 1 comment
Labels
area-controls-hybridwebview HybridWebView control s/triaged Issue has been reviewed
Milestone

Comments

@Eilon
Copy link
Member

Eilon commented Jul 17, 2024

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.

@Eilon Eilon added the area-controls-hybridwebview HybridWebView control label Jul 17, 2024
@dotnet-policy-service dotnet-policy-service bot added the s/triaged Issue has been reviewed label Jul 17, 2024
@PureWeen PureWeen added this to the 9.0-preview7 milestone Jul 18, 2024
@Eilon
Copy link
Member Author

Eilon commented Jul 19, 2024

Oops, this is a dupe of my own issue #22305.

@Eilon Eilon closed this as not planned Won't fix, can't repro, duplicate, stale Jul 19, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Aug 19, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-controls-hybridwebview HybridWebView control s/triaged Issue has been reviewed
Projects
None yet
Development

No branches or pull requests

2 participants