JavaScript exception if time_start > time_end

When reporting undesired behavior, please also specify how exactly you would like that behavior changed.

In this case, it seems natural that the timeline widget might freak out if event durations have negative extent. Presumably the situation was remedied when you corrected the field ordering?

Unless otherwise specified, I would close this as "won't fix".

No can do: that'd have to be inside the SIMILE code, which is not maintained as part of this Drupal module.

It would, however, be possible to have the Timeline module automatically reverse start/end dates that are in the wrong order when creating the JSON feed for the widget. However, that could be problematic since the user never sees his mistake, and it could eventually mask some other larger problem. The other option is to do nothing and close this. Opinions, anyone? Jeff?

@ebrad the problem here is that by the time we can determine that the data is wrong it's too late to present a nice error message. Drupal has already loaded the page and we are just presenting JSON data to the timeline widget.

So the options are - We let the SIMILE code handle the error (present situation), we "fix" it (swap the dates) and potentially mask larger problems, or we could possible display a 'quiet' timeline that doesn't "bark" (ie is blank or ignores end data, etc).

I think the correct way here is to construct the JSON feed as described in the view and let the SIMILE code produce the error, which is what happens now.

In the D6 version we're ignoring end dates that are before start dates.