0.7.0-beta.5
Pre-release
Pre-release
API changes:
- Applications shouldn't call
register.parse()
anymore, norCustomElement#attachedCallback()
. It happens automatically. Therefore, you don't need torequire()
"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 aneffectiveDir
property, indicating the widget's dir setting, or the setting it inherits. WheneffectivDir
's value changes, it triggers a notification tocomputeProperties()
andrefreshRendering()
, 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.