Skip to content

ReportHeader - update UI screenshots (feature branch) - #235

Draft
tzi wants to merge 2 commits into
6.x-devfrom
feature-new-report-header
Draft

ReportHeader - update UI screenshots (feature branch)#235
tzi wants to merge 2 commits into
6.x-devfrom
feature-new-report-header

Conversation

@tzi

@tzi tzi commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

Description

Feature branch for the report header work in this plugin: it carries the 7 expected UI screenshots regenerated for the DataTable search moving from the table footer into the shared report header.

Merged into this branch

Impact

None visible to users: expected test screenshots only.

Step by step tests

Nothing to exercise by hand. The screenshots come from the CI artifacts of matomo-org/matomo#24986 and are verified by the core feature branch, matomo-org/matomo#25059.

Note on the UI tests

The plugin's own UI jobs run against core 6.x-dev, which does not yet contain the report header change, so they compare these screenshots against a core that renders the old footer search and go red. They turn green once matomo-org/matomo#25059 lands. Merge this only together with that PR.

Checklist

  • I have understood, reviewed, and tested all AI outputs before use
  • All AI instructions respect security, IP, and privacy rules

The DataTable search moved from the table footer into the shared ReportHeader
(matomo-org/matomo#24986), which changes every report screenshot.
The report header search restyles the shared form controls, which moves the help
panel text on the plugin settings page down by a pixel. That was captured on the
previous report-header branch, but this branch was cut from 6.x-dev, where the
same file had been recaptured for the TrackingSpamPrevention integration (#233)
against a core without the restyle, so the adjustment was lost.

Byte-identical to what CI renders for the report header branch.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant