A context menu from OpenOffice.org Writer, appearing when the user right-clicks on a page elementGNOME context menu with icons
Acontext menu (also called contextual, shortcut, and pop uporpop-upmenu) is a menu in a graphical user interface (GUI) that appears upon user interaction, such as a right-click mouse operation. A context menu offers a limited set of choices that are available in the current state, or context, of the operating system or application to which the menu belongs. Usually the available choices are actions related to the selected object. From a technical point of view, such a context menu is a graphical control element.
Context menus first appeared in the Smalltalk environment on the Xerox Alto computer, where they were called pop-up menus; they were invented by Dan Ingalls in the mid-1970s.[1][2]
Microsoft Office v3.0 introduced the context menu for copy and paste functionality in 1990. Borland demonstrated extensive use of the context menu in 1991 at the Second Paradox Conference in Phoenix Arizona. Lotus 1-2-3/G for OS/2 v1.0 added additional formatting options in 1991. Borland Quattro Pro for Windows v1.0 introduced the Properties context menu option in 1992.
Context menus are opened via various forms of user interaction that target a region of the GUI that supports context menus. The specific form of user interaction and the means by which a region is targeted vary:
On a computer running Microsoft Windows, macOS, or Unix running the X Window System, clicking the secondary mouse button (usually the right button) opens a context menu for the region that is under the mouse pointer.
For quickness, implementations may additionally support hold-and-release selection, meaning the pointer is held down and dragged, and released at desirable menu entry.
On systems that support one-button mice, context menus are typically opened by pressing and holding the primary mouse button (this works on the icons in the Dock on macOS) or by pressing a keyboard/mouse button combination (e.g. Ctrl-mouse click in Classic Mac OS and macOS). A keyboard alternative for macOS is to enable Mouse keysinUniversal Access. Then, depending on whether a laptop or compact or extended keyboard type is used, the shortcut is Function+Ctrl+5 or Ctrl+5 (numeric keypad) or Function+Ctrl+i (laptop).
On systems with a multi-touch interface such as MacBook or Surface, the context menu can be opened by pressing or tapping with two fingers instead of just one.
Some cameras on smartphones for example recognize a QR code when a picture is taken. Then a pop-up appears if you want to 'open' the QR content. This could be anything like a website or to configure your phone to connect to Wi-Fi. See image.
On some user interfaces, context menu items are accompanied by icons for quicker recognition upon navigation.[3]
Context menus can also have a top row of icons only for quick access to most frequently used options.[4]
Windows mouse click behavior is such that the context menu doesn't open while the mouse button is pressed, but only opens the menu when the button is released, so the user has to click again to select a context menu item. This behavior differs from that of macOS and most free software GUIs.
In Microsoft Windows, pressing the Application key or Shift+F10 opens a context menu for the region that has focus.
Context menus are sometimes hierarchically organized, allowing navigation through different levels of the menu structure. The implementations differ: Microsoft Word was one of the first applications to only show sub-entries of some menu entries after clicking an arrow icon on the context menu, otherwise executing an action associated with the parent entry. This makes it possible to quickly repeat an action with the parameters of the previous execution, and to better separate options from actions.
Context menus have received some criticism from usability analysts when improperly used, as some applications make certain features only available in context menus, which may confuse even experienced users (especially when the context menus can only be activated in a limited area of the application's client window).
Context menus usually open in a fixed position under the pointer, but when the pointer is near a screen edge the menu will be displaced - thus reducing consistency and impeding use of muscle memory. If the context menu is being triggered by keyboard, such as by using Shift + F10, the context menu appears near the focused widget instead of the position of the pointer, to save recognition efforts.
