Opened 5 years ago

Closed 5 years ago

#9914 closed bug (invalid)

Selectable: fix mousedown on hierarchical selectable items

Reported by: epowers Owned by: epowers
Priority: minor Milestone: none
Component: ui.selectable Version: 1.8.19
Keywords: Cc:
Blocked by: Blocking:

Description

  1. Create selectable items in a hierarchy.
  2. Click on the child item.
  3. Bug: the parent is selected if the click is directly on the child selectee.

See: http://jsfiddle.net/epowers/a8DY2/

Change History (6)

comment:1 Changed 5 years ago by tj.vantoll

Owner: set to epowers
Status: newpending

Well this is actually a feature request because the selectable interaction does not support nested selectables.

What is your use case for needing selectables within selectables? This seems a bit odd to me.

comment:2 in reply to:  1 Changed 5 years ago by epowers

Status: pendingnew

The use case is adding selectable to elements in an xhtml editor. User directly selects (multiple) items in the document for drag/resize/copy/etc at different levels of the xml document hierarchy.

Selectable is necessary in this situation because it already coordinates (through ui.widget/ui.mouse) mouse interaction with other components: draggable, droppable, resizable. As well, it provides a lasso tool.

comment:3 Changed 5 years ago by Scott González

Status: newpending

Do you have examples of existing tools that behave this way?

comment:4 in reply to:  3 Changed 5 years ago by epowers

Status: pendingnew

I haven't researched use of selectable in other tools, so I do not know of an existing tool that exercises this problem.

comment:5 Changed 5 years ago by Scott González

Status: newpending

Well, with only one request for nested selectable support, I don't think we'd want to implement this.

comment:6 Changed 5 years ago by trac-o-bot

Resolution: invalid
Status: pendingclosed

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!

Note: See TracTickets for help on using tickets.