Opened 3 years ago

Closed 3 years ago

#1488772 closed Bugs (fixed)

Deselecting first message of collapsed thread does not deselect children

Reported by: dj1yfk Owned by: alec
Priority: 5 Milestone: 0.9-beta
Component: User Interface Version: 0.8.2
Severity: normal Keywords: threads, selection, children


When selecting a range of messages in the message list (by first clicking one single message, and then clicking on another one below or above, while holding down Shift), collapsed threads (with all of their children) that are somewhere within this range appear as selected and if an action is performed, e. g. deleting the selected range of messages, the whole thread is deleted, as expected.

If now, after selecting such a range, I deselect a collapsed thread by clicking the first (and only visible) message of it while holding down Ctrl, it appears that actually only this very first message of the thread is deselected. If I now press "Delete" only the first message of this thread survives, the children are still selected and are deleted. I'd have expected that the children are also deselected.

Tested with the latest version on (0.8.2) and verified on 0.7.2 too (IE8, Firefox 16.0.1)

Change History (5)

comment:1 Changed 3 years ago by alec

  • Milestone changed from later to 0.9-beta

comment:2 Changed 3 years ago by alec

  • Owner set to alec

comment:3 Changed 3 years ago by alec

  • Resolution set to fixed
  • Status changed from new to closed

comment:4 Changed 3 years ago by maharaja

  • Resolution fixed deleted
  • Status changed from closed to reopened

i think this commit broke the deletion of collapsed threads, at least for 0.8.

reverting to commit a0682b56d174bc801916f60f85f31f0513b660c6 restores the functionality.


comment:5 Changed 3 years ago by alec

  • Resolution set to fixed
  • Status changed from reopened to closed
Note: See TracTickets for help on using tickets.