Re: Third-party cookie question
WaltS48 wrote: On 12/13/2014 11:10 PM, Paul B. Gallagher wrote: WaltS48 wrote: On 12/13/2014 10:36 PM, Paul B. Gallagher wrote: WaltS48 wrote: Have you tried the Allow cookies for the originating site only (no third-party cookies) setting? I refer you to my original query, which you apparently have not read. Slipped my mind when replying. Did you try a test profile, visit no web sites, check cookies. What did you find? See the response I gave to »Q« 16 minutes ago downthread. So you didn't try a test profile. Okay, I started my SeaMonkey with the test profile. Had the 2 Google cookies I mentioned earlier. Cleared cookies, history, cache, and everything else I could check. Restarted SeaMonkey with the test profile, had the 2 Google cookies again, repeated the Clear history, restart process and the 2 Google cookies come back on every restart. Let me set Block Cookies from This Website, the website being http://www.seamonkey-project.org/start/, clear history, restart and they're back. Block Cookies from The Website under Tools Cookie Manager is still enabled. Let me try checking When removing, block the listed websites from setting future cookies in the Cookies tab of Data Manager and using Remove there also. APPLAUSE! No Google cookies! That was an adventure. :) An interesting one, but not really relevant to my query. I don't get Google cookies on startup as you do, so I don't need to cure a problem I don't have. I don't get them merely by launching the browser as you do, so I don't need to cure a problem I don't have. (I don't understand what clearing history has to do with cookies, but be that as it may...) I do get precisely one Google cookie by visiting nhl.com, and since Google isn't the originating site, that makes them third-party cookies, which SeaMonkey claims it's blocking. How can Google set a third-party cookie from nhl.com when my setting says to reject third-party cookies? I must conclude that SM's cookie-handling routine is not working correctly. -- 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
Web page loading and display problem
I'm running SeaMonkey 2.30 under Windows 7 Home Premium (Service Pack 1) on a Toshiba Satellite L455 laptop with 4G of memory. When I load a new web page - either by clicking hyperlink or bookmark or typing in URL, only the 'top screen' of the page can be read, and I have to click the 'reload' button to be able to scroll down and read the rest of the page. This is annoying. Also, when I put the computer into 'sleep mode', upon reawakening, the web pages loaded by SeaMonkey are again frozen and need to be 'reloaded'. As I must work while commuting or in places without fast or reliable 'net connections or WiFi, this is much more than just annoying. How can I correct this problem ? Thanks for your help with this. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Google/Yahoo
On 14/12/14 14:39, Paul B. Gallagher wrote: Daniel wrote: On 14/12/14 06:22, Paul B. Gallagher wrote Snip That's problematic for me because I do have a gmail account and sometimes use it to login to other sites (as soon as I'm done, I clear the cookies and resume living privately). nhl.com is not one of those, and AFAIK has not been bought by Google the way Yahoo has. Sorry, Paul, are you suggesting Google owns Yahoo?? I would have thought there would have been some sort of anti-competition thing going on if this were the case! Sorry, typo for YouTube. O.K., you're excused!! ;-) -- Daniel User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:32.0) Gecko/20100101 SeaMonkey/2.29 Build identifier: 20140829003846 or User agent: Mozilla/5.0 (X11; Linux x86_64; rv:34.0) Gecko/20100101 SeaMonkey/2.31 Build identifier: 20141020202138 ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Seamonkey 2.31 chase web site
David H. Durgee wrote: Marisa Ciceran wrote: Same problem here as of the start of this weekend. I've been on the phone several times with Chase support about this and this time the agent I spoke to said he sent a note to their compatibility developers. I am on 64-bit Windows 7 Pro on on ASUSI7 4790k processor. Marisa NoOp wrote: On 12/08/2014 10:21 AM, Lemuel Johnson wrote: On 12/8/2014 10:52 AM, NoOp wrote: On 12/08/2014 05:23 AM, J. Weaver Jr. wrote: Ken Rudolph wrote: Ron wrote: Just got the 2.31 upgrade now I can't log in to my account on chase.com I hit logon it just reloads the log on page. Works in IE and Seamonkey 2.30 Same thing happening here. This is frustrating. Can I go back to Seamonkey 2.30? Or maybe spoof the browser to firefox (which used to work when bank sites didn't accept SeaMonkey)? Same problem here: worked great with IE 2.30, not at all with 2.31. sigh Is there a Bugzilla entry for this yet? -JW https://bugzilla.mozilla.org/show_bug.cgi?id=109471 ( Unable to login at chase.com due to NS_ERROR_FAILURE (SeaMonkey only)) and for reference, here is a previous one that was fixed last year: https://bugzilla.mozilla.org/show_bug.cgi?id=924025 (Unable to log in at chase.com) I believe that's actually https://bugzilla.mozilla.org/show_bug.cgi?id=1094714 Lem Johnson You are correct - thanks for the catch! Gary Well, that is enough reason to hold back from upgrading for me! I have a Chase account, so until this is fixed or there is a work-around this one is a show-stopper. Dave Well, the cause is now known, and it *is* possible to access the site using SM 2.31. Comment 21 in the 1094714 bug report has it. The steps recommended by Phillip Chee solved the problem for me (Ken Jarman), Thanks Phillip: 1. Restart SeaMonkey. DO NOT go to chase.com YET 2. Open the Error Console (CTRL-SHIFT-J) 3. Evaluate: Components.utils.import(resource://gre/modules/Webapps.jsm); 4. Try to login to chase.com One hell of a workaround. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Web page loading and display problem
johndesmond.busin...@gmail.com wrote: I'm running SeaMonkey 2.30 under Windows 7 Home Premium (Service Pack 1) on a Toshiba Satellite L455 laptop with 4G of memory. When I load a new web page - either by clicking hyperlink or bookmark or typing in URL, only the 'top screen' of the page can be read, and I have to click the 'reload' button to be able to scroll down and read the rest of the page. This is annoying. Also, when I put the computer into 'sleep mode', upon reawakening, the web pages loaded by SeaMonkey are again frozen and need to be 'reloaded'. As I must work while commuting or in places without fast or reliable 'net connections or WiFi, this is much more than just annoying. How can I correct this problem ? Thanks for your help with this. go to SM 2.31b2 and *flash*, flash to become from http://adobe.com sincerely, -- Vink home:http://ciudadpatricia.com User agent: Mozilla/5.0 (X11; Linux x86_64; rv:34.0) Gecko/20100101 Firefox/34.0 SeaMonkey/2.31b2 Build identifier: 20141020202138 File: libflashplayer.so Path: /home/gerardjan/Downloads/seamonkey/plugins/libflashplayer.so Version: 11.2.202.425 State: Enabled Shockwave Flash 11.2 r202 ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Web page loading and display problem
GerardJan wrote: johndesmond.busin...@gmail.com wrote: I'm running SeaMonkey 2.30 under Windows 7 Home Premium (Service Pack 1) on a Toshiba Satellite L455 laptop with 4G of memory. When I load a new web page - either by clicking hyperlink or bookmark or typing in URL, only the 'top screen' of the page can be read, and I have to click the 'reload' button to be able to scroll down and read the rest of the page. This is annoying. Also, when I put the computer into 'sleep mode', upon reawakening, the web pages loaded by SeaMonkey are again frozen and need to be 'reloaded'. As I must work while commuting or in places without fast or reliable 'net connections or WiFi, this is much more than just annoying. How can I correct this problem ? Thanks for your help with this. go to SM 2.31b2 and *flash*, flash to become from http://adobe.com sincerely, adobe.com or http://macromedia.com -- Vink home:http://ciudadpatricia.com User agent: Mozilla/5.0 (X11; Linux x86_64; rv:34.0) Gecko/20100101 Firefox/34.0 SeaMonkey/2.31b2 Build identifier: 20141020202138 File: libflashplayer.so Path: /home/gerardjan/Downloads/seamonkey/plugins/libflashplayer.so Version: 11.2.202.425 State: Enabled Shockwave Flash 11.2 r202 ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Third-party cookie question
On 12/14/2014 03:28 AM, Paul B. Gallagher wrote: WaltS48 wrote: On 12/13/2014 11:10 PM, Paul B. Gallagher wrote: WaltS48 wrote: On 12/13/2014 10:36 PM, Paul B. Gallagher wrote: WaltS48 wrote: Have you tried the Allow cookies for the originating site only (no third-party cookies) setting? I refer you to my original query, which you apparently have not read. Slipped my mind when replying. Did you try a test profile, visit no web sites, check cookies. What did you find? See the response I gave to »Q« 16 minutes ago downthread. So you didn't try a test profile. Okay, I started my SeaMonkey with the test profile. Had the 2 Google cookies I mentioned earlier. Cleared cookies, history, cache, and everything else I could check. Restarted SeaMonkey with the test profile, had the 2 Google cookies again, repeated the Clear history, restart process and the 2 Google cookies come back on every restart. Let me set Block Cookies from This Website, the website being http://www.seamonkey-project.org/start/, clear history, restart and they're back. Block Cookies from The Website under Tools Cookie Manager is still enabled. Let me try checking When removing, block the listed websites from setting future cookies in the Cookies tab of Data Manager and using Remove there also. APPLAUSE! No Google cookies! That was an adventure. :) An interesting one, but not really relevant to my query. I don't get Google cookies on startup as you do, so I don't need to cure a problem I don't have. I don't get them merely by launching the browser as you do, so I don't need to cure a problem I don't have. (I don't understand what clearing history has to do with cookies, but be that as it may...) I do get precisely one Google cookie by visiting nhl.com, and since Google isn't the originating site, that makes them third-party cookies, which SeaMonkey claims it's blocking. How can Google set a third-party cookie from nhl.com when my setting says to reject third-party cookies? I must conclude that SM's cookie-handling routine is not working correctly. Sorry for the unnecessary noise. Then you need to file a bug report, or nhl.com is setting it and it isn't a third-party cookie. Since a lot appears to be broken in SeaMonkey lately, you could switch to Firefox. -- One of the millions of Firefox makes me happy users https://input.mozilla.org/en-US/feedback/firefox/ ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Seamonkey 2.31 chase web site
A Williams wrote: David H. Durgee wrote: Marisa Ciceran wrote: Same problem here as of the start of this weekend. I've been on the phone several times with Chase support about this and this time the agent I spoke to said he sent a note to their compatibility developers. I am on 64-bit Windows 7 Pro on on ASUSI7 4790k processor. Marisa NoOp wrote: On 12/08/2014 10:21 AM, Lemuel Johnson wrote: On 12/8/2014 10:52 AM, NoOp wrote: On 12/08/2014 05:23 AM, J. Weaver Jr. wrote: Ken Rudolph wrote: Ron wrote: Just got the 2.31 upgrade now I can't log in to my account on chase.com I hit logon it just reloads the log on page. Works in IE and Seamonkey 2.30 Same thing happening here. This is frustrating. Can I go back to Seamonkey 2.30? Or maybe spoof the browser to firefox (which used to work when bank sites didn't accept SeaMonkey)? Same problem here: worked great with IE 2.30, not at all with 2.31. sigh Is there a Bugzilla entry for this yet? -JW https://bugzilla.mozilla.org/show_bug.cgi?id=109471 ( Unable to login at chase.com due to NS_ERROR_FAILURE (SeaMonkey only)) and for reference, here is a previous one that was fixed last year: https://bugzilla.mozilla.org/show_bug.cgi?id=924025 (Unable to log in at chase.com) I believe that's actually https://bugzilla.mozilla.org/show_bug.cgi?id=1094714 Lem Johnson You are correct - thanks for the catch! Gary Well, that is enough reason to hold back from upgrading for me! I have a Chase account, so until this is fixed or there is a work-around this one is a show-stopper. Dave Well, the cause is now known, and it *is* possible to access the site using SM 2.31. Comment 21 in the 1094714 bug report has it. The steps recommended by Phillip Chee solved the problem for me (Ken Jarman), Thanks Phillip: 1. Restart SeaMonkey. DO NOT go to chase.com YET 2. Open the Error Console (CTRL-SHIFT-J) 3. Evaluate: Components.utils.import(resource://gre/modules/Webapps.jsm); 4. Try to login to chase.com One hell of a workaround. Is this a one-time fixes-it-forever work-around or one that needs to be repeated every time you restart SeaMonkey? Is the restart necessary or just cleaner? I am assuming now that it is identified it will be fixed in the next release, correct? I doubt that Chase is the only site impacted by it. Dave ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Seamonkey 2.31 chase web site
On 12/14/2014 10:02 AM, David H. Durgee wrote: A Williams wrote: David H. Durgee wrote: Marisa Ciceran wrote: Same problem here as of the start of this weekend. I've been on the phone several times with Chase support about this and this time the agent I spoke to said he sent a note to their compatibility developers. I am on 64-bit Windows 7 Pro on on ASUSI7 4790k processor. Marisa NoOp wrote: On 12/08/2014 10:21 AM, Lemuel Johnson wrote: On 12/8/2014 10:52 AM, NoOp wrote: On 12/08/2014 05:23 AM, J. Weaver Jr. wrote: Ken Rudolph wrote: Ron wrote: Just got the 2.31 upgrade now I can't log in to my account on chase.com I hit logon it just reloads the log on page. Works in IE and Seamonkey 2.30 Same thing happening here. This is frustrating. Can I go back to Seamonkey 2.30? Or maybe spoof the browser to firefox (which used to work when bank sites didn't accept SeaMonkey)? Same problem here: worked great with IE 2.30, not at all with 2.31. sigh Is there a Bugzilla entry for this yet? -JW https://bugzilla.mozilla.org/show_bug.cgi?id=109471 ( Unable to login at chase.com due to NS_ERROR_FAILURE (SeaMonkey only)) and for reference, here is a previous one that was fixed last year: https://bugzilla.mozilla.org/show_bug.cgi?id=924025 (Unable to log in at chase.com) I believe that's actually https://bugzilla.mozilla.org/show_bug.cgi?id=1094714 Lem Johnson You are correct - thanks for the catch! Gary Well, that is enough reason to hold back from upgrading for me! I have a Chase account, so until this is fixed or there is a work-around this one is a show-stopper. Dave Well, the cause is now known, and it *is* possible to access the site using SM 2.31. Comment 21 in the 1094714 bug report has it. The steps recommended by Phillip Chee solved the problem for me (Ken Jarman), Thanks Phillip: 1. Restart SeaMonkey. DO NOT go to chase.com YET 2. Open the Error Console (CTRL-SHIFT-J) 3. Evaluate: Components.utils.import(resource://gre/modules/Webapps.jsm); 4. Try to login to chase.com One hell of a workaround. Is this a one-time fixes-it-forever work-around or one that needs to be repeated every time you restart SeaMonkey? Is the restart necessary or just cleaner? I am assuming now that it is identified it will be fixed in the next release, correct? I doubt that Chase is the only site impacted by it. Dave Use Firefox -- One of the millions of Firefox makes me happy users https://input.mozilla.org/en-US/feedback/firefox/ ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Third-party cookie question
On 12/14/14, Paul B. Gallagher pau...@pbgdashtranslations.com wrote:
WaltS48 wrote:
On 12/13/2014 11:10 PM, Paul B. Gallagher wrote:
WaltS48 wrote:
On 12/13/2014 10:36 PM, Paul B. Gallagher wrote:
WaltS48 wrote:
Have you tried the Allow cookies for the originating site only (no
third-party cookies) setting?
I refer you to my original query, which you apparently have not read.
Slipped my mind when replying.
Did you try a test profile, visit no web sites, check cookies. What did
you find?
See the response I gave to »Q« 16 minutes ago downthread.
So you didn't try a test profile.
Okay, I started my SeaMonkey with the test profile. Had the 2 Google
cookies I mentioned earlier. Cleared cookies, history, cache, and
everything else I could check.
Restarted SeaMonkey with the test profile, had the 2 Google cookies
again, repeated the Clear history, restart process and the 2 Google
cookies come back on every restart.
Let me set Block Cookies from This Website, the website being
http://www.seamonkey-project.org/start/, clear history, restart and
they're back. Block Cookies from The Website under Tools Cookie
Manager is still enabled.
Let me try checking When removing, block the listed websites from
setting future cookies in the Cookies tab of Data Manager and using
Remove there also. APPLAUSE! No Google cookies!
That was an adventure. :)
An interesting one, but not really relevant to my query.
I don't get Google cookies on startup as you do, so I don't need to cure
a problem I don't have.
I don't get them merely by launching the browser as you do, so I don't
need to cure a problem I don't have.
(I don't understand what clearing history has to do with cookies, but be
that as it may...)
I do get precisely one Google cookie by visiting nhl.com, and since
Google isn't the originating site, that makes them third-party cookies,
which SeaMonkey claims it's blocking.
How can Google set a third-party cookie from nhl.com when my setting
says to reject third-party cookies? I must conclude that SM's
cookie-handling routine is not working correctly.
I went to nhl.com did a view source - could this
script type='text/javascript'
src='http://www.googletagservices.com/tag/js/gpt.js'
or this
(function() {
var po = document.createElement('script'); po.type =
'text/javascript'; po.async = true;
po.src = 'https://apis.google.com/js/plusone.js?onload=onLoadCallback';
var s = document.getElementsByTagName('script')[0];
s.parentNode.insertBefore(po, s);
})();
set a first-party cookie?
Lee
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
Re: updating or uninstalling flash plug-in?
Paul B. Gallagher wrote on 12/13/2014 7:36 PM: Ed Mullen wrote: Paul B. Gallagher wrote on 12/13/2014 2:19 PM: Ed Mullen wrote: Paul B. Gallagher wrote on 12/13/2014 1:18 AM: Miles Fidelman wrote: Hi Folks, So it looks like Seamonkey automatically disables the Flash plug-in if it's older than a certain version. But.. the update button takes one to a security alert, not an update page, which leads to two questions: You're right, that's really user-unfriendly and has been for some time. 1. How does one update it?, or If you skim through all the fine print in the security alert (I assume you're referring to http://helpx.adobe.com/security/products/flash-player/apsb14-27.html or something like it), you'll find a link to Adobe's download center. Once you've done it a couple of times, you'll learn to scan through all the chaff and find it. You're looking for the phrase Flash Player Download Center near the bottom. 2. How does one remove it, to force sites to push HTM5 video (there is no remove button under tools/add-ons/plugins, the way there is for extensions). (Seamonkey 2.31, Macintosh) On Windows, the program has to be removed via the Control Panel -- it's not a feature of the browser, but an independent program (though it does generally play nice with the browser). For the Mac, look here: https://forums.adobe.com/thread/928315 Why not go directly there? https://www.adobe.com/support/flashplayer/downloads.html Yes, I agree the plugins check should link there, but it doesn't. Should the user have to bookmark or memorize that link instead, or come here to ask for it? Fer God's sake, the user should bookmark the link to the add-on that needs frequent updating. Is that unreasonable? Jesus! Just save the frigging link instead of re-inventing the wheel. This isn't an Adobe support site, it's a SeaMonkey support site. The OP came here because _Mozilla's_ plugin check was so unfriendly he couldn't figure out how to update the plugin. So for us here at mozilla.support.seamonkey the issue is Mozilla's unfriendly plugin check. That's something we should fix. I was referring to: 1. How does one update it?, or If you skim through all the fine print in the security alert (I assume you're referring to http://helpx.adobe.com/security/products/flash-player/apsb14-27.html or something like it), you'll find a link to Adobe's download center. Once you've done it a couple of times, you'll learn to scan through all the chaff and find it. You're looking for the phrase Flash Player Download Center near the bottom. The link provided requires much more work to find what is needed than the direct one I provided. -- Ed Mullen http://edmullen.net/ Remember, amateurs built the ark, professionals built the Titanic. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Seamonkey 2.31 chase web site
David H. Durgee wrote on 12/14/2014 10:02 AM: A Williams wrote: David H. Durgee wrote: Marisa Ciceran wrote: Same problem here as of the start of this weekend. I've been on the phone several times with Chase support about this and this time the agent I spoke to said he sent a note to their compatibility developers. I am on 64-bit Windows 7 Pro on on ASUSI7 4790k processor. Marisa NoOp wrote: On 12/08/2014 10:21 AM, Lemuel Johnson wrote: On 12/8/2014 10:52 AM, NoOp wrote: On 12/08/2014 05:23 AM, J. Weaver Jr. wrote: Ken Rudolph wrote: Ron wrote: Just got the 2.31 upgrade now I can't log in to my account on chase.com I hit logon it just reloads the log on page. Works in IE and Seamonkey 2.30 Same thing happening here. This is frustrating. Can I go back to Seamonkey 2.30? Or maybe spoof the browser to firefox (which used to work when bank sites didn't accept SeaMonkey)? Same problem here: worked great with IE 2.30, not at all with 2.31. sigh Is there a Bugzilla entry for this yet? -JW https://bugzilla.mozilla.org/show_bug.cgi?id=109471 ( Unable to login at chase.com due to NS_ERROR_FAILURE (SeaMonkey only)) and for reference, here is a previous one that was fixed last year: https://bugzilla.mozilla.org/show_bug.cgi?id=924025 (Unable to log in at chase.com) I believe that's actually https://bugzilla.mozilla.org/show_bug.cgi?id=1094714 Lem Johnson You are correct - thanks for the catch! Gary Well, that is enough reason to hold back from upgrading for me! I have a Chase account, so until this is fixed or there is a work-around this one is a show-stopper. Dave Well, the cause is now known, and it *is* possible to access the site using SM 2.31. Comment 21 in the 1094714 bug report has it. The steps recommended by Phillip Chee solved the problem for me (Ken Jarman), Thanks Phillip: 1. Restart SeaMonkey. DO NOT go to chase.com YET 2. Open the Error Console (CTRL-SHIFT-J) 3. Evaluate: Components.utils.import(resource://gre/modules/Webapps.jsm); 4. Try to login to chase.com One hell of a workaround. Is this a one-time fixes-it-forever work-around or one that needs to be repeated every time you restart SeaMonkey? Is the restart necessary or just cleaner? One-time. Close SM, restart, you gotta do it again. I am assuming now that it is identified it will be fixed in the next release, correct? I doubt that Chase is the only site impacted by it. It's not: https://webmailcluster.perfora.net/xml/webmail/Login -- Ed Mullen http://edmullen.net/ Remember, amateurs built the ark, professionals built the Titanic. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: updating or uninstalling flash plug-in?
Ed Mullen wrote: Paul B. Gallagher wrote on 12/13/2014 7:36 PM: Ed Mullen wrote: Paul B. Gallagher wrote on 12/13/2014 2:19 PM: Ed Mullen wrote: Paul B. Gallagher wrote on 12/13/2014 1:18 AM: Miles Fidelman wrote: Hi Folks, So it looks like Seamonkey automatically disables the Flash plug-in if it's older than a certain version. But.. the update button takes one to a security alert, not an update page, which leads to two questions: You're right, that's really user-unfriendly and has been for some time. 1. How does one update it?, or If you skim through all the fine print in the security alert (I assume you're referring to http://helpx.adobe.com/security/products/flash-player/apsb14-27.html or something like it), you'll find a link to Adobe's download center. Once you've done it a couple of times, you'll learn to scan through all the chaff and find it. You're looking for the phrase Flash Player Download Center near the bottom. 2. How does one remove it, to force sites to push HTM5 video (there is no remove button under tools/add-ons/plugins, the way there is for extensions). (Seamonkey 2.31, Macintosh) On Windows, the program has to be removed via the Control Panel -- it's not a feature of the browser, but an independent program (though it does generally play nice with the browser). For the Mac, look here: https://forums.adobe.com/thread/928315 Why not go directly there? https://www.adobe.com/support/flashplayer/downloads.html Yes, I agree the plugins check should link there, but it doesn't. Should the user have to bookmark or memorize that link instead, or come here to ask for it? Fer God's sake, the user should bookmark the link to the add-on that needs frequent updating. Is that unreasonable? Jesus! Just save the frigging link instead of re-inventing the wheel. This isn't an Adobe support site, it's a SeaMonkey support site. The OP came here because _Mozilla's_ plugin check was so unfriendly he couldn't figure out how to update the plugin. So for us here at mozilla.support.seamonkey the issue is Mozilla's unfriendly plugin check. That's something we should fix. I was referring to: 1. How does one update it?, or If you skim through all the fine print in the security alert (I assume you're referring to http://helpx.adobe.com/security/products/flash-player/apsb14-27.html or something like it), you'll find a link to Adobe's download center. Once you've done it a couple of times, you'll learn to scan through all the chaff and find it. You're looking for the phrase Flash Player Download Center near the bottom. The link provided requires much more work to find what is needed than the direct one I provided. Agreed. This is the link provided by our plugin check, and it does require too much work to find what is needed. That should be fixed. By mentioning it in my reply, I was merely demonstrating that I understood and could replicate the OP's user experience. I was not advocating this circuitous route as the ideal solution that should be foisted off on all users. But you're right that I sounded too accepting of the status quo and resigned to its permanence. -- 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
Re: Seamonkey 2.31 chase web site
David H. Durgee wrote: A Williams wrote: David H. Durgee wrote: Marisa Ciceran wrote: Same problem here as of the start of this weekend. I've been on the phone several times with Chase support about this and this time the agent I spoke to said he sent a note to their compatibility developers. I am on 64-bit Windows 7 Pro on on ASUSI7 4790k processor. Marisa NoOp wrote: On 12/08/2014 10:21 AM, Lemuel Johnson wrote: On 12/8/2014 10:52 AM, NoOp wrote: On 12/08/2014 05:23 AM, J. Weaver Jr. wrote: Ken Rudolph wrote: Ron wrote: Just got the 2.31 upgrade now I can't log in to my account on chase.com I hit logon it just reloads the log on page. Works in IE and Seamonkey 2.30 Same thing happening here. This is frustrating. Can I go back to Seamonkey 2.30? Or maybe spoof the browser to firefox (which used to work when bank sites didn't accept SeaMonkey)? Same problem here: worked great with IE 2.30, not at all with 2.31. sigh Is there a Bugzilla entry for this yet? -JW https://bugzilla.mozilla.org/show_bug.cgi?id=109471 ( Unable to login at chase.com due to NS_ERROR_FAILURE (SeaMonkey only)) and for reference, here is a previous one that was fixed last year: https://bugzilla.mozilla.org/show_bug.cgi?id=924025 (Unable to log in at chase.com) I believe that's actually https://bugzilla.mozilla.org/show_bug.cgi?id=1094714 Lem Johnson You are correct - thanks for the catch! Gary Well, that is enough reason to hold back from upgrading for me! I have a Chase account, so until this is fixed or there is a work-around this one is a show-stopper. Dave Well, the cause is now known, and it *is* possible to access the site using SM 2.31. Comment 21 in the 1094714 bug report has it. The steps recommended by Phillip Chee solved the problem for me (Ken Jarman), Thanks Phillip: 1. Restart SeaMonkey. DO NOT go to chase.com YET 2. Open the Error Console (CTRL-SHIFT-J) 3. Evaluate: Components.utils.import(resource://gre/modules/Webapps.jsm); 4. Try to login to chase.com One hell of a workaround. Is this a one-time fixes-it-forever work-around or one that needs to be repeated every time you restart SeaMonkey? Is the restart necessary or just cleaner? I am assuming now that it is identified it will be fixed in the next release, correct? I doubt that Chase is the only site impacted by it. Dave I'm assuming it is an each-time-you-restart-seamonkey job. What it really means is that the developers care *and* know what the problem is. I'd expect the next version of Seamonkey to be fixed. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: updating or uninstalling flash plug-in?
Paul B. Gallagher wrote on 12/14/2014 12:28 PM: Ed Mullen wrote: Paul B. Gallagher wrote on 12/13/2014 7:36 PM: Ed Mullen wrote: Paul B. Gallagher wrote on 12/13/2014 2:19 PM: Ed Mullen wrote: Paul B. Gallagher wrote on 12/13/2014 1:18 AM: Miles Fidelman wrote: Hi Folks, So it looks like Seamonkey automatically disables the Flash plug-in if it's older than a certain version. But.. the update button takes one to a security alert, not an update page, which leads to two questions: You're right, that's really user-unfriendly and has been for some time. 1. How does one update it?, or If you skim through all the fine print in the security alert (I assume you're referring to http://helpx.adobe.com/security/products/flash-player/apsb14-27.html or something like it), you'll find a link to Adobe's download center. Once you've done it a couple of times, you'll learn to scan through all the chaff and find it. You're looking for the phrase Flash Player Download Center near the bottom. 2. How does one remove it, to force sites to push HTM5 video (there is no remove button under tools/add-ons/plugins, the way there is for extensions). (Seamonkey 2.31, Macintosh) On Windows, the program has to be removed via the Control Panel -- it's not a feature of the browser, but an independent program (though it does generally play nice with the browser). For the Mac, look here: https://forums.adobe.com/thread/928315 Why not go directly there? https://www.adobe.com/support/flashplayer/downloads.html Yes, I agree the plugins check should link there, but it doesn't. Should the user have to bookmark or memorize that link instead, or come here to ask for it? Fer God's sake, the user should bookmark the link to the add-on that needs frequent updating. Is that unreasonable? Jesus! Just save the frigging link instead of re-inventing the wheel. This isn't an Adobe support site, it's a SeaMonkey support site. The OP came here because _Mozilla's_ plugin check was so unfriendly he couldn't figure out how to update the plugin. So for us here at mozilla.support.seamonkey the issue is Mozilla's unfriendly plugin check. That's something we should fix. I was referring to: 1. How does one update it?, or If you skim through all the fine print in the security alert (I assume you're referring to http://helpx.adobe.com/security/products/flash-player/apsb14-27.html or something like it), you'll find a link to Adobe's download center. Once you've done it a couple of times, you'll learn to scan through all the chaff and find it. You're looking for the phrase Flash Player Download Center near the bottom. The link provided requires much more work to find what is needed than the direct one I provided. Agreed. This is the link provided by our plugin check, and it does require too much work to find what is needed. That should be fixed. By mentioning it in my reply, I was merely demonstrating that I understood and could replicate the OP's user experience. I was not advocating this circuitous route as the ideal solution that should be foisted off on all users. But you're right that I sounded too accepting of the status quo and resigned to its permanence. ;-) I certainly agree with you that the Mozilla plug-in check is messed up. -- Ed Mullen http://edmullen.net/ I hate sex in the movies. The seat folded up, the drink spilled and that ice really chilled the mood. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Third-party cookie question
On 12/14/2014 12:28 AM, Paul B. Gallagher wrote: WaltS48 wrote: On 12/13/2014 11:10 PM, Paul B. Gallagher wrote: WaltS48 wrote: On 12/13/2014 10:36 PM, Paul B. Gallagher wrote: WaltS48 wrote: Have you tried the Allow cookies for the originating site only (no third-party cookies) setting? I refer you to my original query, which you apparently have not read. Slipped my mind when replying. Did you try a test profile, visit no web sites, check cookies. What did you find? See the response I gave to »Q« 16 minutes ago downthread. So you didn't try a test profile. Okay, I started my SeaMonkey with the test profile. Had the 2 Google cookies I mentioned earlier. Cleared cookies, history, cache, and everything else I could check. Restarted SeaMonkey with the test profile, had the 2 Google cookies again, repeated the Clear history, restart process and the 2 Google cookies come back on every restart. Let me set Block Cookies from This Website, the website being http://www.seamonkey-project.org/start/, clear history, restart and they're back. Block Cookies from The Website under Tools Cookie Manager is still enabled. Let me try checking When removing, block the listed websites from setting future cookies in the Cookies tab of Data Manager and using Remove there also. APPLAUSE! No Google cookies! That was an adventure. :) An interesting one, but not really relevant to my query. I don't get Google cookies on startup as you do, so I don't need to cure a problem I don't have. I don't get them merely by launching the browser as you do, so I don't need to cure a problem I don't have. (I don't understand what clearing history has to do with cookies, but be that as it may...) I do get precisely one Google cookie by visiting nhl.com, and since Google isn't the originating site, that makes them third-party cookies, which SeaMonkey claims it's blocking. How can Google set a third-party cookie from nhl.com when my setting says to reject third-party cookies? I must conclude that SM's cookie-handling routine is not working correctly. It must be from something other than just viewing the main page. If I allow cookies and visit nhl.com, I get cookies from: 207.net doubleclick.net imrworldwide.com nhl.com No Google cookie. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Third-party cookie question
On 12/14/2014 09:51 AM, NoOp wrote: On 12/14/2014 12:28 AM, Paul B. Gallagher wrote: ... (I don't understand what clearing history has to do with cookies, but be that as it may...) I do get precisely one Google cookie by visiting nhl.com, and since Google isn't the originating site, that makes them third-party cookies, which SeaMonkey claims it's blocking. How can Google set a third-party cookie from nhl.com when my setting says to reject third-party cookies? I must conclude that SM's cookie-handling routine is not working correctly. It must be from something other than just viewing the main page. If I allow cookies and visit nhl.com, I get cookies from: 207.net doubleclick.net imrworldwide.com nhl.com No Google cookie. Ah, forgot that I had adblock-plus turned on, went back and turned off adblock-plus reloaded the page - now I get the google NID cookie (and a billion others). Clear cookies, cache et al - set cookies to not accept cookes from 3rd party sites, reload nhl.com only see cookies from hnl.com. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: updating or uninstalling flash plug-in?
On 12/14/2014 09:35 AM, Ed Mullen wrote: Paul B. Gallagher wrote on 12/14/2014 12:28 PM: Ed Mullen wrote: Paul B. Gallagher wrote on 12/13/2014 7:36 PM: Ed Mullen wrote: Paul B. Gallagher wrote on 12/13/2014 2:19 PM: Ed Mullen wrote: Paul B. Gallagher wrote on 12/13/2014 1:18 AM: Miles Fidelman wrote: Hi Folks, So it looks like Seamonkey automatically disables the Flash plug-in if it's older than a certain version. But.. the update button takes one to a security alert, not an update page, which leads to two questions: You're right, that's really user-unfriendly and has been for some time. 1. How does one update it?, or If you skim through all the fine print in the security alert (I assume you're referring to http://helpx.adobe.com/security/products/flash-player/apsb14-27.html or something like it), you'll find a link to Adobe's download center. Once you've done it a couple of times, you'll learn to scan through all the chaff and find it. You're looking for the phrase Flash Player Download Center near the bottom. 2. How does one remove it, to force sites to push HTM5 video (there is no remove button under tools/add-ons/plugins, the way there is for extensions). (Seamonkey 2.31, Macintosh) On Windows, the program has to be removed via the Control Panel -- it's not a feature of the browser, but an independent program (though it does generally play nice with the browser). For the Mac, look here: https://forums.adobe.com/thread/928315 Why not go directly there? https://www.adobe.com/support/flashplayer/downloads.html Yes, I agree the plugins check should link there, but it doesn't. Should the user have to bookmark or memorize that link instead, or come here to ask for it? Fer God's sake, the user should bookmark the link to the add-on that needs frequent updating. Is that unreasonable? Jesus! Just save the frigging link instead of re-inventing the wheel. This isn't an Adobe support site, it's a SeaMonkey support site. The OP came here because _Mozilla's_ plugin check was so unfriendly he couldn't figure out how to update the plugin. So for us here at mozilla.support.seamonkey the issue is Mozilla's unfriendly plugin check. That's something we should fix. I was referring to: 1. How does one update it?, or If you skim through all the fine print in the security alert (I assume you're referring to http://helpx.adobe.com/security/products/flash-player/apsb14-27.html or something like it), you'll find a link to Adobe's download center. Once you've done it a couple of times, you'll learn to scan through all the chaff and find it. You're looking for the phrase Flash Player Download Center near the bottom. The link provided requires much more work to find what is needed than the direct one I provided. Agreed. This is the link provided by our plugin check, and it does require too much work to find what is needed. That should be fixed. By mentioning it in my reply, I was merely demonstrating that I understood and could replicate the OP's user experience. I was not advocating this circuitous route as the ideal solution that should be foisted off on all users. But you're right that I sounded too accepting of the status quo and resigned to its permanence. ;-) I certainly agree with you that the Mozilla plug-in check is messed up. Usually I have a problem with the Plugin check page - particulary with Adobe Flash linux. Today when checking the page works fine.. it actually shows the correct version status. When clicking the the action button, it takes me directly to: http://get.adobe.com/flashplayer/. Just checked on a Windows machine with an outdated Adobe Flash the action link takes me to the same URL: http://get.adobe.com/flashplayer/. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Third-party cookie question
On 12/14/2014 12:59 PM, NoOp wrote: On 12/14/2014 09:51 AM, NoOp wrote: On 12/14/2014 12:28 AM, Paul B. Gallagher wrote: ... (I don't understand what clearing history has to do with cookies, but be that as it may...) I do get precisely one Google cookie by visiting nhl.com, and since Google isn't the originating site, that makes them third-party cookies, which SeaMonkey claims it's blocking. How can Google set a third-party cookie from nhl.com when my setting says to reject third-party cookies? I must conclude that SM's cookie-handling routine is not working correctly. It must be from something other than just viewing the main page. If I allow cookies and visit nhl.com, I get cookies from: 207.net doubleclick.net imrworldwide.com nhl.com No Google cookie. Ah, forgot that I had adblock-plus turned on, went back and turned off adblock-plus reloaded the page - now I get the google NID cookie (and a billion others). Clear cookies, cache et al - set cookies to not accept cookes from 3rd party sites, reload nhl.com only see cookies from hnl.com. Using my production profile for SeaMonkey. I just set my *Cookie Acceptance Policy* to Allow cookies for the original website (no third-party cookies). Left the *Cookie Retention Policy* set to Accept Cookies Normally. Removed all nhl.com and google.com cookies and cleared Private Data. Restarted SeaMonkey, went to nhl.com, did not see the google.com NID cookie. Retested several times without restarting SeaMonkey with the same result. No NID cookie was set. It appears to me that Allow cookies for the original website (no third-party cookies) is working correctly here and with your SeaMonkey. -- One of the millions of Firefox makes me happy users https://input.mozilla.org/en-US/feedback/firefox/ ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Third-party cookie question
Paul B. Gallagher wrote: EE wrote: Paul B. Gallagher wrote: This evening, I cleared all private data (including cache and cookies), and then visited nhl.com. Immediately after aborting their troublesome javascript,* I inspected my cookies and discovered that google.com had set a cookie. Now, my cookie policy at Edit | Preferences | Privacy Security | Cookies is Allow cookies for the originating website only (no third-party cookies). So how was Google able to set a cookie if I never visited their site? It's bad enough that they update their dossier on me when I visit their own sites, do they have to do it everywhere else, too?\ More to the point, how can I set SeaMonkey to do as it says and block third-party cookies? * -- They have a series of annoying scripts that grind SM to a halt and must be aborted before the site becomes usable. The URLs are constantly changing; today's version was at http://cdn.nhle.com/projects/ice3-ui/com.nhl.ice3.ui.t5.components/GlobalPageImports/dist/js/GlobalPageImports.min.js?v=8.9:1. And I'm constantly updating my custom filter in AdBlock Plus. That isn't my question. Even though I default to blocking cookies, I added an exception to block Google cookies, just to make sure. That works. I have no Google cookies. That's problematic for me because I do have a gmail account and sometimes use it to login to other sites (as soon as I'm done, I clear the cookies and resume living privately). nhl.com is not one of those, and AFAIK has not been bought by Google the way Yahoo has. I thought it was Microsoft that bought Yahoo? ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Third-party cookie question
Paul B. Gallagher wrote: WaltS48 wrote: On 12/13/2014 11:10 PM, Paul B. Gallagher wrote: WaltS48 wrote: On 12/13/2014 10:36 PM, Paul B. Gallagher wrote: WaltS48 wrote: Have you tried the Allow cookies for the originating site only (no third-party cookies) setting? I refer you to my original query, which you apparently have not read. Slipped my mind when replying. Did you try a test profile, visit no web sites, check cookies. What did you find? See the response I gave to »Q« 16 minutes ago downthread. So you didn't try a test profile. Okay, I started my SeaMonkey with the test profile. Had the 2 Google cookies I mentioned earlier. Cleared cookies, history, cache, and everything else I could check. Restarted SeaMonkey with the test profile, had the 2 Google cookies again, repeated the Clear history, restart process and the 2 Google cookies come back on every restart. Let me set Block Cookies from This Website, the website being http://www.seamonkey-project.org/start/, clear history, restart and they're back. Block Cookies from The Website under Tools Cookie Manager is still enabled. Let me try checking When removing, block the listed websites from setting future cookies in the Cookies tab of Data Manager and using Remove there also. APPLAUSE! No Google cookies! That was an adventure. :) An interesting one, but not really relevant to my query. I don't get Google cookies on startup as you do, so I don't need to cure a problem I don't have. I don't get them merely by launching the browser as you do, so I don't need to cure a problem I don't have. (I don't understand what clearing history has to do with cookies, but be that as it may...) I do get precisely one Google cookie by visiting nhl.com, and since Google isn't the originating site, that makes them third-party cookies, which SeaMonkey claims it's blocking. How can Google set a third-party cookie from nhl.com when my setting says to reject third-party cookies? I must conclude that SM's cookie-handling routine is not working correctly. You could default to blocking cookies and make exceptions for those that you need. I do that, and I have no unwanted cookies. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Find box invoked without being requested
Does anyone else have the problem where they're typing something into a web form in SM and suddenly the find box pops open and the cursor is entering my text there, instead of in the web form? This has been happening quite a lot and I kept assuming I was hitting some odd key combination that replicated 'control F' -- but today I've been paying attention and it's been happening randomly, even when I'm sure I'm not hitting any odd key combination, or any specific key. If this is happening only to me, I'd better investigate my keyboard! ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Find box invoked without being requested
Yes, it's an accessibility feature called Type Ahead Find which is enabled by default in SeaMonkey. In about:config you can disable by setting these prefs to false: accessibility.typeaheadfind accessibility.typeaheadfind.autostart ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: updating or uninstalling flash plug-in?
Mozilla's plugin-check page is updated manually and is *never* up-to-date. In fact, it generally considers many ancient versions of plugins to be current and occasionally it will even say that brand new versions are out-of-date. The plan was to convince the various plugins developers to adopt a system of notifications that all browsers could use to keep their plugins up-to-date. This likely was never considered because Google's answer was to simply bundle important plugins into Chrome, thus circumventing the whole mess. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Flashblock 1.5 can be made to work in SeaMonkey 2.31!
On Wednesday, December 10, 2014 5:41:25 PM UTC-5, David E. Ross wrote: I have the PrefBar extension. I created my own button to toggle the HTML5 preference, which is media.autoplay.enabled. That way, HTML5 is not tied to Flash. AFAIK, this preference stopped working some time ago and Mozilla is in no hurry to fix it for some reason. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Find box invoked without being requested
pjdkru...@gmail.com wrote: Yes, it's an accessibility feature called Type Ahead Find which is enabled by default in SeaMonkey. In about:config you can disable by setting these prefs to false: accessibility.typeaheadfind accessibility.typeaheadfind.autostart THANK YOU! This was driving me NUTS!! -- Jaime A. Cruz Nassau Wings Motorcycle Club http://www.nassauwings.org/ AMA District 34 http://www.AMADistrict34.com/ Pop's Run http://www.popsrun.org/ ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Seamonkey 2.31 chase web site
On 15/12/2014 01:39, A Williams wrote: David H. Durgee wrote: Is this a one-time fixes-it-forever work-around or one that needs to be repeated every time you restart SeaMonkey? Is the restart necessary or just cleaner? I am assuming now that it is identified it will be fixed in the next release, correct? I doubt that Chase is the only site impacted by it. Dave I'm assuming it is an each-time-you-restart-seamonkey job. What it really means is that the developers care *and* know what the problem is. I'd expect the next version of Seamonkey to be fixed. I had a hypothesis on what was causing the problem. https://bugzilla.mozilla.org/show_bug.cgi?id=1094714#c17 I wrote a few steps that a non-technical user could do to test this hypothesis. Results confirm that we were right. We now have a quick fix and we need to get this in the hands of our users as soon as possible. https://bugzilla.mozilla.org/attachment.cgi?id=8527843action=edit A longer term fix would be: https://bugzilla.mozilla.org/show_bug.cgi?id=1094714#c12 but that would require the involvement of a Gecko developer. And nothing stops us from landing the quick fix. Phil -- Philip Chee phi...@aleytys.pc.my, philip.c...@gmail.com http://flashblock.mozdev.org/ http://xsidebar.mozdev.org Guard us from the she-wolf and the wolf, and guard us from the thief, oh Night, and so be good for us to pass. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Seamonkey 2.31 chase web site
Philip Chee wrote: On 15/12/2014 01:39, A Williams wrote: David H. Durgee wrote: Is this a one-time fixes-it-forever work-around or one that needs to be repeated every time you restart SeaMonkey? Is the restart necessary or just cleaner? I am assuming now that it is identified it will be fixed in the next release, correct? I doubt that Chase is the only site impacted by it. Dave I'm assuming it is an each-time-you-restart-seamonkey job. What it really means is that the developers care *and* know what the problem is. I'd expect the next version of Seamonkey to be fixed. I had a hypothesis on what was causing the problem. https://bugzilla.mozilla.org/show_bug.cgi?id=1094714#c17 I wrote a few steps that a non-technical user could do to test this hypothesis. Results confirm that we were right. We now have a quick fix and we need to get this in the hands of our users as soon as possible. https://bugzilla.mozilla.org/attachment.cgi?id=8527843action=edit A longer term fix would be: https://bugzilla.mozilla.org/show_bug.cgi?id=1094714#c12 but that would require the involvement of a Gecko developer. And nothing stops us from landing the quick fix. Phil For a non-technical novice, how exactly (step by step) does one utilize the quick fix? -- Ken Rudolph ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
