Thank you so much, you guys!

Find "Disable accelerated 2D canvas" in the list and click "enable"

At the bottom of the page, you'll need to click "Relaunch"

Then, you should be good to go.

Thanks!

For some reason (I have no clue about this stuff) I had to go to about:config and set dom.storage.enable to 'true' dispite local storage was enabled in Firefox settings all the time.

Good question. The answer is a bit technical.

Google Chrome is continually developed and Google is trying to make everything render faster. That means offloading tasks on to the hardware, rather than computing it in software. The recent change Google made, was to have "canvas" elements be rendered by the hardware -- the stats chart is a canvas element. When this is rendered by hardware, it renders faster and uses less battery on mobile computers.

Enabling the "Disable accelerated 2D canvas" flag reverts the behavior, so canvas elements are rendered in software again.

I believe flags are reset for every new stable major version of Chrome there is. So come Chrome 24, hopefully Google will have fixed this issue, and the flag should be reset automatically as you receive the update. Stable Chrome updates are usually 6 weeks apart. I could be wrong though, that flags are set until you unset them (or the are removed).

If setting the flag makes the chart work for you, I can't think of any downsides. In fact, other websites that use the canvas element should be more compatible as a side-effect.

But the real solution is for Google to fix the bug so you don't have to use the flag.

If I do leave them enabled (which I'm happy to by the way) could these settings affect anything else in Chrome?

It's just as a matter of interest just incase something else is affected down the line! :-)

Thanks for your help!

Thanks for everybody's help.

When I first log in and click the link to stats nothing happens just the loading symbol going round and round.

Thanks

Until Google fixes this issue in Chrome, there are unfortunately only two solutions for users who are experiencing this issue: either change the flags as suggested in the thread linked above, or use a different browser to view stats.

I'm going to file a bugreport with Google, and hopefully they'll fix it in the next version of Chrome.

That also means that until Google fixes this issue, there are unfortunately only two solutions for users who are experiencing this issue: either change the flags as suggested above, or use a different browser to view stats.

We're speculating that a change related to hardware acceleration made to Chrome 23 and newer may conflict with the stats chart on some hardware configurations.

In order to verify whether or not this is the case, we ask that one of you who has this issue try the following:

1. Visit the page chrome://flags/ in your Chrome browser
2. Click “Enable” next to the two items shown in this screenshot: http://cl.ly/image/150b1m3k0L0r
3. Restart the browser and see whether the bars have returned

Important: before you do this you should know there's a risk associated with changing these settings, so you should not do this unless you're logged into Chrome with your Google account, so your bookmarks and settings are backed up. Worst case scenario, Chrome won't start after changing these flags, and you'll have to reinstall. I don't think this is likely, but knowing is half the battle.

Please let us know if changing these settings makes the chart work again.

Thank you.

I took two shots of the stats so you could read the whole page (wasn't quite figuring out how else to get the sizing right).

http://dadpoet.files.wordpress.com/2012/11/screeb-shot-stats-1.jpg

http://dadpoet.files.wordpress.com/2012/11/screeb-shot-stats-2.jpg

And one of the stats as they appear on the Dashboard:

http://dadpoet.files.wordpress.com/2012/11/screeb-shot-stats-2.jpg

We're still looking into this.

(Jenia, thanks for being here on Thanksgiving!)

This is what I see on booksnobbery.wordpress.com/wp-admin/index.php?page=stats: http://screencast.com/t/RTapWm1S

It doesn't look like there are any errors on either.