Open kirsan31 opened 2 years ago
Thanks for the bug report @kirsan31! I've opened it on our backlog.
The note at the end means that it will only fire the event if the runtime being used and updated are the same channel (Canary/Dev/Beta) and using the evergreen version (not Fixed Version).
Description
NewBrowserVersionAvailable
is not firing when new version of runtime installed.Version SDK: 1.0.1072.54 Runtime: 97.0.1072.62 -> 97.0.1072.69 Framework: WinForms OS: Win10
Repro Steps
We have 2 Evergreen Standalone Installers. 97.0.1072.62 and 97.0.1072.69 versions.
Install 97.0.1072.62 and run some sample WinForms app with code like below:
In log you will see:
WebView2 ready, RuntimeVersion 97.0.1072.62.
Install 97.0.1072.69 -Environment_NewBrowserVersionAvailable
will never fire. If we close (deinit) window with WebView2, wait several seconds and open it again, we will seeWebView2 ready, RuntimeVersion 97.0.1072.69.
in log.Also, can some one explain the meaning of this phrase (from docs), it eludes me:
AB#37952354