-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add second set of data table action icons below the report title #22827
base: 5.x-dev
Are you sure you want to change the base?
Conversation
So far found a weird behaviour where the top actions don't display the settings icon when the report doesn't show data, need to dig into that. |
91d09e8
to
80ee0a8
Compare
delete self.param.totalRows; | ||
delete self.param.totalRows; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This actually fixes the alignment in IDE
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Transitions are not within the data table wrapper, so they don't get the top controls.
606f240
to
a8e4e9a
Compare
This should be resolved. |
See internal Jira card for more details on the context of the change. |
Remaining failing UI tests come from submodules. |
I've been reviewing the screenshots and found a few that don't look right. All the This also applies to the Looking at I'll stop reviewing now until those are corrected, as i think fixing them once will fix a lot of the screenshots. |
Thanks for the feedback @caddoo.
They actually don't spill over, they are at the very edge with 0 pixels gap. My understanding is that is due to how the report screenshot is taken, not that there would be anything missing. However we do use
Again, this is due to how the screenshots are taken and where the mouse is during that event since the bottom actions were visible on hover. If the mouse is moved outside of the report or the report is not being interacted with, the hover effect is not there and the bottom action are not visible. The change makes both bottom and top controls visible at all times, which is why it is newly visible both at the bottom and at the top. Does that answer your question? |
@michalkleiner there are still a couple of inconsistencies. For example if you search for something and the table then has no results: report_search.mp4And another problem I've spotted is, that the datatable setting do not always have the same options: report_settings.mp4 |
Thanks for your testing @sgiehl. The inconsistency around the top controls being hidden came from it being hidden when there's no data initially, but it didn't occur to me that it would also apply when searching, so I guess I'll need to check if we can differentiate those two scenarios - initial table empty and empty search results. For the latter, I have no idea why that would be happening, unless someone was adding the options via JS. I'll investigate, but any hints would be appreciated. |
The flattening option is not added, it is removed from the table: matomo/plugins/CoreHome/javascripts/dataTable.js Lines 1262 to 1270 in 0973713
So the top action row is correct, and the bottom one is not, because there is no loop over both |
There is a few other UI screenshots updated as a leftover from the icons update. |
Plugin PRs created |
This issue is in "needs review" but there has been no activity for 7 days. ping @matomo-org/core-reviewers |
# Conflicts: # tests/UI/expected-screenshots/Comparison_multi_row_evolution.png # tests/UI/expected-screenshots/IncompletePeriodVisualisation_visitors_overview.png
@matomo-org/core-reviewers please have another look, the merge conflict was resolved, there are no errors in UI tests, the failing ones are from submodules that have their respective PRs prepared to be merged after this. |
@@ -50,6 +57,14 @@ | |||
{% if error is defined %} | |||
<div vue-entry="CoreHome.Alert" severity="danger">{{ error.message }}</div> | |||
{% else %} | |||
{% if showTableActionsInHeader %} | |||
<div class="row dataTableHeaderControls"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is one relevant test failures broken by the .row
selector changes:
https://github.com/matomo-org/matomo/actions/runs/12666720833/job/35298662515#step:3:1054
matomo/tests/UI/specs/UIIntegration_spec.js
Line 557 in bc8e0c2
await page.hover('.dataTableVizVisitorLog .row:nth-child(2) .actionList li.action'); |
The test selector probably needs to be :nth-child(3)
now, or we switch to jQuery and .card:eq(2)
🤔
@@ -111,7 +111,7 @@ describe("PagePerformance", function () { | |||
await page.goto("?module=Widgetize&action=iframe&disableLink=0&widget=1&moduleToWidgetize=Actions&actionToWidgetize=getPageUrls&" + generalParams); | |||
|
|||
// hover visualization selection | |||
const icon = await page.jQuery('.activateVisualizationSelection'); | |||
const icon = await page.jQuery('.activateVisualizationSelection:last'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is one more selector causing issues in this suite:
https://github.com/matomo-org/matomo/actions/runs/12666720833/job/35298664217#step:3:1126
const icon = await page.jQuery('.dropdown-content .icon-page-performance'); |
Changing that to .dropdown-content .icon-page-performance:last
could already solve the issue.
@@ -218,7 +204,7 @@ describe("EvolutionGraph", function () { | |||
testEnvironment.save(); | |||
|
|||
await page.goto(url); | |||
await showDataTableFooter(); | |||
await page.waitForNetworkIdle(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adding this here only to have a resolvable thread.
There are two weird reported screenshot errors:
- https://github.com/matomo-org/matomo/actions/runs/12666720833/job/35298662515#step:3:1041
- https://github.com/matomo-org/matomo/actions/runs/12666720833/job/35298663653#step:3:1064
If I download the screenshots from the artifact host they tell me there is no difference, but CI has an issue somehow. Maybe it solves itself in the next CI run 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I noticed those as well and was hoping for them to resolve, but at the same time I can just update them and see if it fixes itself afterwards.
Description:
Ref. DEV-13900
Review