Opened 10 years ago
Closed 10 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
- Create selectable items in a hierarchy.
- Click on the child item.
- Bug: the parent is selected if the click is directly on the child selectee.
Change History (6)
comment:1 follow-up: 2 Changed 10 years ago by
Owner: | set to epowers |
---|---|
Status: | new → pending |
comment:2 Changed 10 years ago by
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.
comment:3 follow-up: 4 Changed 10 years ago by
Status: | new → pending |
---|
Do you have examples of existing tools that behave this way?
comment:4 Changed 10 years ago by
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.
comment:5 Changed 10 years ago by
Status: | new → pending |
---|
Well, with only one request for nested selectable support, I don't think we'd want to implement this.
comment:6 Changed 10 years ago by
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!
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.