Ticket #1795 (closed defect: fixed)

Opened 5 months ago

Last modified 5 months ago

Tree.setValue() behaves unexpectedly

Reported by: Henrik Paul Owned by: Marko Gronroos
Priority: minor Milestone: User Interface Library 5.2.3
Component: gwt-adapter-client Version: 5.2.1
Keywords: Cc:
Known Issue description:
Hours estimate: Deadline (dd.mm.yyyy):
Known Issue version (since): Known Issue title:
Hours done: Depends to:
Affects documentation: no
Known Issue workaround:
Affects release notes: no Contract:

Description

If setValue() is used to set the tree's value to something that is not yet expanded, the tree's value doesn't change when clicking on other elements. The value is still correctly highlighted once you expand the tree manually (but still doesn't change values).

If you expand the tree before setting the value, the tree works as expected.

Change History

Changed 5 months ago by Henrik Paul

Clarification: the tree's value is set correctly with setValue() in both cases. The former case just doesn't seem to fire a ValueChangeEvent?.

Changed 5 months ago by Joonas Lehtinen

  • priority changed from undefined to minor
  • component changed from undefined to gwt-adapter-client
  • milestone set to User Interface Library 5.2.3

Changed 5 months ago by Marc Englund

  • status changed from new to closed
  • resolution set to fixed

ITree (client) threw, fixed in [4899]

Note: See TracTickets for help on using tickets.