Selection History Navigation
A navigation pattern for moving between previously selected items, enabling users to move backward and forward through their Selection History.
Selection History · UX essentials
Essential guidance on effectively using Selection History Navigation.
Windows with no content use empty states
Labels do not end with punctuation
In Inspector-like windows, input controls should have labels and tooltips
Only use link labels for opening external applications
Tooltips are written in clear, complete sentences
All UI elements use the appropriate font
UI uses appropriate font sizes
Padding exists between text and other UI elements
Text is aligned appropriately
Adapt your content layout for various window sizes
The interface should support the set min and max sizes of the window
Overview
Buttons allowing to move backwards or forwards through selection history
Selection History allows users to navigate through their recent selections using back/forward navigation, similar to web browser history. This pattern addresses a common workflow disruption: accidentally losing context when selecting a different object.
Choosing Pattern
Decision Tree
Use this flowchart to determine which pattern applies:
Usage Comparison
Selection History can be implemented at two scopes for various aspects:
The Editor Selection History is the Editor-wide history that tracks any selection affecting the main Inspector window. This is the shared navigation context across the Editor.
- Single, Editor-wide history stack
- Keyboard shortcuts are Ctrl/Cmd + [ or Ctrl/Cmd + ]
- Optional toolbar buttons in the main toolbar
- Records up to 50 selections
- Managed by the core Editor
Local Selection History is window-specific navigation for self-contained editing environments that manage their own selection context independently from the main Inspector.
- Per-window history stack
- Window provides its own back/forward UI (toolbar buttons within the window)
- Does not clutter the global history with internal navigation
- Window manages its own history depth and persistence
Registration with Global Selection History:
- Registration is implicit
- Selection changes as they happen via the Selection.selectionChanged callback, anything that emits this callback is automatically in the Editor selection History
Implement Local Selection History when:
- Your window is a self-contained editing environment
- Selections within your window do NOT affect the main Inspector
- Internal navigation is frequent and would overwhelm global history
- Users need to navigate within your window while maintaining their global selection
Examples of Global selections:
- Selecting a GameObject in Hierarchy or Scene View
- Selecting an Asset in the Project window
- Navigating folders in Project window
Examples of Local selections:
- Browsing documentation or reference panels
- Navigating within a custom asset browser
- Internal state changes in a wizard or multi-step workflow
- Preview navigation in an inspection tool
Choice Examples
User browses folders in Project window
Global Editor History
User navigates pages in a documentation panel
Local History
User steps through a wizard's pages
Local History
User selects an asset in a custom picker that updates Inspector view
Global Editor History
User selects items in a tool that has its own embedded property panel ( or local inspector view)
Local History
Design Guidelines
Layout & Placement
Main toolbar buttons layout
Editor Global Selection History:
- Back/forward buttons are positioned at the right hand side and hidden by default in the main toolbar
- Users can enable them via toolbar options
- Keyboard shortcuts are Ctrl/Cmd + [ or Ctrl/Cmd + ]
Local Selection History:
- Provide back/forward buttons within the window's toolbar as its context affects selection within that window
- Use regular toolbar icon buttons
- Position buttons to right side of the window's toolbar (see toolbar button layout)
- If needed, consider window-scoped shortcuts i (e.g., Alt + Left/Right) and make them available in Shortcuts Manager
- Consider whether history should persist when window is closed/reopened. It should at least clear history when the window's editing target changes fundamentally (e.g., a different data set is loaded)
Do: Disable buttons when at history boundaries
Do: Use common Selection History Navigation button icons (load with EditorGUIUtility.LoadIcon("tab_prev") and EditorGUIUtility.LoadIcon("tab_next")
Don’t: Duplicate consecutive selections of the same item
Don’t: Add selections not initiated by user action
Icon Buttons
Arrow buttons allowing Selection History navigation
Use common Selection History Navigation button icons
tab_prev
Navigate backward (previous selection)
EditorGUIUtility.LoadIcon("tab_prev")
tab_next
Navigate forward (next selection)
EditorGUIUtility.LoadIcon("tab_next")
Tooltips
Provide informative tooltips on history buttons:
Back button
"Previous Selection" and include the item name if useful
Forward button
"Next Selection" and include the item name if useful
Visual Feedback
Showing selection feedback in the Hierarchy, affecting the Inspector view content
- Selection highlight should update in source views (Hierarchy, Project or your local window) when navigating history
- Inspector should update immediately and display current selection normally
- No intrusive animations or notifications needed: the updated selection highlight is sufficient feedback
Copyright © 2026 Unity Technologies
