Dropdown & Context Menu — Learning Bundle
This learning bundle compares menus by how they open. A dropdown opens from a control. A context menu belongs to one object and often opens at the pointer. The bundle is not one standard menu term.
DropdownMenu / ContextMenuA real example
The More button opens general actions. Right-clicking a file opens actions only for that file.
Main parts
- 01Trigger
- 02Anchored or modal surface
- 03Focus boundary
- 04Dismiss path
Use it when
Choose a menu whose trigger and object fit the task. Then build its keyboard behavior.
Do not use it when
Never put form fields or the main site navigation inside a command menu.
Name used in code
DropdownMenu / ContextMenu Before you ship
Check that every member concept has its own name and link. Show all members in the same situation. Give a visible rule for when each one applies and which groups are valid. Never present the bundle as one canonical pattern or as parts that can be swapped freely.
Outcome: Use Dropdown & Context Menu — Learning Bundle to compare its member concepts. Keep their boundaries clear, then decide which members apply and which can work together. User context: The More button opens general actions. Right-clicking a file opens actions only for that file. Learning bundle to unpack: Dropdown & Context Menu — Learning Bundle. Canonical members: Dropdown Menu, Context Menu Why this comparison helps: Choose a menu whose trigger and object fit the task. Then build its keyboard behavior. Do not treat the bundle as one pattern when: Never put form fields or the main site navigation inside a command menu. Comparison requirements: Name every member concept on its own. Explain its job and limits. Show every member in the same real situation. Give a visible sign for when to use, combine, or leave out each member. Decision quality: Keep platform and evidence limits clear. Show which members can work together. Point out false matches, unsafe swaps, and cases that need another concept. Acceptance criteria: A reader can explain each member in one sentence and tell them apart in the example. They can defend the chosen member or valid group and open every canonical guide. Evidence and limits (evidence boundary): This is not a normative standard. Its name, limits, and expected behavior can change from one source to another. Unknowns to confirm: Target platform, decision setting, limits, and evidence needed to use, combine, or leave out members.
Check this request
Review the current use of Dropdown & Context Menu — Learning Bundle. Definition: This learning bundle compares menus by how they open. A dropdown opens from a control. A context menu belongs to one object and often opens at the pointer. The bundle is not one standard menu term. Release checks: Check that every member concept has its own name and link. Show all members in the same situation. Give a visible rule for when each one applies and which groups are valid. Never present the bundle as one canonical pattern or as parts that can be swapped freely. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.