Ticket #666 (closed defect: invalid)

Opened 21 months ago

Last modified 9 months ago

Tree component keeps last selection after changing selectable-property to false

Reported by: Mikael Vappula Owned by: Jani Laakso
Priority: undefined Milestone: User Interface Library 5.2.0 RC
Component: Server-side framework Version: 4.0.1-rc
Keywords: Cc:
Known Issue description:
Hours estimate: Deadline (dd.mm.yyyy):
Known Issue version (since): Known Issue title:
Hours done: Depends to:
Affects documentation: yes
Known Issue workaround:
Affects release notes: no Contract:

Description

Tree shows last selected nodes also after setting selectable property false. Happens also in multiselect mode. Found in 4.0.1-rc8

Change History

Changed 12 months ago by Joonas Lehtinen

  • milestone set to User Interface Library 5.1.0 RC

Changed 10 months ago by Marc Englund

  • status changed from new to closed
  • resolution set to invalid
  • affects_documentation set

This is a feature, not a bug: leaving as-is allows the programmer to make a non-selectable Tree with selected nodes, and one can null the selection by saying tree.setValue(null) before setSelectable(false).

(however, the client ignores selectmode="none" completely right now, bug this is a separate ticket)

Changed 9 months ago by Joonas Lehtinen

  • milestone changed from User Interface Library 5.1.2 to User Interface Library 5.2.0

Milestone User Interface Library 5.1.2 deleted

Note: See TracTickets for help on using tickets.