Cascader
A Cascader shows choices one level at a time. One choice opens the next matching list.
A real example
A shipping form asks for country, province, and city. Each answer narrows the next list.
Main parts
- 01Trigger
- 02Level columns
- 03Selected path
Use it when
Use it when choices form a stable tree and each level has a clear path.
Do not use it when
Avoid it for short lists, cross-branch search, or labels that need extra context.
Name used in code
tree path + dependent option columns Before you ship
Give each field a label that code can read. Link hints and errors, and keep entered values. Check autofill, keyboard order, validation timing, submit states, failure recovery, zoom, and languages.
Outcome: Use Cascader to solve this user need without losing the current context. User context: A shipping form asks for country, province, and city. Each answer narrows the next list. Recommended pattern: Cascader. Why it fits: Use it when choices form a stable tree and each level has a clear path. Do not use it when: Avoid it for short lists, cross-branch search, or labels that need extra context. Product requirements: Define the default, loading, empty, error, success, and recovery states. Keep user input. Give clear feedback after every action. Accessibility and resilience: Use semantic HTML, full keyboard access, and visible focus. Make the layout work when zoomed and support reduced motion. Follow the project’s current rules. Do not add a new UI library unless the project already uses it. Acceptance criteria: The main task works with keyboard only and at 320px width. Focus and status changes are announced. Check loading, failure, retry, cancel, and reduced-motion paths. 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: Product wording, data source, analytics events, supported devices and languages, and platform limits.
Check this request
Review the current use of Cascader. Definition: A Cascader shows choices one level at a time. One choice opens the next matching list. Release checks: Give each field a label that code can read. Link hints and errors, and keep entered values. Check autofill, keyboard order, validation timing, submit states, failure recovery, zoom, and languages. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.