Skip to content
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

After subtable expands, the margin left of table row actions is calculated incorrectly (sometimes) #19277

Open
diosmosis opened this issue May 26, 2022 · 2 comments
Labels
Bug For errors / faults / flaws / inconsistencies etc.

Comments

@diosmosis
Copy link
Member

To reproduce:

  • open a report (tested w/ a CustomReports report w/ many metrics that scroll)
  • hover over a row with a subtable (notice the segmented visitor log + row evolution icon shows)
  • click the row to expand the subtable (the icons will disappear at first)
  • move the mouse w/o existing the row (the row actions will display, but only the segmented visitor log is visible)

The row evolution icon is in the HTML after the segmented visitor log one, but is displayed under it because the margin-left is too high. If you move the mouse away and back over, it can randomly appear in the correct position.

This issue can be seen in the CustomReports test as a random failure:

image

@diosmosis diosmosis added the Potential Bug Something that might be a bug, but needs validation and confirmation it can be reproduced. label May 26, 2022
@bx80 bx80 added Bug For errors / faults / flaws / inconsistencies etc. and removed Potential Bug Something that might be a bug, but needs validation and confirmation it can be reproduced. labels May 30, 2022
@bx80 bx80 added this to the For Prioritization milestone May 30, 2022
@bx80
Copy link
Contributor

bx80 commented May 30, 2022

I managed to recreate this with a CustomReport report. 👍
Couldn't recreate it with any other data tables, so it might be specific to custom reports?

@diosmosis
Copy link
Member Author

Possibly, I didn't check any other tables. I assumed it had to do with the number of columns in the table. If that's the case then a goals table for a site w/ many goals might exhibit the same behavior. (Though again I didn't check for this.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For errors / faults / flaws / inconsistencies etc.
Projects
None yet
Development

No branches or pull requests

2 participants