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

Enable support for browser extensions #featurerequest #81

Closed
paj777 opened this issue Nov 25, 2019 · 13 comments
Closed

Enable support for browser extensions #featurerequest #81

paj777 opened this issue Nov 25, 2019 · 13 comments
Labels
feature request feature request

Comments

@paj777
Copy link

paj777 commented Nov 25, 2019

We have the need for using different zoom levels in different browser instances pointing at the same domain. Will there be browser extension support so that it would be possible to implement this?

@paj777 paj777 changed the title Enable support for browser extensions feature request Enable support for browser extensions #feature request Nov 25, 2019
@paj777 paj777 changed the title Enable support for browser extensions #feature request Enable support for browser extensions #featurerequest Nov 25, 2019
@david-risney
Copy link
Contributor

Hi @paj777, thanks for your feedback! This sounds like two different feature requests:

  1. Control the zoom of a WebView independent of the origin
  2. Host may provide browser extensions

For (2) host provided browser extensions, do you have other use cases for browser extensions or if we implemented a mechanism to control the zoom of a webview and didn't implement host browser extensions would that solve your problem?

Host provided browser extensions would certainly open up a lot of possibilities although it may end up being a lot more work than enabling origin independent zoom.

@david-risney david-risney added the feature request feature request label Nov 25, 2019
@paj777
Copy link
Author

paj777 commented Nov 26, 2019

Hi @david-risney thank you for your response.

Yes, breaking this up into two separate feature requests makes sense. The reason my suggestion included extensions is because this is the only solution that Chrome provides for this zoom issue. If the independent zoom can be tackled without the need for browser extensions then that would be great.

As you said, providing browser extensions would open up possibilities but may not be necessary for this issue.

@douglas-jordan
Copy link

+1 for extensions

@douglas-jordan
Copy link

douglas-jordan commented Feb 7, 2020

I just ran into this problem today, zoom is not independent of origin. I have more than one WebView2 showing different pages on the same domain and any zoom change sets all the views to the same.

I verified the same behavior in the browser with multiple tabs.

Would like to have independent zoom on each render.

@douglas-jordan
Copy link

douglas-jordan commented Feb 25, 2020

I have tested Canary 82.0.435.0 and zoom is independent of origin. Does not appear to be in the release notes for the updated SDK.

@priprii
Copy link

priprii commented Mar 19, 2020

I would also like to see support for extensions for element blocking with uBlock Origin which makes use of webRequest.

The WebResourceRequested event in Webview2 does not seem to fire for resources being loaded in iframes so I'm unable to block those specific resources from loading by sending 403 response.

In other browsers like Chrome & Firefox, resources in iframes can be blocked with uBlock Origin extension.

So I'm either looking for support for extensions to make use of webRequest, or to have WebResourceRequested support resources in iframes.

@Adjective-Object
Copy link

Adjective-Object commented Jun 5, 2020

I'm working on a react app hosted in an edge webview and not having access to React Devtools is pretty painful. I unfortunately can't develop in a full-fledged browser, since we're passing messages to the host process for some required native integrations.

@champnic
Copy link
Member

Closing this as it's an amalgamation of issues tracked elsewhere or fixed.

@CoastalData
Copy link

I have another use-case scenario for extension in webview2... I'm making some Line of Business desktop applications that use webview embedded to show a couple of websites that require login, and so I'd like to have access to 1Password in the app to store and fill passwords by the user.

Like others, this is something that would be baked into the app, we're not looking to let users add extensions.

@EnigmaV8
Copy link

EnigmaV8 commented Oct 13, 2022

I have another use-case scenario for extension in webview2... I'm making some Line of Business desktop applications that use webview embedded to show a couple of websites that require login, and so I'd like to have access to 1Password in the app to store and fill passwords by the user.

Like others, this is something that would be baked into the app, we're not looking to let users add extensions.

We have the exact same enterprise scenario except LastPass is our password filler. We have some older internal web apps running on WebView2 that still use Basic Auth. Sure would be nice if our LastPass extension could be utilized instead of requiring wasted time of additional authentication. (use to work when run under Internet Explorer because they could simply save the credential natively)

@jle-pass
Copy link

+1000

@champnic
Copy link
Member

@jle-pass
Copy link

Hi and thank you, but how do this in an existing app (like Microsoft Office365 app), as requested in #4873 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request feature request
Projects
None yet
Development

No branches or pull requests

9 participants