Changes to the WebView2 feedback repository

[victorhuangwq]

Hello WebView2 community,

We would like to share some updates and improvements to the WebView2 feedback repository. These changes aim to better allow us to assist the community and improve transparency. We hope that these changes will enhance your experience and make it easier for you to collaborate with us and with each other.

Changes already introduced:

• Use of GitHub forms for feature request and bug reports: We updated the feature request and bug report templates using GitHub forms. GitHub forms help us gather sufficient information upfront to reduce back and forth and allow us to address issues faster. Please use these templates when you want to request a new feature or report a bug in WebView2.
• Moving questions and tips to discussions: We have noticed that some of the issues posted in the repository are questions or tips rather than bug reports or feature requests. To reduce clutter in the issues and to also encourage community interaction, we have decided to move these posts to the discussions section. You can use the discussions to ask questions, share tips, or have general conversations about WebView2. Note that we will still be monitoring the discussions to provide any assistance if needed.
• Introduction of the automatic regression tag: We have added a new label called regression to the repository. This label will be automatically applied to any issue that is marked as a regression (based on title and issue body). This will help us keep track of regressions and address them faster. If you encounter a regression, please make sure to specify the version of WebView2 that introduced the regression and the version that worked correctly before.

Changes upcoming:

• Introduction of the priority-low tag: We will be introducing a new label called priority-low to the repository and apply it to any issue that we consider to be low priority. We prioritize all our tracked items accordingly to make best use of our team’s resources. Some items we triage as lower priority, which means that it is very unlikely that we will work on those items anytime soon. We are adding this label to be transparent and explicit in pointing out the low priority items to the community, so that developers can make development plans around that expectation. Developers can still, however, return to those issues and add justification for us to revisit the prioritization of those issues.
• Introduction of security policy: We will add a new file called SECURITY.md to the repository. This file will contain our security policy and instructions on how to report security issues related to WebView2. We want to have a way for users to report security issues securely to us, so that we can fix them before they become public.

We hope that these changes will improve your experience and satisfaction with WebView2. We appreciate your feedback and support, and we look forward to hearing from you. Please let us know what you think of these changes, and if you have any suggestions for further improvements. You can leave a comment on this discussion post, and we will respond to you accordingly.

Thank you for being part of the WebView2 community! 🙌

The WebView2 team