Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Please bring back WebView 1 in UWP WinUI 3
See original GitHub issueProposal: Temporarily make WebView (1) available in UWP WinUI 3 projects
Summary
Please enable WebView (1) in WinUI 3 UWP projects.
Rationale
Please make the move to WinUI 3 as easy for us as possible. The legacy WebView has a different API than the new WebView2 component. It would be great if we could tackle these migrations not all at the same time.
Marking WebView (1) as [Obsolete] seems like a great way to send a clear message and at the same time make the porting from 2 to 3 easier. (Or some other kind of compiler warning)
Scope
| Capability | Priority |
|---|---|
| API compatible to WebView (1) | Must |
| Clearly marked as obsolete | Should |
| Long term compatibility/support for WebView 1 | Won’t |
Important Notes
The rendering engine used does not matter for this proposal, a shim from WebView 1 to 2 would also work.
Open Questions
Bringing WebView2 to UWP WinUI 2 would also solve this problem, as we can than move to WebView 2 first and WinUI 3 at a later time.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@Marv51 we appreciate your feedback. We understand the migration experience is a challenge. However, given a number of trade-offs and resource constraints we won’t be able to address this. Let us know if you encounter issues while migrating to WebView2 and any issues that come up with that.
@huoyaoyuan It is not.