Closed
Bug 834689
Opened 11 years ago
Closed 11 years ago
Work - Add multi-selection to richgrid as stop-gap
Categories
(Firefox for Metro Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: sfoster, Assigned: sfoster)
References
Details
(Keywords: feature, platform-parity, Whiteboard: feature=work)
Attachments
(1 file, 1 obsolete file)
Cross-slide and multiple-selection are slated for the new proposed tilegroup widget. In order to unblock the implementation of the contextual appbar and the views & tiles actions that depend on it, we need a stop-gap measure that adapts the existing richgrid with enough to test and work through contextual-action flows
Assignee | ||
Comment 1•11 years ago
|
||
This is just the richgrid/richgrid item changes which allow us to fire a selectionchange event on the grid and the user to toggle tile selection (via contextmenu/right-click/long-press until cross-slide is implemented). I'm still fighting getting tests to run in the xul file so I'll land that seperately if/when its ready.
Attachment #708080 -
Flags: review?(mbrubeck)
Assignee | ||
Comment 2•11 years ago
|
||
Addressed feedback to use selectedItems property instead of QSA in clearSelection. I left the selectionchange event behavior as-is, rather than calling some method on the controller. This seems more like the expected, DOM-ish behavior and we can stop events bubbling to avoid them being global if it becomes a perf. problem.
Attachment #708080 -
Attachment is obsolete: true
Attachment #708080 -
Flags: review?(mbrubeck)
Attachment #708087 -
Flags: review?(mbrubeck)
Updated•11 years ago
|
Attachment #708087 -
Flags: review?(mbrubeck) → review+
Assignee | ||
Comment 3•11 years ago
|
||
https://hg.mozilla.org/projects/elm/rev/1d467cd2359b
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
OS: Windows 8 Metro → Windows 8.1
You need to log in
before you can comment on or make changes to this bug.
Description
•