Re: Automatic Spell Check with v.2.39
Henrik37 wrote: I recently installed SM v.2.39 on a new, larger, hard drive. My memory is that there is way to enable forced spell checking with newly composed e-mail messages prior to sending them. The problem is that I can't find out whether this feature exists in v.2.39 and how to enable it or whether my memory is simply faulty. I think it's in the same place as in other recent versions. On my 2.40, it's at: Edit | Preferences | Appearance | Spelling ... [x] Check spelling before sending [x] Check spelling as you type If the default language isn't the one you want, click the button that shows the language and you'll see any other installed languages, plus the option "Download more dictionaries..." -- War doesn't determine who's right, just who's left. -- Paul B. Gallagher ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Automatic Spell Check with v.2.39
I recently installed SM v.2.39 on a new, larger, hard drive. My memory is that there is way to enable forced spell checking with newly composed e-mail messages prior to sending them. The problem is that I can't find out whether this feature exists in v.2.39 and how to enable it or whether my memory is simply faulty. Help ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default
David E. Ross wrote: On 9/5/2016 12:17 PM, Ray_Net wrote: Jerry wrote on 04/09/2016 15:12: I've been following this thread with much interest, since I had the same problem with CHASE. I am happy to report that as of today I can now log into my Chase account with Seamonkey 2.45 on Linux. I have the User Agent Switcher addon installed. In that I entered a new User Agent I named Seamonkey. For the User Agent string I have "Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0". I removed Seamonkey from the end of the string (taking the clue from David's last post), and now it works! Oh, I did go in and delete all chase.com cookies before I tried to log in to Chase. Thanks to all of you for not giving up and sorting this out! As I said before .. SM must ONLY have Firefox in his User Agent String ... ... when "Advertise Firefox compatibility" is checked. No, that would indicate Firefox is the browser. "Advertise Firefox compatibility" should indicate both SeaMonkey and Firefox. Actually, when I use PrefBar's user agent spoofing, my user agent strings is Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 SeaMonkey/2.40, NOT Firefox/45.0 If I were to enable "Advertise Firefox compatibility", the string would be Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40 Many cases of user agent sniffing merely look for "Firefox" without considering the rest of the string. It would be better to look for "Gecko", in which case all this discussion would be moot. Of course, that would have to change when Gecko is abandoned in favor of Servo; but that replacement is not yet certain. Does not the general.useragent.overide.chase.com;Mozilla/5.0 (Windows NT 6.1; rv:43.0) Gecko/20100101 Firefox/43.0 not work anymore? It used to work in about:config -- You either teach people to treat you with dignity and respect, or you don't. This means you are partly responsible for the mistreatment that you get at the hands of someone else. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default
On 9/5/2016 12:17 PM, Ray_Net wrote: > Jerry wrote on 04/09/2016 15:12: >> I've been following this thread with much interest, since I had the >> same problem with CHASE. I am happy to report that as of today I can >> now log into my Chase account with Seamonkey 2.45 on Linux. >> >> I have the User Agent Switcher addon installed. In that I entered a >> new User Agent I named Seamonkey. For the User Agent string I have >> "Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101 >> Firefox/43.0". I removed Seamonkey from the end of the string (taking >> the clue from David's last post), and now it works! >> >> Oh, I did go in and delete all chase.com cookies before I tried to log >> in to Chase. >> >> Thanks to all of you for not giving up and sorting this out! >> >> >> >> > As I said before .. SM must ONLY have Firefox in his User Agent String ... > ... when "Advertise Firefox compatibility" is checked. > No, that would indicate Firefox is the browser. "Advertise Firefox compatibility" should indicate both SeaMonkey and Firefox. Actually, when I use PrefBar's user agent spoofing, my user agent strings is Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 SeaMonkey/2.40, NOT Firefox/45.0 If I were to enable "Advertise Firefox compatibility", the string would be Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40 Many cases of user agent sniffing merely look for "Firefox" without considering the rest of the string. It would be better to look for "Gecko", in which case all this discussion would be moot. Of course, that would have to change when Gecko is abandoned in favor of Servo; but that replacement is not yet certain. -- Donald Trump claims everyone likes him. Does that include his ex-wives? How about the students who discovered that their education at Trump University was worthless? And how about the contractors, suppliers, and employees he stiffed in his several bankruptcies? ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default
Jerry wrote on 04/09/2016 15:12: I've been following this thread with much interest, since I had the same problem with CHASE. I am happy to report that as of today I can now log into my Chase account with Seamonkey 2.45 on Linux. I have the User Agent Switcher addon installed. In that I entered a new User Agent I named Seamonkey. For the User Agent string I have "Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0". I removed Seamonkey from the end of the string (taking the clue from David's last post), and now it works! Oh, I did go in and delete all chase.com cookies before I tried to log in to Chase. Thanks to all of you for not giving up and sorting this out! As I said before .. SM must ONLY have Firefox in his User Agent String ... ... when "Advertise Firefox compatibility" is checked. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
