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

Hide the relative % value in the "Browser Plugins" report #16611

Closed
mattab opened this issue Oct 27, 2020 · 0 comments · Fixed by #16622
Closed

Hide the relative % value in the "Browser Plugins" report #16611

mattab opened this issue Oct 27, 2020 · 0 comments · Fixed by #16622
Assignees
Labels
Bug For errors / faults / flaws / inconsistencies etc.
Milestone

Comments

@mattab
Copy link
Member

mattab commented Oct 27, 2020

In the "Browser Plugins" report, the % value displayed on hover is not accurate. The value uses the sum of the Visits in that report (but in this particular "browser plugins" report, it doesn't make sense to sum the "Visits" metric, because one visit can match several plugins.). Instead we would expect to not show the value on hover (the other column " % Visits" is anyway present).

image

Reported by a user:

It's not so much a problem, but rather a wrong presentation of numbers. In the case of browser plugins, the percentage of visits in the last column makes no sense to me, and it should be removed to avoid confusion.

See my screenshot; it labels the visits that support cookies as being 72.8%. This conflicts with the correct 100% in the other column. There's no use in dividing the visits in this report because they have overlapping properties.

@mattab mattab added the Bug For errors / faults / flaws / inconsistencies etc. label Oct 27, 2020
@tsteur tsteur added this to the Priority Backlog (Help wanted) milestone Oct 27, 2020
@sgiehl sgiehl self-assigned this Oct 28, 2020
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

Successfully merging a pull request may close this issue.

4 participants