MicrosoftEdge / MicrosoftEdge/WebView2Feedback
Release Notes tabs use misleading platform titles
@victorhuangwq is already working on this.
Since Aug 30, 2023.
- Dominant language
- PowerShell
- Stars
- 526
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
The WebView2 SDK Release Notes page use tabs to allow focusing on one of the three platforms which are currently titled:
- ".NET/C#"
- "WinRT/C#"
- "Win32/C++"
This is misleading because .NET supports not only C#, but also F#, and even C++/CLI. WinRT also does not only support C#, but many other language projections, one of which is standard C++. This is especially misleading since "C++" in turn is listed only for Win32.
I now know about all these things, but for developers who are not familiar with 30 years of Microsoft framework/platform history, this can be confusing, especially with WinRT being a relatively new platform, with its support of standard C++ being quite important, as it is the first platform to do so since MFC (= decades ago). So giving the impression of "You use C#? Look at WinRT. You use C++? Look at Win32." is not great. In my opinion, these tab titles should only name the platforms ".NET", "WinRT", "Win32" themselves without drawing connections to one specific arbitrarily chosen language supported by these platforms.
A while ago, you improved the "WebView2 API Reference" document to be less confusing with regard to WinRT and what's available where. Unfortunately, I just found out, that a change https://github.com/MicrosoftDocs/edge-developer/commit/756a6f42385db165ceb0200e51915434be56e25e#diff-7ec2f86c705953c4359fe7a6ce3b5c9fd5bba5c6f23f47fafdd03671767112ab was made, which does exactly the opposite of what I'm proposing here and I don't know why. This does not make any sense to me.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.