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

Webview2 not rendering in VSTO when running multiple instances of the same app #655

Closed
tiagoabreu opened this issue Nov 23, 2020 · 2 comments
Labels
bug Something isn't working

Comments

@tiagoabreu
Copy link

Description
We are rendering a Webview2 control in an integrated window in Word. Initially, everything renders correctly, but when opening a new instance of Word (for example, by opening a new document), the integrated window does not render the Webview2 control, despite navigation happening. We tracked the navigation by checking the NavigationCompleted event.

We are using the same environment settings, including UserData folder, between all windows.
If we use a different UserData folder every time, everything renders correctly and the bug cannot be reproduced.

This applies to all Office applications.

Version
SDK: 1.0.664.37
Runtime: Canary 89.0.707.0
Framework: WinForms
OS: Win10

Repro Steps

  1. Open Word with a VSTO add-in that renders an integrated window with an Webview2 control that navigates somewhere
  2. Open another instance of Word with the same window.
  3. Verify that the page does not render in one of the instances

Expected: A page should render in all instances

Screenshots
image

@tiagoabreu tiagoabreu added the bug Something isn't working label Nov 23, 2020
@tiagoabreu
Copy link
Author

Retested today with version 1.0.707.0 of the SDK and instead of showing the control as if it was in design mode, it shows only white. Pressing F12 for example does not open the developer tools, but the Save action of Word.

@champnic
Copy link
Member

champnic commented Dec 3, 2020

Your first issue is probably the same as #622, which we fixed in 1.0.707-prerelease. However, for the second issue you are probably running into #678 (for which we deprecated that release and are putting out a new SDK package soon). You can try the workarounds mentioned in my comment though: #678 (comment)

If that doesn't fix the issue, please let me know and I can reactivate this. Thanks!

@champnic champnic closed this as completed Dec 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants