Description
Is your feature request related to a problem? Please describe.
The use of LPWSTR throughout the API for posted messages, URIs, resource locations, and more is fairly anachronistic and requires a lot of unnecessary unicode and ascii character conversions (and allocations) for codebases that either do not require unicode support, or more likely, use utf-8 everywhere. Base win32 APIs also support utf-8 code pages, and integrating WebView2 at the moment is a little awkward due to the string handling convention.
Describe the solution you'd like and alternatives you've considered
As a comparison point, CEF defines the string type based on a preprocessor definition to change between utf8 and utf16. As a pure runtime dependency, it would be great to have extended interfaces with overloads for LPWSTR receiving methods that accept LPSTR instead, ideally without internal encoding overhead.