Hi, Frank-Rainer Grahl! Thanks for the quick reply:
Meaning that you couldn't do that in 2.40?
Meaning I didn't even try.
So, maybe it has absolutely nothing to do with the SM version, but it's
something in your system that is different from mine (eg, I'm using XP
on this machine; I'll try it on a W7 one when I get the chance): If you
were running 2.40, perhaps you would also have no problems with this site...
From what I've seen in this and other forums, I think I'll stay on 2.40
until I have very strong reasons to do otherwise...
2.46 is not error free but miles ahead of 2.40. Backup you profile and
just try it. Its free and 2.40 is completely unsupported now. If you
encounter an error which hasn't been reported just do so.
"Unsupported" in this context is meaningless: What kind of 'support' do
we have for 2.46? Besides forums (which should work equally well for
2.40), I doubt there's any hope of any one-on-one support for any SM
version, now and in the foreseeable future: If the devs manage to keep
up with needed new versions, we'll all be very thankful (as am I , always).
Absolutely no software is "error free", either, and all SM (and FF)
versions have always been free so that's not relevant too...
You do imply a valid query: What, exactly, led me to decide to not
migrate to 2.46 now? While I have seen many advantages (though they
hardly sound "miles ahead of 2.40", IMHO), there were a few points which
led to this decision, but I've now 'deleted' them from my 'memory',
leaving only the conclusion; since that seems worthwhile, I will try to
recover exactly which were these points (I seem to recall just 2, but
enough to counterbalance any not-important-to-me advantages), and post
it here when I do, but I don't have much free time right now, so that
may take a while.
So, I'm interested again: What changes after 2.40 would lead to the
Fastmail 'new' site opening, while it didn't in 2.40?
Probably nothing in SeaMonkey but take your pick and see if you can find
a Gecko change which did it. Only a few thousand files changed :)
Ha, ha!
Seriously probably some new js features did the trick.
Since it isn't clear that the version difference had anything to do
with it, that's just a speculation...
If you change cookie settings at most a browser restart is required.
Should pick them up even so but you never know...
If a different OS (W7) and/or reboot with cookie rules have any effect,
I'll let you know.
I still hope to fond someone who is actually a FastMail and SM user, and
has already faced this problem.
--
Thanks beforehand for your attention, and I hope to hear from you soon.
s) Alexander Yudenitsch <[email protected]>
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
