Auto-resizing on multiple points differing in seconds

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Have a dataset with 100 points on the same day, only different in
minutes/seconds
2. Chronoscope it

What is the expected output? What do you see instead?

Expected output is to be able to see the chronoscope in its fullscope.
Instead, I see a chronoscope that auto-resizes and it's initial scope is
only a portion of my data.

What version of the product are you using? On what operating system?

Newest (I am sourcing it directing from you)

Please provide any additional information below.

Original issue reported on code.google.com by dans...@gmail.com on 15 Apr 2009 at 6:06

[GoogleCodeExporter]

Just an update, I think this actually occurs also if you have the visualization 
width
set at 100%.

eg. <div id="chronoscope" width:100%>

Original comment by dans...@gmail.com on 8 May 2009 at 2:28

[GoogleCodeExporter]

Can you describe step by step how you created the project please ?
That would help in understanding what's going on.

Original comment by pkirklew...@gabaedevelopment.com on 13 Jun 2009 at 8:17

[GoogleCodeExporter]

I'm really not sure how to reproduce this problem. Apparently when I load the 
library
from <script src="http://api.timepedia.org/gviz/"></script> - and I have the
chronoscope visualization displayed in a div of width 100% along with a 
scatterplot
or table from the Google Viz, this causes the page to be re-sized automatically 
on
the page - essentially moving the chronoscope viz out of the browser window - 
without
allowing the ability to scroll horizontally.

Original comment by dans...@gmail.com on 15 Jun 2009 at 3:48

[GoogleCodeExporter]

I also noticed that this occurred when the data points had time differences of 
seconds.

Original comment by dans...@gmail.com on 10 Jul 2009 at 5:47

[GoogleCodeExporter]

Is this multiple points on the same second?  

Are the points on the domain monotonically increasing?  Chronoscope expects 
domain elements to be in increasing order.

If neither of these are the problem, please attach a dataset that shows the 
error, or a URL to a page that exhibits the error.  Thanks.

Original comment by timepedia@gmail.com on 20 Aug 2010 at 8:31