Ticket #821 (closed defect: fixed)

Opened 18 months ago

Last modified 17 months ago

Clicking a component in a Table row causes change in selection

Reported by: Marko Gronroos Owned by: Matti Tahvonen
Priority: major Milestone: 4.0.3
Component: Server-side framework Version: 4.0.2
Keywords: Cc: tomi.virtanen@…
Known Issue description: Table component which has other components embedded, e.g. buttons, has a side effect of selecting the row if embedded component such as button is clicked.
Hours estimate: 1 Deadline (dd.mm.yyyy):
Known Issue version (since): 4.0.0 Known Issue title: Table containing other components has a state change side effect
Hours done: Depends to:
Affects documentation: no
Known Issue workaround:
Affects release notes: yes Contract:

Description

When a Table is selectable and contains a column with, for example, checkboxes (Buttons), clicking on a checkbox also causes selection of the row. This is unwanted behaviour. I think the same applies to all kinds of components that could be included in tables.

This is problematic in a case where selecting an item in a table causes a heavy operation, such as loading stuff in other part of the screen, or even opening a new screen that replaces the table, in which case the problem makes the components in the table completely unusable. For example, the rows could be a list of persons and selecting them would open information about the persons in other part of the screen, or by replacing the table itself. On the other hand, it would be necessary to be able to select multiple persons for, for example, deletion.

Change History

Changed 18 months ago by Matti Tahvonen

  • owner changed from Jani Laakso to Matti Tahvonen
  • hours_left set to 2
  • status changed from new to assigned
  • priority changed from undefined to major

We'd need to check if event is coming from a child component.

Changed 18 months ago by Matti Tahvonen

  • status changed from assigned to closed
  • hours_left changed from 2 to 0
  • resolution set to fixed

in [1928]

Changed 17 months ago by Jani Laakso

  • milestone set to 4.0.3

Changed 17 months ago by Jani Laakso

  • milestone deleted

Removing milestone as fix done for TK5 only.

Changed 17 months ago by Matti Tahvonen

  • milestone set to 4.0.3

Dought, my bad, wrong cs number. [1922]

Changed 17 months ago by Jani Laakso

  • known_issue_since set to 4.0.0
  • known_issue_desc modified (diff)

Changed 17 months ago by Jani Laakso

  • known_issue_title set to Table containing other components has a state change side effect

Changed 17 months ago by Matti Tahvonen

  • cc tomi.virtanen@… added
  • hours_left changed from 0 to 1
  • status changed from closed to reopened
  • resolution deleted

Tomi Virtanen reported that in -removed- (-removed-?) they rely on selecting rows by clicking label components in rows. Apparently there is a need to let some click events continue and stop most. I'll add a check which passes label components click events through.

Changed 17 months ago by Matti Tahvonen

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

in [2076]

Note: See TracTickets for help on using tickets.