MicrosoftEdge / MicrosoftEdge/WebView2Feedback
Custom context menu items (Remove / Save As / Inspect)
Open
Nobody has claimed this yet.
bug
doc
tracked
- Dominant language
- PowerShell
- Stars
- 526
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
Example:
if (!m_displayPageUrlContextSubMenuItem)
{
items->RemoveValueAtIndex(0); // Back
itemsCount--;
items->RemoveValueAtIndex(0); // Forward
itemsCount--;
items->RemoveValueAtIndex(5); // Share
itemsCount--;
items->RemoveValueAtIndex(5); // Separator
itemsCount--;
}
Looks like:

Questions:
- Is the default menu always going to be the same? I am concerned about using the literal index positions. If the default menu changes my code then breaks. What is the best approach?
- Save As does nothing in my application. Why?
- Can we change Inspect (which works) to Inspect Element?
- How can we add new functional menu item for View Page Source?
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
The issue names no repository file, test, or implementation entry point. Start by tracing the WebView2 custom context-menu behavior described in the example, then verify the default item identification, Save As behavior, Inspect naming, and View Page Source support; done means each question has a documented, supported answer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop, devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100