Skip to content

DUPLICATE_BUGS_REPORT.md

Latest commit

 

History

History
114 lines (81 loc) · 5.81 KB

DUPLICATE_BUGS_REPORT.md

File metadata and controls

114 lines (81 loc) · 5.81 KB

Top Duplicate Bugs in WebView2Feedback Repository

Generated: 2025-10-29 00:41:25 UTC

Analysis Period: All duplicate issues tracked in the repository

Executive Summary

This report identifies the bugs that have been reported multiple times in the WebView2Feedback repository. Understanding duplicate bugs helps prioritize fixes and identify pain points affecting multiple users.

Key Findings

  • Total original issues with duplicates: 2
  • Total duplicate reports found: 4
  • Issue with most duplicates: #5144 with 3 duplicates

Top Duplicate Bugs

The following table shows the bugs that have been reported multiple times:

Rank Issue # Title State # Duplicates 👍 Reactions Comments Link
1 #5144 [Problem/Bug]: input field of type text and name email loses focus open 3 14 57 View
2 #3008 COMException 0x8007139F in Microsoft.Web.WebView2.WinForms.WebView2... closed 1 0 91 View

Detailed Analysis

1. Issue #5144: [Problem/Bug]: input field of type text and name email loses focus

  • State: open
  • Created: 2025-03-07T17:10:16Z
  • Labels: bug, tracked, regression
  • Comments: 57
  • Reactions: 👍 14 | ❤️ 0 | 👀 0
  • Number of duplicate reports: 3
  • Duplicate issue numbers: #5150, #5154, #5165
  • Link: #5144

Impact: This is a regression in WebView2 Runtime version 134.0.3124.51 affecting input fields with name='email'. Users report that clicking in such fields causes immediate focus loss, severely impacting form usability. The issue affects Windows 11 and was working in version 133.x. This was patched in version 134.0.3124.68.

2. Issue #3008: COMException 0x8007139F in Microsoft.Web.WebView2.WinForms.WebView2.d__13.MoveNext

  • State: closed
  • Created: 2022-11-29T12:39:23Z
  • Labels: bug, tracked
  • Comments: 91
  • Reactions: 👍 0 | ❤️ 0 | 👀 0
  • Number of duplicate reports: 1
  • Duplicate issue numbers: #5298
  • Link: #3008

Impact: Users encounter COMException (0x8007139F) when initializing WebView2 controls in WinForms, particularly in Excel add-ins. This is a blocking issue affecting basic functionality. The issue is difficult to reproduce in development environments but affects multiple customer deployments. This issue has 91 comments showing extensive investigation and community engagement.

Analysis & Recommendations

Priority Assessment

Based on the duplicate count, reactions, and impact:

  1. Issue #5144 - Input field focus loss (3 duplicates, 14 👍 reactions)

    • Priority: HIGH
    • Reason: Regression affecting user experience, multiple reports, active engagement
    • Status: RESOLVED - Fixed in version 134.0.3124.68 (patch release)
    • Recommendation: Document this in release notes and consider adding regression testing for form input behavior

  2. Issue #3008 - COMException during initialization (1 duplicate, 91 comments)

    • Priority: MEDIUM-HIGH
    • Reason: Blocking issue but harder to reproduce, tracked and closed with continued follow-up
    • Status: CLOSED but still receiving reports (see duplicate #5298 from July 2025)
    • Recommendation: Continue monitoring for patterns and provide better diagnostic guidance

Insights

  • Most duplicates are related to input/autofill regression in runtime version 134.x
  • The autofill/input focus issues were quickly identified and patched (134.0.3124.68)
  • Issues span multiple frameworks (WinForms, WPF, Win32) and Windows versions
  • Regression issues get more duplicate reports than long-standing bugs
  • Issue #3008 shows that even closed issues continue to receive duplicate reports when users encounter the same problem

Recommendations for Repository Maintainers

  1. Improve issue search discoverability - When users submit new issues, GitHub should suggest similar existing issues
  2. Create template responses for duplicate reports to quickly redirect users to canonical issues
  3. Add prominent notices in release notes about known regressions and their fixes
  4. Implement duplicate detection in issue submission flow to suggest similar issues before submission
  5. Pin critical issues with many duplicates to improve discoverability
  6. Document common error codes like 0x8007139F with troubleshooting steps and references to related issues

Methodology

This analysis was conducted by:

  1. Searching for all closed issues with state_reason: duplicate in the repository
  2. Analyzing comments to identify the original issue each duplicate references
  3. Collecting detailed information about each original issue
  4. Ranking issues by number of duplicates, reactions, and community engagement

Data Collection Date

  • Analysis performed: 2025-10-29
  • Total issues scanned: 6 duplicate issues identified
  • Time period: All-time (repository inception to present)

Future Enhancements

To get more comprehensive data, consider:

  • Analyzing issues over longer time periods with pagination
  • Checking for duplicates that weren't formally marked as such
  • Analyzing issue text similarity to find potential unmarked duplicates
  • Tracking which WebView2 versions have the most duplicate bug reports
  • Monitoring duplicate patterns to identify systemic quality issues