0.8.0-beta

Dynamic template support etc.

See 0.7.0...0.8.0-beta for details.

0.8.0-alpha

Tag for Christophe. The API will change again before the 0.8.0 release.

0.7.1

What's new in this release?

Bug Fix

• delite/features uses window and it is breaking the build. (#401)

0.7.0

What's new in this release?

New Features

• support inheritance of direction from any ancestor node (#381)
• support native properties (#34)

Enhancements

• Container: emit delite-add-child, delite-remove-child events (#403)
• automatically call parse() and attachedCallback() / detachedCallback() (#392)
• make Widget#detachedCallback() call detachedCallback() on widgets in template (#390)
• allow repeated calls to attachedCallback() / detachedCallback() (#388)
• Remove Widget#startup() method (#386)
• Call Widget#deliver() automatically on creation (#385)

Bug Fixes

• HasDropDown#detachedCallback() should detach wrapper (#406)
• Widget#getParent() should return null when no parent (#405)
• delite/features uses window and it is breaking the build. (#401)
• register.parse() throws exception when no widgets registered (Safari 8.0.4) (#393)
• KeyNav: scrolling should not trigger navigation (#379)

Open Issues

• Due to (#392) custom elements inside of <template> nodes are being instantiated. This breaks liaison (and also, goes against the spec of how <template> works). Planned to be fixed in a 0.7.2 point release.

0.7.0-beta.5

API changes:

• Applications shouldn't call register.parse() anymore, nor CustomElement#attachedCallback(). It happens automatically. Therefore, you don't need to require() "delite/register" unless you are declaring your own widgets. There is a new register.deliver() method that you can call if you need for widgets to be parsed synchronously.
• Removed deprecated Widget#startup() method.
• refreshRendering() may get called before widget is attached to the document. Actually, that was true before too, but now it's more likely.
• The Widget#isLeftToRight() method was replaced by an effectiveDir property, indicating the widget's dir setting, or the setting it inherits. When effectivDir's value changes, it triggers a notification to computeProperties() and refreshRendering(), just like when other property values change.

Bug fixes:

• KeyNav: navigate on click, not pointerdown. Avoids problem on tablets/phones where scrolling navigates to a node. Fixes #379.
• Widget#getParent() returns null if this.parentNode is null. #405
• HasDropDown does better job cleaning up old popups (by detaching them from the document)

Enhancements:

• Call parser and attachedCallback() / detachedCallback() automatically. Also, attachedCallback() will only be executed once, even if it's called multiple times. Happens asynchronously, but there's a register.deliver() method to make it happen synchronously.
• HasDropDown: add focusOnPointerOpen and focusOnKeyboardOpen properties.
• Add has("inherited-dir") flag to inherit direction from any ancestor
• Allow observing changes to any native property
• Call deliver() automatically when widgets created. Fixes #385.
• Made deliver() work synchronously on native properties too. Previously on Chrome the native property updates were always delivered asynchronously.
• Allow CustomElements to be attached and then detached repeatedly.

0.7.0-beta.4

API changes:

• Applications shouldn't call register.parse() anymore, nor CustomElement#attachedCallback(). It happens automatically. Therefore, you don't need to require() "delite/register" unless you are declaring your own widgets. There is a new register.deliver() method that you can call if you need for widgets to be parsed synchronously.
• Removed deprecated Widget#startup() method.
• refreshRendering() may get called before widget is attached to the document. Actually, that was true before too, but now it's more likely.

Bug fixes:

• KeyNav: navigate on click, not pointerdown. Avoids problem on tablets/phones where scrolling navigates to a node. Fixes #379.

Enhancements:

• Call parser and attachedCallback() / detachedCallback() automatically. Also, attachedCallback() will only be executed once, even if it's called multiple times. Happens asynchronously, but there's a register.deliver() method to make it happen synchronously.
• HasDropDown: add focusOnPointerOpen and focusOnKeyboardOpen properties.
• Add has("inherited-dir") flag to inherit direction from any ancestor
• Allow observing changes to any native property
• Call deliver() automatically when widgets created. Fixes #385.
• Made deliver() work synchronously on native properties too. Previously on Chrome the native property updates were always delivered asynchronously.
• Allow CustomElements to be attached and then detached repeatedly.

0.7.0-beta.3

Bug fixes:

• KeyNav: navigate on click, not pointerdown. Avoids problem on tablets/phones where scrolling navigates to a node. Fixes #379.

Enhancements:

• Call parser and attachedCallback() / detachedCallback() automatically. Also, attachedCallback() will only be executed once, even if it's called multiple times. Happens asynchronously, but there's a register.deliver() method to make it happen synchronously.
• HasDropDown: add focusOnPointerOpen and focusOnKeyboardOpen properties.
• Add has("inherited-dir") flag to inherit direction from any ancestor
• Allow observing changes to any native property
• Call deliver() automatically when widgets created. Fixes #385.
• Made deliver() work synchronously on native properties too. Previously on Chrome the native property updates were always delivered asynchronously.
• Allow CustomElements to be attached and then detached repeatedly.

API changes:

• Applications shouldn't call register.parse() anymore, nor CustomElement#attachedCallback(). It happens automatically. Therefore, you don't need to require() "delite/register" unless you are declaring your own widgets.
• Removed deprecated Widget#startup() method.
• refreshRendering() may get called before widget is attached to the document. Actually, that was true before too, but now it's more likely.

0.7.0-beta.2

Bug fixes:

• KeyNav: navigate on click, not pointerdown. Avoids problem on tablets/phones where scrolling navigates to a node. Fixes #379.

Enhancements:

• HasDropDown: add focusOnPointerOpen and focusOnKeyboardOpen properties.
• Add has("inherited-dir") flag to inherit direction from any ancestor
• Allow observing changes to any native property
• Call deliver() automatically when widgets created. Fixes #385.
• Made deliver() work synchronously on native properties too. Previously on Chrome the native property updates were always delivered asynchronously.
• Allow CustomElements to be attached and then detached repeatedly.
• attachedCallback() will only be executed once, even if it's called multiple times.

API changes:

• Removed deprecated Widget#startup() method.
• refreshRendering() may get called before widget is attached to the document. Actually, that was true before too, but now it's more likely.

0.7.0-beta

set version to 0.7.0

0.6.0

What's new in this release?

Enhancements

• Bidi support enhancements
• Print warning when template tries to use undefined custom element
• handlebars requireAndCompile() method for code that needs to load the templates manually rather than using handlebars! as a plugin
• Widget#attachedCallback() enhanced to automatically start widgets in templates.
• Optimized register.upgrade() to not call document.contains() unnecessarily
• guard against repeated calls to attachedCallback()
• Delite tutorial
• Updates to doc, tests, etc.

API changes

• Replaced evt.loadDeferred with evt.setChild(). setChild() takes a promise or a plain object (like the one previously passed to loadDeferred.resolve()).
• For people using delite/Template directly rather than via handlebars: AST for strings (attribute values and inner text )changed from {expr: "this.label", dependsOn: ["label"]} to just this.label. Template.js computes the dependencies automatically.
• Deprecated Widget#startup(). Promoting Widget#placeAt() instead. Widget#attachedCallback() enhanced to automatically start widgets in templates, and placeAt() will call attachedCallback on delite/Container's children.
• HasDropDown no longer sets CSS classes for the arrow direction

Bug fixes

• FormWidget and FormValueWidget cleanup:
  • apply disabled, readonly, alt properties to focusNode, not just valueNode
  • automatically map value property to this.valueNode
  • fix handling for widgets with multiple tab stops
• fix for when KeyNav.focusDependents is set to false after creation

Internal changes

• use lie Promise library rather than dojo/Deferred
• (relatedly) removal of dojo dependencies (except from test files)

See 0.5.1...0.6.0 for details.