Any document created using the Uize.SimpleDoc module now contains a contents list that is generated based on the structure of the document.

The list item for each section is linked to the section's anchor in the document and has a title attribute (i.e. a tooltip) that provides a preview of the section's first paragraph. Some other small tweaks were made to improve performance and the appearance of the generated markup.

The Uize.Widget.Tree module - that is the base class for the Uize.Widget.Tree.List module - now is implemented so that the setExpandedDepth instance method does not require the DOM for a list instance to already be created before this method can be called.

If an instance of Uize.Widget.Tree.List is not yet wired up and there is no corresponding DOM for the list, then the setExpandedDepth method will only modify the expanded property at the appropriate places in the tree structure JSON object. This allows a list widget to be instantiated, with its data tree, then the tree can be expanded to a desired depth, and then the UI can be built and wired up to immediately reflect that state. This is mostly a performance improvement.

A bug was fixed with tooltips not being positioned correctly in Safari when a document is scrolled.

Essentially, Safari is not consistent with other browsers in where meaningful values for scrollLeft and scrollTop are reflected.

The palette implied node of an instance of the Uize.Widget.PopupPalette widget class is now positioned to butt up against the selector child button's root node.

If the selector button is not visible at the time that the palette is shown, then the palette is positioned based upon the current mouse coordinates.

4.3.1. New Method: Uize.Node.setAbsPosAdjacentTo

4.3.2. Improved Method: Uize.Node.getEventAbsPos

The widgets.map, widgets.add, and widgets.remove backwards compatibility provisions in the Uize.Widget class have been eliminated.

This feature had been deprecated back in May, in favor of the more concise and semantically elegant children property, and the addChild and removeChild instance methods. If you have code that references the widgets property or its add and remove methods (which is unlikely), you will need to update your code. This change lightens the memory load for every widget instance and reduces code size for the Uize.Widget class a tiny bit.

The Uize.Widget.Window module now supports new title and defaultTitle state properties that let you modify the title displayed in a window's title bar.

The Uize.clone static method of the Uize base class now supports cloning values that are instances of JavaScript's built-in RegExp, Date, String, Number, and Boolean objects.

For example, if you clone an instance of the Date object, you get a new Date object instance of the same value.

The basic marquee example has been updated to provide linked JavaScript statements that provide a demonstration of the widget's programmatic interface.

The configuration of the marquee can be updated in realtime.

The new Scrolly Carousel example demonstrates how the Uize.Widget.Scrolly class can be used to create a carousel scrolly that lets you step through a series of pages.

Such an interface could be provided on a company's homepage, with pages like "About Us", "Products", "Services", "Investor Relations", etc. Some examples of the scrolly's programmatic interface are also provided.

CHECK IT OUT

Support for the 'nodes' mode for Uize.Widget.Button instances has been eliminated.

There were only a few cases of this feature being used, and they have been converted over to the more flexible 'classes' mode. The performance of applications that instantiate hundreds of button widgets is improved as a result of this change, and the code size of the module is reduced.

There are new additions to the Coding Style Guide and JavaScript Optimization appendixes, and various methods of various modules have been documented. Documentation continues to be fleshed out more upon each release.