TYPO3 Core

In DefaultConfiguration.php the following settings are defined:

options.contextMenu {
  table {
    pages {
      disableItems =
      tree.disableItems =
    }
    sys_file {
      disableItems =
      tree.disableItems =
    }
    sys_filemounts {
      disableItems =
      tree.disableItems =
    }
  }
}

https://github.com/TYPO3/typo3/blob/12.4/typo3/sysext/core/Configuration/DefaultConfiguration.php#L1340-L1355

If you find bugs in documentation, please open an issue in the according repository. The repository is linked on the bottom of each page.

Digging into it: The documentation described this:

"The full path of this property is: contextMenu.table.[tableName][.context].disableItems"

and

"Optional key "[.context]" refers to the place from which the context menu is triggered. The core uses just one context called tree for context menus triggered from page tree and folder tree. This way you can disable certain options for one context, but keep them for another."

And the examples:

# Remove "New" and "Create New wizard" for pages context menu (list module)
options.contextMenu.table.pages.disableItems = new,newWizard

# Remove "New" and "Create New wizard" in page tree context menu
options.contextMenu.table.pages.tree.disableItems = new,newWizard

So, there are two cases, as far as I can see. In the tree and outside the tree.

If the ".context" option describes the context from which the context menu is invoked, why isn't there a ".list" context? In tsconfig we often have options where it is possible to define something for all (e.g. contexts) and override it for special (context). Here you have to define it for each context separately. Fine. You can close this issue: it's not a bug.

I can't answer you the question, maybe historical reasons and backward compatibility.