Alexander Yudenitsch wrote:
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...
You could try with a new test profile. I doubt that running XP makes a
difference unless its about HTML5 content.
"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).
Every bug report is read even if it stays unconfirmed. If a report is against
2.40 and can't be easily reproduced in 2.46+ I usually ignore it and/or ask
for verifying it with a supported version. 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.
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 :)
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.
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. That doesn't mean it will work for you so backup your profile but I ran
it during the whole beta phase and even gave copies to 2 friends which were
happy with it. 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.
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.
FRG
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
