Skip to content

Keep the Python docs search overlay within the viewport #16

Description

@rmcdaniel

Problem

Opening search on https://python.durable-workflow.com/ expands the document far beyond the viewport. At 768 px the rendered document is 2240 px wide; at 390 px it is 1262 px wide. The visible overlay appears fitted, but the page remains horizontally pannable.

The regression landed with CSS that directly changes MkDocs search behavior, while the visual evidence covered consent states without exercising the search-open interaction. The evidence gate must recognize search/navigation selectors as requiring their meaningful interaction states.

Acceptance criteria

  • Keep the closed and open MkDocs search states within the viewport at desktop, intermediate, and mobile widths.
  • Preserve a usable search input, result list, close/back control, consent controls, and underlying navigation behavior.
  • Add a focused browser regression assertion that opens search and verifies document width does not exceed viewport width at intermediate and mobile sizes.
  • Update visual-evidence classification so customer-facing CSS or templates that affect search/navigation require captures of the affected open interaction state, not only the default page state.
  • Do not pin documentation prose, headings, or Markdown layout.

Delete when

Both repository changes are landed, and rendered evidence shows the search-open state without horizontal overflow at intermediate and mobile widths.

Required source targets

durable-workflow/.github@main
durable-workflow/sdk-python@main

Metadata

Metadata

Assignees

No one assigned

    Labels

    authority:githubGitHub is the authoritative lifecycle record for this workbeta:compatibleMay be completed without changing the frozen beta contractkind:cross-repositoryWork spans more than one public repositorypriority:P2Normal-priority product workrepo:sdk-pythonOwned by the Python SDK repositorystatus:doneDerived from the authoritative closed issue state

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions