v1.2.2 Cotton Candy Cloud

• fixed a long-standing bug that caused bind-repeat bindings in the default stable mode to be rendered in reverse order #23 (#44)

v1.2.1 Cotton Candy Cloud

• fixed a bug that caused getters inside an expression to always get executed twice #27 (#28)
• an already scheduled scope recycle would cause an exception, if the scope was destroyed before the recycle was executed #24 (#26)
• the legacy mode of the attribute binding caused an exception #22 (#29)

v1.2.0 Cotton Candy Cloud

• template recycling has been isolated when the new createTemplateInstance() method is used to instantiate a template. The previous makeTemplate() method will be deprecated.
• bind-repeat has been upgraded into a Binding API binding and recycling has been improved.
• binding attributes now can make use of parameters in the form of bind-event(param)="value"
• first steps for server side rendering have been made
• elements are kept visible as long as they are animated and neither of their three closest ancestors
• if an animation binding returns an empty string it is aborted
• when parsing expressions results in a number, the number is returned as a number, not a string anymore
• binding API has been implemented
• bind-attr now supports two-way bindings
• bind-repeat now supports the parameter fast which sets the fast render mode
• if animation functions don't return a value an error is now logged
• new bind-event binding
• added package-lock.json
• fixed binding of ScopePrototype.update()
• Auto bindings have been moved to an BindingApi implementation
• If bindings have been improved
• Template references have been implemented
• .attachBindings() method introduced
• fixed if bindings which are directly located in a shadow root
• fixed legacy bindings for the .attachBindings() method
• use nextSibling in repeat binding to work around ShadyDOM quirk
• updated to the latest application-frame
• input elements no longer lose focus when their value is changed in chrome
• IE11 treats native constructors as objects with a constructor property, so we can't use hasPrototype() directly on it
• IE 11 provides an attributes property on DocumentFragments with no items, but getAttribute() fails
• stable repeat is now actually stable
• event handler expressions are now evaluated every time the handler is called
• style bindings now trigger a scope update when their values change
• logging can now be controlled via meta prefs
• old internal functions have been removed

v1.2.0 Dev Version 13

• console module now implements log(), the absence of this function broke the previous development version
• the console module is now always imported the right way

v1.2.0 Dev Version 12

• stable repeat is now actually stable
• event handler expressions are now evaluated every time the handler is called
• style bindings now trigger a scope update when their values change
• auto binding wasn't imported anywhere and therefore not available
• logging can now be controlled via meta prefs
• old internal functions have been removed

v1.2.0 Dev Version 11

• IE11 treats native constructors as objects with an constructor property, so we can't use hasPrototype() directly on it
• It also provides an attributes property on DocumentFragments with no items, but getAttribute() fails

v1.2.0 Dev Version 10

• input elements no longer lose focus when their value is changed in chrome

v1.2.0 Dev Version 9

• use nextSibling in repeat binding to work around ShadyDOM quirk
• updated to the latest application-frame

v1.2.0 Dev Version 8

• fixed if bindings which are directly located in a shadow root
• fixed legacy bindings for the .attachBindings() method

v1.2.0 Dev Version 7

• experimental .attachBindings() method introduced
• fixed view update after a scheduled scope update
• fixed a typo in a console error statement