dotnet/winforms

Double-clicking the text in the custom webbrowser component that put into SplitContainer cannot be selected

Open

#2,910 opened on Feb 26, 2020

View on GitHub
 (0 comments) (2 reactions) (0 assignees)C# (922 forks)batch import
:beetle: bughelp wanted

Repository metrics

Stars
 (4,100 stars)
PR merge metrics
 (Avg merge 14d 22h) (56 merged PRs in 30d)

Description

  • .NET Core Version: .Net Core 3.1.200-preview-015002 from 3.1 Release branch + VS2019 with latest core designer

  • Have you experienced this same bug with .NET Framework?: Yes

More Info:

  1. This issue cannot reproduce without SplitContainer.
  2. This issue cannot reproduce on WebBrowser from Winforms control that put into SplitContainer.
  3. This issue cannot reproduce on custom webbrowser component that put into other containers(Panel, TabControl, GroupBox..).

Steps to reproduce:

  1. Open the attached app “Custom_component_WebBrowser_issue.zip” in VS. Custom_component_WebBrowser_issue.zip

  2. Build and run this application.

  3. Double-clicking the text in the custom webbrowser component and observe the behavior.

Actual behavior: Double-clicking the text in the custom webbrowser component that put into SplitContainer cannot be selected.

Expected behavior: Double-clicking the text in the custom webbrowser component that put into SplitContainer should be selected. The behavior should be like below: custom_webbrowser_issue_expected

Contributor guide

Research direction
Investigate the message handling for mouse double click events in the custom WebBrowser control when placed inside a SplitContainer. Check the control's WndProc or override methods to see if the SplitContainer's panel is intercepting or modifying the messages.
Tech stack
csharp
Domain
desktop
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
C#
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60