[isDisabled]="disabled || isDisabled(node, nodeIndex(index))"

Because of the hardcoded disabled property, isDisabled cannot be reliably used to control which item is disabled.

Disabling the parent node automatically disables the entire tree under it and isDisabled is never called for those items.

It should behave like other functions - isChecked, isExpanded, isVisible etc - where you have full control over which item does what.

Hello,

It would be very nice to have dedicated PDF Export functionality for the Editor.  Some of the features that would be included with this would be:

• Built-in exporting of html within the editor, keeping the content consistent with the size of PDF. Currently, tables within the editor are only able to be exported via a workaround where CSS styles have to be applied outside of the editor. (Also, entering data into tables on the editor is very inconsistent - after a few characters, the cursor jumps to the last cell.
• Pagination Support: Header/Footer, page numbers, page breaks. Currently, header and footer functionality is not possible within the editor/PDF export combo (unless there is another workaround possible). Also, depending on what scale is set for the PDF Export component, content will often run off the side of the page on the exported PDF. It would also be useful to have physical page breaks represented somehow on the editor, either through multiple pages or a line separating them. Unless you manually place the page breaks on certain elements within the editor content, there is no way to see when they will appear. 

These features are crucial to our project and would be very much appreciated.

Thanks,

Aidan

It would be nice to have access to a selectionChange event in the autocomplete similar to the other dropdowns. This way when binding against arrays of complex objects, we could receive the whole object selected instead of the single value property out of it.