Last Comment Bug 540252 - WARNING: goofy tree selection state: two ranges are adjacent!: 'endFirstRange == startRange' with test_delete_multiple_messages_with_first_selected_message_open in test-deletion-with-multiple-displays.js
: WARNING: goofy tree selection state: two ranges are adjacent!: 'endFirstRange...
: fixed-seamonkey2.0.4
Product: MailNews Core
Classification: Components
Component: Backend (show other bugs)
: Trunk
: All All
-- minor (vote)
: Thunderbird 3.1b1
Assigned To: Siddharth Agarwal [:sid0] (inactive)
Depends on:
  Show dependency treegraph
Reported: 2010-01-17 01:22 PST by Siddharth Agarwal [:sid0] (inactive)
Modified: 2010-03-18 06:41 PDT (History)
1 user (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---

patch (1.08 KB, patch)
2010-01-17 01:22 PST, Siddharth Agarwal [:sid0] (inactive)
standard8: review+
standard8: superreview+
standard8: approval‑thunderbird3.0.2+
Details | Diff | Splinter Review

Description User image Siddharth Agarwal [:sid0] (inactive) 2010-01-17 01:22:48 PST
Created attachment 422065 [details] [diff] [review]

This should clearly be the other way round -- we need to warn if the first end index is equal to this start index, i.e. if endFirstRange == startRange, i.e. if endFirstRange != startRange is false.

This is a fix to a debug-only assertion, so I don't think it can be tested (apart from running the above-mentioned test in debug mode).
Comment 1 User image Mark Banner (:standard8) 2010-02-01 03:36:49 PST
Comment on attachment 422065 [details] [diff] [review]

Yep some things you just can't test (and I'd argue this isn't worth testing anyway).
Comment 2 User image Siddharth Agarwal [:sid0] (inactive) 2010-02-08 23:01:38 PST

I also fixed the indentation of the line below it.
Comment 3 User image Siddharth Agarwal [:sid0] (inactive) 2010-02-08 23:02:17 PST
Comment on attachment 422065 [details] [diff] [review]

trivial npotdb fix.
Comment 4 User image Siddharth Agarwal [:sid0] (inactive) 2010-02-10 23:39:16 PST
Comment 5 User image Mark Banner (:standard8) 2010-02-16 12:59:28 PST
Verified fixed for 1.9.1 by code inspection (and doesn't affect release builds).

Note You need to log in before you can comment on or make changes to this bug.