← Back to Catalog

Footer buttons when body cannot carry

footer-buttons-when-body-cannot-carry

Footer buttons when the body can't carry them — collapsed/hidden content (not one screen), or complex body with subgroup actions so Complete is not confused with local actions. Footer = separation from body.

Description

Footer buttons separate page-level Complete from body content when the body cannot carry them—collapsed or multi-screen content, or complex bodies with subgroup actions. Leaving Complete among local subgroup actions confuses page commit with local tools and invites the wrong click. Use the footer for clear separation from the body. A simple single-screen body may keep its action in-flow when no confusion with subgroup actions arises.

When to use

Collapsed or complex page bodies where Complete would mix with local actions.

Not when

Simple one-screen bodies that can host the page action clearly.

Agent hint

Put Complete in the footer when body content or subgroup actions would confuse it.

Pass

Complete/footer actions sit in the footer when content is collapsed/not one screen, or when a complex body has subgroup actions.

Fail

Complete sits among local subgroup actions so it is confused with them, on a body that cannot carry the page action.

Citations

Ant Design — Button spec

https://ant.design/docs/spec/buttons

Open UX · cited UX rules agents audit against

Privacy · Sources ·