Skip to content

Make PHP portal browser evidence reject ambiguous active navigation #35

Description

@rmcdaniel

Problem

The PHP documentation browser gate renders the relevant portal pages at desktop, intermediate, mobile, and short-height sizes, but it currently checks only basic rendering, overflow, reachability, and browser errors. The Laravel adoption landing passed that gate while the same route appeared in two primary sidebar groups and produced two simultaneous aria-current="page" markers. Geometry was clean, but the navigation hierarchy was not.

Acceptance criteria

  • Fail portal qualification when a rendered guide has zero or more than one primary current-page destination.
  • Reject duplicate primary guide-navigation URLs, or represent intentional promotional cross-links outside the primary guide-navigation list so they do not create a second active destination.
  • Add a focused regression fixture that demonstrates the duplicate-route or duplicate-current state fails before deployment.
  • Retain responsive checks for the home page, first workflow, Laravel, Symfony, and the open mobile menu at desktop, intermediate, mobile, and short-height viewports.
  • Keep assertions semantic and structural; do not freeze exact headings, paragraph order, or marketing prose.

Delete when

Delete this issue when an ambiguous duplicate active destination reliably fails pre-deploy browser evidence and the corrected portal passes the full responsive matrix.

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:defectA public product behavior is incorrectpriority:P2Normal-priority product workrepo:sdk-phpOwned by the PHP SDK repositorystatus:readyReady for implementation

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions