Skip to content


Subversion checkout URL

You can clone with
Download ZIP


"Length of visits" pie chart disappears when browser window is resized #3295

Amenel opened this Issue · 10 comments

3 participants


When the "length of visits" widget is configured to display a pie chart (and only in that configuration), any resizing of the browser window causes the chart to vanish from the page.

Tested in Firefox 12, Opera 11.64, Chromium 11 and IE 9.

When that happens, hovering over the area where the pie chart should have been generates numerous JS errors. These errors are harmless and I wouldn't have noticed them if it hadn't had Firebug installed in Firefox.


Thanks for the report. Do you mean the graph "Visits per visit duration" ? For me it works well in firefox. Can you reproduce on demo ? which URL ?


Yes, I mean the graph that shows how long visits last. Please see the attachment for a screenshot of the widget.

I am using 1.8.2 on my website,


Attachment: The widget that is affected by the issue.
MWSnap 2012-08-03, 12_51_19 - Piwik widget.png


Can you reproduce the problem on ?


Yes I can reproduce the problem on (see attached files for screen captures in FF 12.0) in both FF 12.0 and Opera 11.64.

To reproduce:

  • open in a maximized browser window
  • go to the bottom left widget ("Dure des visites" or "Length of visits")
  • change the graph type from "tag cloud" to "piechart"
  • un-maximize the browser windo => all widgets are resized but the pie chart disappears from the webpage while all other widgets retain their previous appearance.

To make the graph appear again, you need to click the pie chart icon.


I have just added a screenshot of the errors logged in the Firebug console. Maybe that it'll help pinpointing the root cause of this ungodly vanishment


(In [6705]) Fixes #3295, make sure Piwik JQPlot class doesn't transform pie chart data twice.

@Amenel Amenel added this to the 1.8.3 - Piwik 1.8.3 milestone
@diosmosis diosmosis was assigned by Amenel
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.