Ditch WebView2 in Widgets panel and use native WinUI #3586
Replies: 4 comments
-
The widget panel is a joke. It's not even as helpful as widgets on iOS, despite Microsoft having live tiles 12 years ago, and only exists to push MSN content and other web based services. I strongly recommend bringing back live tiles and adding interactivity to it, rather than make something completely new. |
Beta Was this translation helpful? Give feedback.
-
Maybe live tile content can be brought out of a "tile" and be displayed as a "widget-like" experience, but something similar to tiles? Like this image: It can have all the same traditional live tile functionality but as you mentioned it can have the interactivity that widgets have now. And of course the native WinUI experience powers it. |
Beta Was this translation helpful? Give feedback.
-
I would also prefer the tiles/widgets be always on the desktop and shown on sign-in, instead of a separate flyout. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the bug
The widgets board currently uses Edge's WebView2 to render content and host widget content. This should be dropped and instead a native WinUI 2/3 based interface should be used. Using WebView2 is essentially running a web browser in the background constantly and this results in (more than) a few problems:
Even something as simple as toggling the full screen widgets panel makes the entire UI freeze and flash multiple times while displaying no content for about 5 seconds before it slowly loads in.
Even this repository states that "WinUI is the native UI layer for Windows that embodies Fluent Design and delivers modern, performant, and polished user experiences..." so using WinUI for a native windows component is a no brainer.
The same could be said for other windows components as well, such as the search box experience. While it does not use WebView2, it is still a web-based experience that has the same problems listed above; WinUI would fix it too.
Steps to reproduce the bug
Expected behavior
Native XAML/WinUI based Widgets board that works smoothly and has a consistent theming with other windows components.
Screenshots
No response
NuGet package version
None
Packaging type
Packaged (MSIX), Unpackaged
Windows version
Insider Build (xxxxx), Windows 11 version 22H2 (22621, 2022 Update), Windows 11 version 21H2 (22000)
IDE
Visual Studio 2022-preview, Visual Studio 2022, Visual Studio 2019, Other
Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions