D. K. Kraft wrote:
With patience akin to a cat's, chicagofan, on 10/17/2009 5:37 PM typed:
D. K. Kraft wrote:
Further testing of SM 2.0 RC1 behavior on Win XP SP3 with a migrated
profile from SM 1.1.18:

In 1.1.18, when a message has been viewed (e.g. clicked on), it is
automatically (and logically) marked as "read." This is true for both
mail and news.

SM 2.0 RC1 doesn't follow the above behavior, instead keeping a viewed
message as "unread" no matter how many times it's clicked upon. I have
the pref regarding auto-marking a message as read (Mail& Newsgroups |
Message Display | General | Automatically mark messages as read)
unticked, as I don't want messages to be marked as read until I've read
them. Be that as it may, 2.0 *should not* be behaving in the observed
fashion AFAICT--messages *should* be marked as "read" once they have been
viewed.

In comparison, 1.1.18 only has a time interval setting for marking
messages (Wait [] seconds before marking a message as read), and it's
unclear if this pertains to automatically doing so, or doing so after a
message has been viewed. Since I've never used this pref in SM 1.1.x, I
can't speak to a comparison of behavior.

I think this is the bug you wanted to see filed, and it has been
resolved, in RC2.    :)

https://bugzilla.mozilla.org/show_bug.cgi?id=514876

<snort!>  Nope, it's not even the ghost of a bug.  It's an epic fail on my
part to comprehend the pref under Mail & Newsgroups | Message Display |
General, which is the following (where [] represents a checkbox, and () a
radio button):

[] Automatically mark messages as read:
      () Immediately on display

To get the behavior I have now with 1.1.18--where a message is marked as read
*upon display*--I need to check that checkbox and tick the radio button.

[bangs head on keyboard]

Epic fail on follows instructions.  Epic fail on reading instructions.  I
think I need to take a break, step back, and not try so hard...  Or
something...

And I'm supposed to be the schmart one in my family --

You do have a valid point that the 2.0 defaults would cause less noise if they were the same as 1.1.xx in as far as is possible, and if profile import were a tad more biased toward what used to happen.

The only thing bugging me now is mail/news opening extra tabs, and I'm sure something I do causes that. Well, reasonably sure, anyway, I'm not even at the reproduce stage yet, much less the 'file a bug' stage, it's likely to be user error because of a new feature.

--
Bill Davidsen <david...@tmr.com>
  "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to