MicrosoftEdge / MicrosoftEdge/WebView2Feedback
BringToFront Has No Effect on Winforms
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 526
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
As title, on 1.0.865.0 BringToFront() has no effect with respect to other WebView2 on the same control, only way to make is to make WebView2 visible/invisible.
Which is sort of OK, but can be a delay on the reflow of the WebView2 being made visible.
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.
Research direction
Start by reproducing the BringToFront behavior on WebView2 version 1.0.865.0 with multiple WebView2 controls on the same WinForms control. Done means BringToFront changes the relative order without requiring a visibility toggle or causing the reported reflow delay; the linked AB#33093067 work item may provide additional context.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100