Test finalized webview context menu api

[mjbvz]

Test for #54285

• AnyOS @chrmarti

Complexity: 5

Create Issue

Create Issue

---

Summary

#54285 introduces a new contribution point for context menus on webviews. This contribution point has been tested before, so for this test plan item, you just need to make sure the finalized API works without enabling any api proposals.

Here's a refresher on the API itself:

"webview/context": [
	{
		"command": "gitlens.showSettingsPage",
		"when": "webviewId == 'gitlens.welcome'"
	}
],

The contents of the webview can change the when clauses by setting data-vscode-context with json values of the new context. For example, if I right click inside of nav with the following html:

<div class="menu" data-vscode-context='{"webviewSection": "menu", "countOfThing": 123}'>
    ...
    <div class="nav" data-vscode-context='{"webviewSection": "nav", "preventDefaultContextMenuItems": true}'>
        ...
    </div>
</div>

The set contexts would be:

• webviewSection = "nav" (overrides the value from the . menu element)
• countOfThing = 123 (inherited from the parent .menu element)
• preventDefaultContextMenuItems = true

The preventDefaultContextMenuItems context should prevent the default context menu items from showing up (copy, paste, ...)

Testing

Using the webview extension sample, try testing:

2. You can register webview context menu items and use webview == 'catCoding' to register a new menu. For example:

   "contributes": {
   	"menus": {
   		"webview/context": [
   			{
   				"command": "catCoding.doRefactor",
   				"when": "webview == 'catCoding'"
   			}
   		]
   	},

3. Your html can suppress the default context menu items using preventDefaultContextMenuItems with data-vscode-context (see above)

4. Your html can set custom context using data-vscode-context

5. Any set contexts should override contexts set by parent element (the above example shows this for webviewSection)