🐛🧑‍💻 - Compare navigation screenshots with original Home Assistant pixels #14

Activity

1. efraespada

   added

   bugSomething isn't workingSomething isn't working

   in-progressStart work on an admitted issue.Start work on an admitted issue.

   bugfixLabel to manage bugfix branchesLabel to manage bugfix branches

   priority: highLabel to indicate a priority highLabel to indicate a priority high

   on Nov 5, 2026
2. vypbot

   added

   state:ai-processingA Copilot agent is analyzing or working on the issue or change.A Copilot agent is analyzing or working on the issue or change.

   on Nov 5, 2026
3. vypbot

   assigned

   efraespada

   on Nov 5, 2026
4. vypbot

   added the

   Bug

   issue type on Nov 5, 2026
5. vypbot

   added this to vypdevon Nov 5, 2026
6. vypbot

   moved this to Todo in vypdevon Nov 5, 2026
7. vypbot

   moved this from Todo to In Progress in vypdevon Nov 5, 2026
8. vypbot

   added

   branchedThe linked branch and required SDD commit are verified.The linked branch and required SDD commit are verified.

   on Nov 5, 2026
9. vypbot

   changed the title [-]Compare navigation screenshots with original Home Assistant pixels[/-] [+]🐛🧑‍💻 - Compare navigation screenshots with original Home Assistant pixels[/+] on Nov 5, 2026
10. vypbot

    added

    state:workingWork can proceed on the verified branch or without a branch.Work can proceed on the verified branch or without a branch.

    and removed

    state:ai-processingA Copilot agent is analyzing or working on the issue or change.A Copilot agent is analyzing or working on the issue or change.

    on Nov 5, 2026
11. vypbot commented on Nov 5, 2026

    

    vypbot

    on Nov 5, 2026

    More actions

    Implementation plan

    Current status: Ready to start. No action is required from maintainers before implementation.

    1. Locate the navigation parity checks and reference captures
       • Identify the text and icon Storybook checks, their independently captured Home Assistant references, and the existing Chromium platform matrix.
    2. Add decoded-pixel comparison
       • Compare each built catalog screenshot with its matching reference and report a pixel agreement metric alongside the original image identity and candidate screenshot.
    3. Set measured platform tolerances
       • Measure capture differences on Linux and macOS and use a narrow tolerance only where a platform requires it.
    4. Preserve existing assertions and captures
       • Keep geometry, state, and accessibility assertions and retain the original reference captures.
    5. Verify both checks across the matrix
       • Run the static Storybook tests on the existing Chromium platform matrix and update relevant documentation if the comparison workflow changes.

    Acceptance: On every existing Chromium matrix platform, both text and icon navigation parity reports include a pixel agreement metric against the matching independent reference, and the checks pass within the measured platform tolerance while retaining their existing geometry, state, and accessibility assertions.

    Need something else? Mention the bot with a question or use /copilot help.
12. vypbot

    added

    state:ai-processingA Copilot agent is analyzing or working on the issue or change.A Copilot agent is analyzing or working on the issue or change.

    size: SLabel to indicate a task of size SLabel to indicate a task of size S

    on Nov 5, 2026
13. efraespada

    linked a pull request that will close this issuetest: compare Home Assistant navigation pixels #15on Nov 5, 2026
14. vypbot

    added

    75%Progress: 75%Progress: 75%

    and removed

    state:ai-processingA Copilot agent is analyzing or working on the issue or change.A Copilot agent is analyzing or working on the issue or change.

    on Nov 5, 2026
15. vypbot commented on Nov 5, 2026

    

    vypbot

    on Nov 5, 2026

    Last edited by vypbot

    More actions

    Issue closed — historical progress

    Current status: closed as completed.

    The last estimate is retained below as history. Closure does not certify a new percentage, tests, or branch alignment.

    Action required: none for this closed issue. If work continues, reopen the issue; a fresh assessment can update this same card.

    Last assessment before closure (historical)

    Progress: 75% — in progress

    > Current status: [R1] The text and icon navigation checks compare measured styles and geometry but only retain screenshots. They can miss a paint-only regression in the navigation surface. Compare decoded pixels from the built catalog against the existing independently captured Home Assistant references for both checks, with a narrow, measured tolerance where the captured platform requires it. — Both navigation checks compare decoded candidate pixels with the matching original reference and assert zero changed pixels. Reports record raster agreement alongside existing measured style and geometry results.
    [R2] Keep the existing geometry, state and accessibility assertions and the original captures. Validate on the existing Chromium platform matrix. The change belongs on develop so promotion PR #13 receives the correction. — The patches preserve the existing geometry, state, accessibility, and reference-image checks. Documentation describes pixel checks on macOS and Linux, but the supplied comparison does not establish execution across the Chromium platform matrix or branch promotion.
    [R3] "acceptance": "On every existing Chromium matrix platform, both text and icon navigation parity reports include a pixel agreement metric against the matching independent reference, and the checks pass within the measured platform tolerance while retaining their existing geometry, state, and accessibility assertions." — The source adds a pixel agreement metric and a zero-changed-p
    [untrusted content truncated]

    Next: [R2] Keep the existing geometry, state and accessibility assertions and the original captures. Validate on the existing Chromium platform matrix. The change belongs on develop so promotion PR #13 receives the correction. — Verify both checks on every existing Chromium matrix platform and confirm the correction is on develop for promotion PR #13.
    [R3] "acceptance": "On every existing Chromium matrix platform, both text and icon navigation parity reports include a pixel agreement metric against the matching independent reference, and the checks pass within the measured platform tolerance while retaining their existing geometry, state, and accessibility assertions." — Obtain independent results confirming both reports include pixel agreement against matching references and pass on every existing Chromium matrix platform.
16. vypbot commented on Nov 5, 2026

    

    vypbot

    on Nov 5, 2026

    Last edited by vypbot

    More actions

    Issue closed: synchronization recommendation retired

    No branch synchronization is required for this closed issue.

    The previous recommendation is historical. Issue closure does not certify that the branches are synchronized.
17. vypbot

    closed this as completedon Nov 5, 2026
18. vypbot

    removed

    in-progressStart work on an admitted issue.Start work on an admitted issue.

    on Nov 5, 2026
19. github-project-automation

    moved this from In Progress to Done in vypdevon Nov 5, 2026
20. vypbot

    added

    100%Progress: 100%Progress: 100%

    and removed

    state:workingWork can proceed on the verified branch or without a branch.Work can proceed on the verified branch or without a branch.

    75%Progress: 75%Progress: 75%

    on Nov 5, 2026