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.

Sign up for GitHub

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

Jump to bottom

Visitor stats are always set to 0 when selecting a custom range in Performance dashboard card #12680

Open
JorgeMucientes opened this issue Sep 24, 2024 · 1 comment
Open

Visitor stats are always set to 0 when selecting a custom range in Performance dashboard card #12680

JorgeMucientes opened this issue Sep 24, 2024 · 1 comment
Labels
feature: dashboard Related to home screen project priority: low Not many people are affected or there’s a workaround, etc.

Comments

@JorgeMucientes
Copy link
Contributor

JorgeMucientes commented Sep 24, 2024 •
edited
Loading

Describe the bug
Visitor stats are always set to 0 when selecting a custom range in the Performance dashboard card. Whatever the custom range I select, visitor stats are always 0 when dragging your finger through the chart.

Screenshots

visitorsAlways0.mp4

On iOS the same site and same custom range displays visitor stats different from 0:

Simulator.Screen.Recording.-.iPhone.15.-.2024-09-24.at.18.28.03.mp4
@JorgeMucientes JorgeMucientes added type: bug A confirmed bug. feature: dashboard Related to home screen project labels Sep 24, 2024
@dangermattic
Copy link
Collaborator

dangermattic commented Sep 24, 2024 •
edited
Loading

🚫 Please add a type label (e.g. type: enhancement) and a feature label (e.g. feature: stats) to this issue.

@JorgeMucientes JorgeMucientes added priority: low Not many people are affected or there’s a workaround, etc. and removed type: bug A confirmed bug. labels Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature: dashboard Related to home screen project priority: low Not many people are affected or there’s a workaround, etc.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@JorgeMucientes @dangermattic