Hi, Frank-Rainer Grahl! Thanks for writing, on 06 Mar 17 07:23:

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...

You could try with a new test profile. I doubt that running XP makes a
difference unless its about HTML5 content.

As I just said in a reply to Daniel:

since I do get that login page OK on my XP 32-bit FireFox 41, my
problem isn't finding a way to access it:  It's discovering why my
SM 40 on 32-bit XP cannot (exactly because it seems that, besides a
very efficient 'version-sniffing' from FM, there doesn't seem to be
any reason for that, and I'd like to understand why that happens).

So, even if I tried a new profile and it worked, I still wouldn't be much closer to discovering the reason for it not working now, and THAT's what I'd like.

There were really tons of changes between 2.40 and 2.46 and not only
in the Gecko engine. I ran all versions between 2.40 and 2.46 and
around 2.42 I noticed a considerable speed improvement. But some also
noticed a regression so you just need to try it out yourself.

Unless it's very noticeable, I wouldn't care too much about 'speed' -- and, as you said, it seems to vary depending on each specific system configuration, so that probably wouldn't motivate me either way.

As I said before, I don't have much free time right now (and one of the reasons is that I'm migrating to a dual-boot XP/W7 system, so discovering, and learning to handle, the differences about programs on these SOs (much more work than I expected) takes up much time.

I really would like (including for my own sake) to remember why I decided to keep on SM 40 for now, but I recall that it's something which is a 'no turning back': Sure, a backup can be restored, but once you start using the new one for everyday use, going back is very difficult and time-consuming -- and recall it was something I might only realize wasn't working for me some time onward... So, since I can upgrade any time (I kept SM 39 for quite some time before I felt safe going to 40), I decided to wait.

Other than the default search engine bug for which there is a workaround
and the Data Manager hang probably caused by old cruft in
webappsstore.sqlite (just rename or delete it) I am not aware of any
widespread problems with 2.46.

I don't think it was a "widespread problem", but it might be something which may not be important to many, but was a problem for some, and it seemed it might be so for me, too -- but, unfortunately, I can't recall what it was, and don't want to use my time now looking for it, and I'll be sure to keep an eye for anything which is relevant to this, and post it here if I do find it within a reasonable time period.

I am more concerned now with 2.48+ because there are some reports of
it crashing when using mail and news. Hits some users all the time
and others never. Mostly on Linux.

Something's tugging at my memory on reading that, suggesting the problem I mention was a consequence of something done in Gecko/FF, which made a change in SM 46, causing that unwanted result (so, it wouldn't be changed on any version after 46)...

Absolutely no software is "error free", either, and all SM (and FF)
versions have always been free so that's not relevant too...

Was mean't as a joke :)

So was my reply!  :-))

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...

Yes but I had some problems with pages in 2.40 which did go away in
later versions. There were really improvements in HTML5 compatibility
and the JS interpreter.

Noe THAT is somewhat encouraging, and it might be compatible with my not getting a login denial on my XP 32-bit FireFox 41, but getting it on my XP 32-bit SeaMonkey 40!

--
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

Reply via email to