Re: WINDOWS 10 UPGRADE WITH SEAMONKEY V 2.33.1

[Ray Davison]

BER wrote:

Hello,
Please see my email below. I have decided to upgrade to Windows 10. Will 
Version 2.33.1 work with Windows 10 and should I be able to upgrade to 
the latest version of Seamonkey?

Thank you
Brenda


Yes SM suns on W 10.  However, starting with Netscape, I have never 
caused or allowed any Mozilla app to write over another version.  Newer 
is not always better, and combining versions can sometimes be 
"interesting"  I install each version in it's own space, at a place of 
my choosing.  And never on a boot partition.  And when I decide I prefer 
a later version to an earlier, I delete the earlier; and not before.


I have had some issues with recent versions.  As a result I currently 
have eight SM versions and two Pale Moon.  Some SM versions share a 
profile and some have their own.  All SM versions that I configure to 
access email all use the same mail files.


Mozilla apps are very friendly in how they can be managed.

Ray

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Google.com difference with SeaMonkey compared to Firefox

[NFN Smith]

no...@nonospam.org wrote:
For the last couple of months, the appearance of the main Google website 
on SeaMonkey has been different from what it has been for years. Search 
results are presented in individual boxes, and the website just looks 
strange.


I haven't seen any changes recently, but I rarely go to google.com, and 
I also normally leave the scripting for google.com inactive (via 
NoScript) unless I encounter something that requires it (most often, 
other sites that offer search and use Google's searching).


That said, I've found that at www.google.com, if using a standard 
Seamonkey User Agent display, the search bar's display is a little odd, 
where cursor and text is displayed about half a line offset above where 
it should be.  I found that that goes away if I show a stock Firefox UA 
string (rather than Seamonkey's UA of Firefox with Seamonkey's ID tagged 
at the end).


Even though I'm a fan of changing UA with PrefBar, I've found that this 
is one site (among several) where I'd rather not have to remember to 
change the UA when I visit, then remember to change back when I'm done, 
because UA spoofing also changes the User-Agent header in mail.  (I 
notice that your message shows Firefox 86, rather than Seamonkey). 
Thus, for this one, I prefer to do permanent site-specific spoofing, and 
in about:config, I have a line in prefs.js that sets 
general.useragent.override.google.com to show:


   Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 
Firefox/78.0


This is another example of a website which works differently with 
SeaMonkey than it does with Firefox. Changing the user agent string is a 
workaround, but why should this be required?


It's something specific to Google, and why they do it isn't obvious. 
I've heard indications of issues at YouTube that require similar 
spoofing.  I haven't seen that myself, but I don't do a lot at YouTube.


Although my observation is that a Firefox UA string that includes 
additional text (which is normal for browsers that are derived from 
Firefox but not actually Firefox, such as Seamonkey, PaleMoon and 
Waterfox) seems to confuse Google, I haven't actually tested either 
PaleMoon or Waterfox.


In the grand scheme of things, I think it's one of those places where 
the number of people running Firefox browsers is small enough (the 
function equivalent of a rounding error), that Google doesn't really 
care, one way or another.  They'll do the necessary work to make Firefox 
behave correctly, and if it's not Firefox, not worth the effort.


Smith


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: WINDOWS 10 UPGRADE WITH SEAMONKEY V 2.33.1

[WaltS48]

On 3/21/21 3:18 PM, BER wrote:

Hello,
Please see my email below. I have decided to upgrade to Windows 10. 
Will Version 2.33.1 work with Windows 10 and should I be able to 
upgrade to the latest version of Seamonkey?

Thank you
Brenda


Upgrading has been broken for several versions so you need to do a new 
installation.


The SeaMonkey project is proud to present SeaMonkey 2.53.6: The new 
release of the all-in-one Internet suite is available for download now 
! 2.53.6 is an incremental 
update from the 2.53.x branch and incorporates a number of changes, 
including improved usability of multiple mailboxes/folders selection, 
Greek localization, and fixes from the underlying platform code. 
*Before installing it make a full backup of your profile and 
thoroughly read and follow the Release Notes 
*. 


At the very top of those Release Notes it states:

*You MUST absolutely do a full backup of your profile before upgrading 
from a version earlier than SeaMonkey 2.53.1. This version of 
SeaMonkey makes changes to your profile that can't be reverted in 
cases where you need to go back to the older version.*


*Automatic upgrades from previous versions are currently disabled for 
this release. Please download the full installer from the downloads 
section and install SeaMonkey 2.53.6 manually over the previous version.*




Hope that helps.

--
OS: Fedora 33 Workstation - Gnome Desktop
https://www.thunderbird.net/en-US/get-involved/

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Google.com difference with SeaMonkey compared to Firefox

[Rubens via support-seamonkey]

no...@nonospam.org wrote on 21/03/2021 14:27:

For the last couple of months, the appearance of the main Google website on 
SeaMonkey has been different from what it has been for years. Search results 
are presented in individual boxes, and the website just looks strange.

I've done some troubleshooting and here is what I've observed:

1. When entering google.com on Firefox v86.0.1, the site appears normal.

2. When entering google.com on SeaMonkey v2.53.5.1, the site has the strange 
appearance described above. The site address showing in the title box is 
https://www.google.com/#spf=1616331365185 even though only 
https://www.google.com was entered.

3. If I change the SeaMonkey user agent to Firefox 86.0(Using the PrefBar 
extension) and reload the page, the appearance returns to normal, even though 
#spf=1616331987062 is still at the end of the site address.

4. Removing #spf=1616331987062 and reloading the page make the site work 
correctly.

5. Changing the user agent back to Real UA and reloading the page again causes 
the strange appearance and the site address goes back to 
https://www.google.com/#spf=1616332459516

This is another example of a website which works differently with SeaMonkey 
than it does with Firefox. Changing the user agent string is a workaround, but 
why should this be required?

John


I also observe this, even still using SeaMonkey 2.49.5.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey