changed Timeline redraw has been significantly restructured to optimise performance. Previous versions hit performance issues on slower devices above around 10,000 events on the timeline. This is now up to 30,000 events, and can go considerably higher with the right settings! To top off the good news, the worst performing browsers have had the biggest improvement. So performance is now very consistent among all major browsers, with no need to set browser specific timeline options.

There is a new Timeline.requestRedraw() method that can be used to make the most of the performance enhancements within your own custom functions (see below).

new The new hoverStyle works in exactly the same way as the existing style and activeStyle options. They can be set as defaults in your timeline options, and overriden for individual articles.
The new order of style inheritance/override is: style hoverStyle activeStyle

new Set an individual article's hover style any time after initialisation.

new This method allows you to request a redraw of the timeline, optionally specifing any built-in or custom redraw function to use. The redraw will be called directly or integrated into an animation if one is ongoing. This is now the recommended way to redraw the timeline as it gives the best performance.

NOTE: All previous timeline redraw functions can still be used normally, and have some performance improvements even without switching to Timeline.requestRedraw()

new New timeline redraw function with a good balance of functionality and performance. It performs the same steps as the basic Timeline.redraw() method, but includes repositioning of articles from the current time range. This means it can be used when the time range is changing, unlike Timeline.redraw().

NOTE: The most complete (and slowest) redraw is still Timeline.defaultRedraw(), which performs all the same steps as Timeline.repositionRedraw(), but also includes re-stacking of articles on the timeline.

new Similar to Timeline.goToDateAnim(), but for panning the timeline by a number of pixels instead of to a particular date.

new New text align and baseline style options for controlling article title and subtitle.

new Disable drawing of the entire subheader by setting subheader.height to 0 in your article style options.
This means you can easily show/hide the subheader for different article states using your style, hoverStyle or activeStyle settings.

new New event which fires when each timeline redraw has been completed, with handlers registered in your timeline options. The handler function has access to the canvas context and timeline state, so this feature is ideal for adding custom drawings to the timeline canvas.

new By setting options.shiftBceDates to true, all BCE input dates will be shifted by +1 year.

This allows you to use data with either the 1BCE = 0 or 1BCE = -1 convention.
The setting applies to all date input - e.g. in article data, timeline & article methods for setting dates, initial date in timeline options.

changed The draggingVicinity timeline option will now accept a function or boolean value, as well as the original {up: x, down: y} syntax. The default value has been set to true, which enables dragging over the whole timeline canvas.

changed The article.autoStacking.topGap timeline option will now accept a function as well as a number.

changed The default zoom.wheelSpeed timeline option has been increased to 3

changed The default style.mainLine.size timeline option has been increased by a single pixel to 8. Using even numbers for this setting avoids pixel rounding for the top and bottom of the mainLine, giving a sharp line instead of slightly blurred edges. This will be fixed in a future version but best to stick with even numbers where possible for now.

Compatibility with Internet Explorer 11 and various other older browsers has been restored.

The title property in article data is now optional. If not specified it defaults to an empty string "".

When attempting to set a date that does land on a timeline marker, the fraction of the marker was not being calculated. This is now corrected, so the position reached on the timeline is correct to the pixel level.