Skip to content

Add priority-based overflow menu for low-priority PDF toolbar controls #5

Description

@timhaintz

Parent issue

Follow-up to #4 (responsive toolbar and overflow handling).

Problem

The PDF viewer toolbar currently places many controls in a single row. Even with responsive layout work, not every control should remain equally prominent at narrow widths.

A better UX would prioritise the most commonly used controls and move lower-priority controls into an overflow menu when space is constrained.

Proposed solution

Implement a priority-based overflow strategy for the PDF Toolkit toolbar.

Suggested behavior:

  • Keep core controls visible at all times when possible
  • Move lower-priority controls into an overflow menu as width decreases
  • Preserve keyboard accessibility and discoverability
  • Ensure the toolbar remains usable in split editors and narrow panes

Candidate priority tiers

High-priority (prefer to keep visible)

  • previous / next page
  • page indicator / page jump
  • zoom controls
  • screenshot menu
  • extracted menu

Lower-priority (good candidates for overflow)

  • rotate left / right
  • dark mode toggle
  • reset zoom
  • possibly search, depending on final design

Why this matters

This would reduce clutter and preserve the most important actions in constrained layouts instead of forcing users to horizontally scan or scroll through a dense toolbar.

It also gives PDF Toolkit a clearer information hierarchy, which is especially valuable in:

  • narrow editor groups
  • laptop screens
  • side-by-side Copilot workflows
  • demo / presentation settings

Design questions

  • Which controls should always remain visible?
  • Should the overflow be a single menu button or a responsive secondary group?
  • Should search remain inline or move/collapse at specific breakpoints?
  • How should focus order and keyboard navigation behave when controls move into overflow?

Relationship to #4

Issue #4 remains the umbrella issue for responsive toolbar behavior in general.
This issue is specifically about one implementation direction: priority-based overflow for low-priority controls.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions