Scrolling error on Annual Site Stats page

Filed an Issue Automattic/jetpack (GitHub)
Increase your traffic, view your stats, speed up your site, and protect yourself from hackers with Jetpack. - Automattic/jetpack
Perhaps this is a native WP.com issue, but I suspect it’s JetPack functionality as it occurs both with a .org connected account as well as an example.wordpress.com domain both of which have a “Powered by JetPack” logo on the bottom of the page.

Steps to reproduce the issue

  1. Go to https://wordpress.com/stats/day/annualstats/example.com
  2. Scroll down the page (zoom in if necessary so that the table fills the entire screen; the error isn’t as or won’t be obvious on a new account or if one doesn’t have several years worth of data to view)

What I expected

I expected the entire chart and page to scroll down.

What happened instead

The Year column stayed fixed and the remainder of the chart scrolls down the page instead. Without zooming in/out on the entire page, one can’t visualize the data or have it align properly.

Screenshots
Here’s a shot of the misaligned static year column versus the remainder of the chart which scrolls up/down.
On a multi-column display the year column doesn't scroll in alignment with the remainder of the chart

Published by

Chris Aldrich

I'm a biomedical and electrical engineer with interests in information theory, complexity, evolution, genetics, signal processing, theoretical mathematics, and big history. I'm also a talent manager-producer-publisher in the entertainment industry with expertise in representation, distribution, finance, production, content delivery, and new media.

2 thoughts on “Scrolling error on Annual Site Stats page”

  1. This issue has been marked as stale and will be closed in seven days. This happened because:

    It has been inactive in the past 9 months.
    It isn’t a project or a milestone, and hasn’t been labeled [Pri] Blocker,
    [Pri] High, [Status] Keep Open, or OSS Citizen.
    You can keep the issue open by adding a comment. If you do, please provide additional context and explain why you’d like it to remain open. You can also close the issue yourself — if you do, please add a brief explanation.

Leave a Reply

Your email address will not be published. Required fields are marked *