#9914 closed bug (invalid)

Opened March 11, 2014 06:34PM UTC

Closed March 27, 2014 09:10AM UTC

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/

Attachments (0)
Change History (6)

Changed March 12, 2014 12:44PM UTC by tj.vantoll comment:1

owner: → epowers
status: new → pending

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.

Changed March 12, 2014 04:46PM UTC by epowers comment:2

status: pending → new

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.

Changed March 12, 2014 04:51PM UTC by scottgonzalez comment:3

status: new → pending

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

Changed March 12, 2014 06:46PM UTC by epowers comment:4

status: pending → new

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

Changed March 12, 2014 07:02PM UTC by scottgonzalez comment:5

status: new → pending

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

Changed March 27, 2014 09:10AM UTC by trac-o-bot comment:6

resolution: → invalid
status: pending → closed

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!