Repository navigation
ReportHeader - update UI screenshots (feature branch) - #95
Merged
Merged
Conversation
tzi
force-pushed
the
feature-new-report-header
branch
from
August 23, 2026 22:50
e5e600a to
16482f1
Compare
tzi
force-pushed
the
feature-new-report-header
branch
from
September 17, 2026 21:03
89f98ef to
b9f61ca
Compare
The DataTable search moved from the table footer into the shared ReportHeader (matomo-org/matomo#24986), which changes every report screenshot.
Taken from the core branch that moves the report actions behind the header's 3-dots trigger, rebuilt on the pin core's base branch now records so the images carry that base's rendering rather than the one the earlier branch was generated against.
The title and the controls beside it line up on their centres, and the two control clusters keep 8px apart. Every report keeps its size.
The report header lifts Export out of its 3-dots menu into a control of its own, so the line above every full-page report in this plugin changed with it.
The control at the foot of a report takes the shape of the report's other controls, and on a table it moves onto the pagination line.
The control is centred by the pagination line itself now, rather than by a transform that opened a stacking context around it.
It sat flush against the card and now keeps 20px from its right and bottom edges.
A variable name shared with the header's selector had been widening every one of them; these were captured while it did.
Taken from the core CI run for feature-new-report-header, which changes the report header, the pagination row and the pagination counter.
tzi
force-pushed
the
feature-new-report-header
branch
from
September 21, 2026 00:20
b9f61ca to
71cf61b
Compare
The report actions moved back into the 3-dots menu for a Widgetize embed, so the promoted Export button is gone from the header line and the panel is 10px shorter.
tzi
marked this pull request as ready for review
September 29, 2026 00:38
AltamashShaikh
approved these changes
Sep 29, 2026
Contributor
|
@tzi Can you update the PR description with the required template code ? |
Contributor
Author
I updated the checklist. Is it OK? |
Contributor
|
@tzi The AI one is the most important as it is needed as per privacy officer. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Feature branch for the report header work in this plugin: it carries the 3 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