New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

TIMELINE: Bad dates causes IE error #34

Closed

GoogleCodeExporter opened this issue Mar 21, 2016 · 1 comment

Labels

auto-migrated Priority-High Type-Defect

GoogleCodeExporter commented Mar 21, 2016

If latestStart is > earliestEnd then, on IE, causes an exception. The 
reason is that the width of the tape ends up negative, causes an exception.

Fix: do a sanity check of all the dates' temporal relationships, per event. 
Fix the bad date(s) and add error message to the event's title.

Original issue reported on code.google.com by larryklu...@gmail.com on 24 Oct 2008 at 3:09

The text was updated successfully, but these errors were encountered:

Author

GoogleCodeExporter commented Mar 21, 2016

Fixed in rev 1629. Added test cases to the test example too.

Original comment by larryklu...@gmail.com on 24 Oct 2008 at 3:31

Changed state: Fixed

GoogleCodeExporter added auto-migrated Type-Defect Priority-High labels

GoogleCodeExporter closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment