Timeline bug in Google Visualization

[avger]

I am using the visualization timeline. I ran into an odd case where the following code works. But if you comment out the first row..."Why is this line Necessary?"... I get an "Cannot read property 'v' of undefined" error. Or if I change the start date of the same line from 0ms to 10ms, I also get the v undefined error.

I think is is most likely a range issue of some sort, but i'm pretty sure is a bug.

<script type="text/javascript" src="https://www.gstatic.com/charts/loader.js"></script> <script type="text/javascript"> google.charts.load('current', {'packages':['timeline']}); google.charts.setOnLoadCallback(drawChart); function drawChart() { var container = document.getElementById('timeline'); var chart = new google.visualization.Timeline(container); var dataTable = new google.visualization.DataTable(); dataTable.addColumn({ type: 'string', id: 'Handle' }); dataTable.addColumn({ type: 'string', id: 'Description' }); dataTable.addColumn({ type: 'date', id: 'Start' }); dataTable.addColumn({ type: 'date', id: 'End' }); dataTable.addRows([

['Why is this line Necessary?', '', new Date(0, 0, 0, 0, 0, 0 , 0), new Date(0, 0, 0, 0,0,0,698) ],

['23-Tx Length', '0x 10 00 02 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00', new Date(0, 0, 0, 0,0,00,576), new Date(0, 0, 0, 0,0,00,578) ],
['27-Tx Data', '0x 2a 8e de 83 49 b7 0f e6 75 37 bf 04 7e 03 27 62', new Date(0, 0, 0, 0,0,00,655), new Date(0, 0, 0, 0,0,00,657) ],
['31-Tx Crc', '0x a0 26', new Date(0, 0, 0, 0,0,00,656), new Date(0, 0, 0, 0,0,00,658) ],
['35-Tx ACK/NAK', '0x 01', new Date(0, 0, 0, 0,0,00,695), new Date(0, 0, 0, 0,0,00,697) ]

]);

var options = {
timeline: { colorByRowLabel: true }
};
chart.draw(dataTable, options);
}
</script>

[avger]

HTML did not seem to come through. I'll try attaching .html file.
bleTraceMAPPReconnectionChallengeRequest.html.txt

[dlaliberte]

The timeline chart doesn't know how to deal with ranges less than 1 second, so extending to 0, or extending to 1000 milliseconds makes it work well enough.

Sorry about that. This is definitely a bug, which we should at least catch and report in a more meaningful way.

[benhowell]

Same bug appears in Gantt charts.

[aalcutt]

Is there any way to fix this or work around it?

[SemihGk]

This bug seems very old, but I do experience the same issue. Is there any plan for a possible fix?

[namedgraph]

Hello? Any fix in sight?

[crufter]

Just got bit by this too.