Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.
On Sat, 18 Jul 2009 20:47:31 -0700, Ant wrote: I prefer not to use prerelease. Is it still buggy? Crashes, etc.? How about the old extensions? I use all these: * Extension Uninstaller API 2.0 (http://jgillick.nettripper.com/) You don't need this. SeaMonkey comes with the Firefox 3.5 Addons Manager. * Flashblock (http://flashblock.mozdev.org/) I am the Flashblock project owner. I make sure that Flashblock always works with the latest versions of SeaMonkey 2.0x. 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. [ ]To shoot a mime, do you use a silencer? * TagZilla 0.066.6 ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.
On 7/19/2009 4:48 AM PT, Philip Chee typed: On Sat, 18 Jul 2009 20:47:31 -0700, Ant wrote: I prefer not to use prerelease. Is it still buggy? Crashes, etc.? How about the old extensions? I use all these: * Extension Uninstaller API 2.0 (http://jgillick.nettripper.com/) You don't need this. SeaMonkey comes with the Firefox 3.5 Addons Manager. * Flashblock (http://flashblock.mozdev.org/) I am the Flashblock project owner. I make sure that Flashblock always works with the latest versions of SeaMonkey 2.0x. Cool and thanks. I wonder what about the other ones. Hmm. -- It is said that the lonely eagle flies to the mountain peaks while the lowly ant crawls the ground, but cannot the soul of the ant soar as high as the eagle? --unknown /\___/\ / /\ /\ \ Phil/Ant @ http://antfarm.ma.cx (Personal Web Site) | |o o| |Ant's Quality Foraged Links (AQFL): http://aqfl.net \ _ / Nuke ANT from e-mail address: phi...@earthlink.netant ( ) or ant...@zimage.com Ant is currently not listening to any songs on his home computer. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.
On 7/18/2009 12:42 PM PT, Benoit Renard typed: Paul Hartman wrote: On Fri, Jul 17, 2009 at 9:30 AM, Antphi...@earthlink.netant wrote: Since the problem still exists, is there a way to tell SeaMonkey v1 and Firefox v2 to not use JavaScript/JS on these Web sites? You could use the noscript extension. noscript.net Bad suggestion. NoScript disables JavaScript globally and works with a whitelist. If one wants to only disable JavaScript for a couple sites (s)he should use YesScript. Ah thanks for the warning. I thought it could white and black list for specific sites/servers. :( Unfortunately, YesScript doesn't do SeaMonkey v1. :( -- The ant's a centaur in his dragon world. Pull down thy vanity, it is not man... Made courage, or made order, or made grace,... Pull down thy vanity, I say pull down. Learn of the green world what can be thy place... In scaled invention or true artistry,... Pull down thy vanity,... Paquin pull down! The green casque has outdone your elegance. --Ezra Pound's poem /\___/\ / /\ /\ \ Phil/Ant @ http://antfarm.ma.cx (Personal Web Site) | |o o| |Ant's Quality Foraged Links (AQFL): http://aqfl.net \ _ / Nuke ANT from e-mail address: phi...@earthlink.netant ( ) or ant...@zimage.com Ant is currently not listening to any songs on his home computer. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.
On 07/18/2009 01:01 PM, Ant wrote: On 7/18/2009 12:42 PM PT, Benoit Renard typed: Paul Hartman wrote: On Fri, Jul 17, 2009 at 9:30 AM, Antphi...@earthlink.netant wrote: Since the problem still exists, is there a way to tell SeaMonkey v1 and Firefox v2 to not use JavaScript/JS on these Web sites? You could use the noscript extension. noscript.net Bad suggestion. NoScript disables JavaScript globally and works with a whitelist. If one wants to only disable JavaScript for a couple sites (s)he should use YesScript. Ah thanks for the warning. I thought it could white and black list for specific sites/servers. :( Unfortunately, YesScript doesn't do SeaMonkey v1. :( http://prefbar.mozdev.org/ You can disable javascript with a single click before going to the site. Works in 1.1.x and 2.0x It's the first, and one of only a few, that I add as soon as installing SeaMonkey or FireFox. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.
On 7/18/2009 2:23 PM PT, NoOp typed: http://prefbar.mozdev.org/ You can disable javascript with a single click before going to the site. Works in 1.1.x and 2.0x It's the first, and one of only a few, that I add as soon as installing SeaMonkey or FireFox. Yeah, I am using that. Usually, I am too late to find out the site is hogging my Web browser so I try hit JavaScript/JS button and reload/load the Web page. I hope we don't have to wait too long for SeaMonkey v2 since it is in alpha now. :( -- I could crush him like an ant. But it would be too easy. No, revenge is a dish best served cold. I'll bide my time until... Oh, what the hell, I'll just crush him like an ant. --Mr. Burns, The Simpsons (Blood Feud Episode 7F22) /\___/\ / /\ /\ \ Phil/Ant @ http://antfarm.ma.cx (Personal Web Site) | |o o| |Ant's Quality Foraged Links (AQFL): http://aqfl.net \ _ / Nuke ANT from e-mail address: phi...@earthlink.netant ( ) or ant...@zimage.com Ant is currently not listening to any songs on his home computer. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.
On 07/18/2009 03:38 PM, Ant wrote: On 7/18/2009 2:23 PM PT, NoOp typed: http://prefbar.mozdev.org/ You can disable javascript with a single click before going to the site. Works in 1.1.x and 2.0x It's the first, and one of only a few, that I add as soon as installing SeaMonkey or FireFox. Yeah, I am using that. Usually, I am too late to find out the site is hogging my Web browser so I try hit JavaScript/JS button and reload/load the Web page. I hope we don't have to wait too long for SeaMonkey v2 since it is in alpha now. :( Why wait? SM 1.1.x and 2.0x run in parallel just fine. And from Kairo today: Hi everyone, I ran into strange problems with the Mac builds of SeaMonkey 2.0 Beta 1 (a step in the process that works flawlessly everywhere else hangs with very strange errors), but that shouldn't stop us from starting tests on the other two platforms that have builds available now. So, please help us testing the available Windows installers and Linux packages, both available in 17 languages including US English! Windows: http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/2.0b1-candidates/build1/win32/ Linux: http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/2.0b1-candidates/build1/linux-i686/ I hope to sort out the Mac problems ASAP, we'll have disk images when those are solved and will get updates ready on the testing channels once all platforms have builds ready. Robert Kaiser Both installed and are working just find on both linux (see my headers) and WinXPPro (SP3). And prefbar works find in both. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.
On 7/18/2009 4:00 PM PT, NoOp typed: I hope we don't have to wait too long for SeaMonkey v2 since it is in alpha now. :( Why wait? SM 1.1.x and 2.0x run in parallel just fine. And from Kairo today: I prefer not to use prerelease. Is it still buggy? Crashes, etc.? How about the old extensions? I use all these: Last updated: Sat Jul 18 2009 20:47:07 GMT-0700 (Pacific Daylight Time) User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.22) Gecko/20090605 SeaMonkey/1.1.17 Extensions (enabled: 18) * Adblock Plus (http://adblockplus.org/) * BugMeNot (mailto:ehami...@gmail.com) * Colored Tabs 1.3 * Coralize 0.9 (http://piki.org/patrick/) * Extension Uninstaller API 2.0 (http://jgillick.nettripper.com/) * Flashblock (http://flashblock.mozdev.org/) * IE View 1.4.3 (http://ieview.mozdev.org/) * Mnenhy - Chrome Manager (http://mnenhy.mozdev.org/) * Mnenhy - Custom Headers (http://mnenhy.mozdev.org/) * Mnenhy - Junk Filter Tools (http://mnenhy.mozdev.org/) * Mnenhy - MailNews FolderStore (http://mnenhy.mozdev.org/) * Mnenhy - MailNews Sidebar (http://mnenhy.mozdev.org/) * Mnenhy - MailNews-Enhancements (http://mnenhy.mozdev.org/) * Mnenhy - Registry Viewer (http://mnenhy.mozdev.org/) * Mnenhy - Text Codecs (http://mnenhy.mozdev.org/) * Preferences Toolbar (http://prefbar.mozdev.org/) * SessionSaver 0.2d (http://adblock.mozdev.org/sessionsaver/) * TinyUrl Creator 2.0 (http://mozmonkey.com/) -- To conquer the world, we must be as meticulus and calculating as a colony of ants on the march. --Julius Caesar /\___/\ / /\ /\ \ Phil/Ant @ http://antfarm.ma.cx (Personal Web Site) | |o o| |Ant's Quality Foraged Links (AQFL): http://aqfl.net \ _ / Nuke ANT from e-mail address: phi...@earthlink.netant ( ) or ant...@zimage.com Ant is currently not listening to any songs on his home computer. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.
Since the problem still exists, is there a way to tell SeaMonkey v1 and Firefox v2 to not use JavaScript/JS on these Web sites? -- I got this aunt... Carpenter ant. --Girl and Crow /\___/\ / /\ /\ \ Phil/Ant @ http://antfarm.ma.cx (Personal Web Site) | |o o| |Ant's Quality Foraged Links (AQFL): http://aqfl.net \ _ / Nuke ANT from e-mail address: phi...@earthlink.netant ( ) or ant...@zimage.com Ant is currently not listening to any songs on his home computer. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.
On Fri, Jul 17, 2009 at 9:30 AM, Antphi...@earthlink.netant wrote: Since the problem still exists, is there a way to tell SeaMonkey v1 and Firefox v2 to not use JavaScript/JS on these Web sites? You could use the noscript extension. noscript.net ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.
On 7/17/2009 9:07 AM PT, Paul Hartman typed: On Fri, Jul 17, 2009 at 9:30 AM, Antphi...@earthlink.netant wrote: Since the problem still exists, is there a way to tell SeaMonkey v1 and Firefox v2 to not use JavaScript/JS on these Web sites? You could use the noscript extension. noscript.net Thanks. -- I have to sit up with a sick ant. --unknown /\___/\ / /\ /\ \ Phil/Ant @ http://antfarm.ma.cx (Personal Web Site) | |o o| |Ant's Quality Foraged Links (AQFL): http://aqfl.net \ _ / Nuke ANT from e-mail address: phi...@earthlink.netant ( ) or ant...@zimage.com Ant is currently not listening to any songs on his home computer. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.
On 7/15/2009 9:59 PM, Ant wrote: On 7/15/2009 8:38 AM PT, David E. Ross typed: I noticed lately Gizmodo's Web pages are rendering slowly and hogging Web browser's CPU and memory badly. Example: http://gizmodo.com/5313690/why-you-cant-complain-about-the-price-of-todays-gadgets Is anyone else having this problem? If so, then what's going on? Thank you in advance. :) on FF 1.5.0.9 / XP-SP2 that URL is a crapper... there is a script running that refuses to be killed, so I closed FF, disabled JavaScript and re-opened the URL it works properly that way for me. Try disabling JS, see what happens your end! reg I've seen Web pages with scripts that, when rendering of the page is done, a script then downloads additional scripts from a server. Sometimes it seems that one of the addtional scripts then downloads even more scripts. Since I have a dial-up Internet connection, this really slows things down. The Web site for the Vanguard Group (mutual funds) is one such site. I generally disable JavaScript when viewing pages at that site. However, I must enable JavaScript for certain pages to complete transactions or view account statements. Did you ever e-mail the Web team over there? If so, then any luck? :( There is also a problem with viewing parts of the Vanguard site with SeaMonkey, caused by sniffing for Firefox and not Gecko. See bug #417955 at https://bugzilla.mozilla.org/show_bug.cgi?id=417955. I sent E-mail to the Web team, I called them on the phone, and I sent a postal letter to the CEO. They claim that the security of their Web site requires that they test the site for any browser they allow to view it. (After all, Vanguard is one of the two largest mutual fund groups in the U.S.) They tested the site for Firefox but not for SeaMonkey. They don't agree that Gecko is Gecko. As for the delays caused by the use of scripts that download more scripts, their response was that I should use broadband service instead of dial-up. As for the sniffing for Firefox, I ran into the same problem with my bank and my credit union. I solved the problem by creating a special SeaMonkey profile where I am permanently spoofing Firefox. (The UA string ends with SeaMonkey/1.1.17 NOT Firefox/2.0.0.20.) To make these sites work, I also had to set my preferences to accept all cookies and all popups. I am careful not to browse any other sites from that profile. -- David E. Ross http://www.rossde.com/ Go to Mozdev at http://www.mozdev.org/ for quick access to extensions for Firefox, Thunderbird, SeaMonkey, and other Mozilla-related applications. You can access Mozdev much more quickly than you can Mozilla Add-Ons. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.
Date: 7/16/2009 12:21 PM, Author: David E. Ross Wrote: On 7/15/2009 9:59 PM, Ant wrote: On 7/15/2009 8:38 AM PT, David E. Ross typed: I noticed lately Gizmodo's Web pages are rendering slowly and hogging Web browser's CPU and memory badly. Example: http://gizmodo.com/5313690/why-you-cant-complain-about-the-price-of-todays-gadgets Is anyone else having this problem? If so, then what's going on? Thank you in advance. :) on FF 1.5.0.9 / XP-SP2 that URL is a crapper... there is a script running that refuses to be killed, so I closed FF, disabled JavaScript and re-opened the URL it works properly that way for me. Try disabling JS, see what happens your end! reg I've seen Web pages with scripts that, when rendering of the page is done, a script then downloads additional scripts from a server. Sometimes it seems that one of the addtional scripts then downloads even more scripts. Since I have a dial-up Internet connection, this really slows things down. The Web site for the Vanguard Group (mutual funds) is one such site. I generally disable JavaScript when viewing pages at that site. However, I must enable JavaScript for certain pages to complete transactions or view account statements. Did you ever e-mail the Web team over there? If so, then any luck? :( There is also a problem with viewing parts of the Vanguard site with SeaMonkey, caused by sniffing for Firefox and not Gecko. See bug #417955 at https://bugzilla.mozilla.org/show_bug.cgi?id=417955. I sent E-mail to the Web team, I called them on the phone, and I sent a postal letter to the CEO. They claim that the security of their Web site requires that they test the site for any browser they allow to view it. (After all, Vanguard is one of the two largest mutual fund groups in the U.S.) They tested the site for Firefox but not for SeaMonkey. They don't agree that Gecko is Gecko. As for the delays caused by the use of scripts that download more scripts, their response was that I should use broadband service instead of dial-up. As for the sniffing for Firefox, I ran into the same problem with my bank and my credit union. I solved the problem by creating a special SeaMonkey profile where I am permanently spoofing Firefox. (The UA string ends with SeaMonkey/1.1.17 NOT Firefox/2.0.0.20.) To make these sites work, I also had to set my preferences to accept all cookies and all popups. I am careful not to browse any other sites from that profile. Someone should explain to the morons that browser sniffing has absolutely *NO* security benefits. Opera has UA spoofing built in, all Mozilla products have UA switcher extensions available but it can be without one, and even IE8 has a UA picker that can spoof as Firefox, Netscape or even a cell phone. Sniffing for the UA string is like saying that if you are clever enough to write Employee on a 3x5 card and wear it on your lapel, you are free to enter and leave the safe it will :-( My company's website requires IE5.5+ or Netscape 7.1+. I set up a profile to spoof as Netscape 7.2 and happily access the site with Minefield 3.6a :-) -- G. R. Woodring ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.
G. R. Woodring wrote: Date: 7/16/2009 12:21 PM, Author: David E. Ross Wrote: On 7/15/2009 9:59 PM, Ant wrote: On 7/15/2009 8:38 AM PT, David E. Ross typed: I noticed lately Gizmodo's Web pages are rendering slowly and hogging Web browser's CPU and memory badly. Example: http://gizmodo.com/5313690/why-you-cant-complain-about-the-price-of-todays-gadgets Is anyone else having this problem? If so, then what's going on? Thank you in advance. :) on FF 1.5.0.9 / XP-SP2 that URL is a crapper... there is a script running that refuses to be killed, so I closed FF, disabled JavaScript and re-opened the URL it works properly that way for me. Try disabling JS, see what happens your end! reg I've seen Web pages with scripts that, when rendering of the page is done, a script then downloads additional scripts from a server. Sometimes it seems that one of the addtional scripts then downloads even more scripts. Since I have a dial-up Internet connection, this really slows things down. The Web site for the Vanguard Group (mutual funds) is one such site. I generally disable JavaScript when viewing pages at that site. However, I must enable JavaScript for certain pages to complete transactions or view account statements. Did you ever e-mail the Web team over there? If so, then any luck? :( There is also a problem with viewing parts of the Vanguard site with SeaMonkey, caused by sniffing for Firefox and not Gecko. See bug #417955 at https://bugzilla.mozilla.org/show_bug.cgi?id=417955. I sent E-mail to the Web team, I called them on the phone, and I sent a postal letter to the CEO. They claim that the security of their Web site requires that they test the site for any browser they allow to view it. (After all, Vanguard is one of the two largest mutual fund groups in the U.S.) They tested the site for Firefox but not for SeaMonkey. They don't agree that Gecko is Gecko. As for the delays caused by the use of scripts that download more scripts, their response was that I should use broadband service instead of dial-up. As for the sniffing for Firefox, I ran into the same problem with my bank and my credit union. I solved the problem by creating a special SeaMonkey profile where I am permanently spoofing Firefox. (The UA string ends with SeaMonkey/1.1.17 NOT Firefox/2.0.0.20.) To make these sites work, I also had to set my preferences to accept all cookies and all popups. I am careful not to browse any other sites from that profile. Someone should explain to the morons that browser sniffing has absolutely *NO* security benefits. Opera has UA spoofing built in, all Mozilla products have UA switcher extensions available but it can be without one, and even IE8 has a UA picker that can spoof as Firefox, Netscape or even a cell phone. Sniffing for the UA string is like saying that if you are clever enough to write Employee on a 3x5 card and wear it on your lapel, you are free to enter and leave the safe it will :-( My company's website requires IE5.5+ or Netscape 7.1+. I set up a profile to spoof as Netscape 7.2 and happily access the site with Minefield 3.6a :-) Then there are the sites, run by a large software/OS company, that sniff to determine if you are using a rival browser and make sure the display is just enough 'off' to make like unpleasant. That kind of thing is just petty, and juvenile. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.
David E. Ross wrote: On 7/15/2009 9:59 PM, Ant wrote: On 7/15/2009 8:38 AM PT, David E. Ross typed: I noticed lately Gizmodo's Web pages are rendering slowly and hogging Web browser's CPU and memory badly. Example: http://gizmodo.com/5313690/why-you-cant-complain-about-the-price-of-todays-gadgets Is anyone else having this problem? If so, then what's going on? Thank you in advance. :) on FF 1.5.0.9 / XP-SP2 that URL is a crapper... there is a script running that refuses to be killed, so I closed FF, disabled JavaScript and re-opened the URL it works properly that way for me. Try disabling JS, see what happens your end! reg I've seen Web pages with scripts that, when rendering of the page is done, a script then downloads additional scripts from a server. Sometimes it seems that one of the addtional scripts then downloads even more scripts. Since I have a dial-up Internet connection, this really slows things down. The Web site for the Vanguard Group (mutual funds) is one such site. I generally disable JavaScript when viewing pages at that site. However, I must enable JavaScript for certain pages to complete transactions or view account statements. Did you ever e-mail the Web team over there? If so, then any luck? :( There is also a problem with viewing parts of the Vanguard site with SeaMonkey, caused by sniffing for Firefox and not Gecko. See bug #417955 athttps://bugzilla.mozilla.org/show_bug.cgi?id=417955. I sent E-mail to the Web team, I called them on the phone, and I sent a postal letter to the CEO. They claim that the security of their Web site requires that they test the site for any browser they allow to view it. (After all, Vanguard is one of the two largest mutual fund groups in the U.S.) They tested the site for Firefox but not for SeaMonkey. They don't agree that Gecko is Gecko. As for the delays caused by the use of scripts that download more scripts, their response was that I should use broadband service instead of dial-up. As for the sniffing for Firefox, I ran into the same problem with my bank and my credit union. I solved the problem by creating a special SeaMonkey profile where I am permanently spoofing Firefox. (The UA string ends with SeaMonkey/1.1.17 NOT Firefox/2.0.0.20.) To make these sites work, I also had to set my preferences to accept all cookies and all popups. I am careful not to browse any other sites from that profile. David, I think it may be a little-more complicated than simply sniffing the Firefox vs SeaMonkey UA. I don't have a Vanguard account, so that may be a factor for me... I don't spoof-UA ever, but using the nightly-Linux-64bit build over broadband ~ Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2a1pre) Gecko/20090716 Lightning/1.0pre SeaMonkey/2.1a1pre ID:20090716013332 on your UA/Flash test-URL at https://personal.vanguard.com/us/VanguardViewsArticlePublic?ArticleJSP=/freshness/News_and_Views/news_ALL_mmyields_01262009_ALL.jspsrc=NMCreturnLink=/freshness/News_and_Views/news_ALL_mmyields_01262009_ALL.jsp https://personal.vanguard.com/us/VanguardViewsArticlePublic?ArticleJSP=/freshness/News_and_Views/news_ALL_mmyields_01262009_ALL.jspsrc=NMCreturnLink=/freshness/News_and_Views/news_ALL_mmyields_01262009_ALL.jsp I got this :- http://www.flickr.com/photos/22198...@n03/3727717220/sizes/l/ Which I think, renders the page OK? What do you think? Barry. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.
Barry Edwin Gilmour wrote: David E. Ross wrote: On 7/15/2009 9:59 PM, Ant wrote: On 7/15/2009 8:38 AM PT, David E. Ross typed: I noticed lately Gizmodo's Web pages are rendering slowly and hogging Web browser's CPU and memory badly. Example: http://gizmodo.com/5313690/why-you-cant-complain-about-the-price-of-todays-gadgets Is anyone else having this problem? If so, then what's going on? Thank you in advance. :) on FF 1.5.0.9 / XP-SP2 that URL is a crapper... there is a script running that refuses to be killed, so I closed FF, disabled JavaScript and re-opened the URL it works properly that way for me. Try disabling JS, see what happens your end! reg I've seen Web pages with scripts that, when rendering of the page is done, a script then downloads additional scripts from a server. Sometimes it seems that one of the addtional scripts then downloads even more scripts. Since I have a dial-up Internet connection, this really slows things down. The Web site for the Vanguard Group (mutual funds) is one such site. I generally disable JavaScript when viewing pages at that site. However, I must enable JavaScript for certain pages to complete transactions or view account statements. Did you ever e-mail the Web team over there? If so, then any luck? :( There is also a problem with viewing parts of the Vanguard site with SeaMonkey, caused by sniffing for Firefox and not Gecko. See bug #417955 athttps://bugzilla.mozilla.org/show_bug.cgi?id=417955. I sent E-mail to the Web team, I called them on the phone, and I sent a postal letter to the CEO. They claim that the security of their Web site requires that they test the site for any browser they allow to view it. (After all, Vanguard is one of the two largest mutual fund groups in the U.S.) They tested the site for Firefox but not for SeaMonkey. They don't agree that Gecko is Gecko. As for the delays caused by the use of scripts that download more scripts, their response was that I should use broadband service instead of dial-up. As for the sniffing for Firefox, I ran into the same problem with my bank and my credit union. I solved the problem by creating a special SeaMonkey profile where I am permanently spoofing Firefox. (The UA string ends with SeaMonkey/1.1.17 NOT Firefox/2.0.0.20.) To make these sites work, I also had to set my preferences to accept all cookies and all popups. I am careful not to browse any other sites from that profile. David, I think it may be a little-more complicated than simply sniffing the Firefox vs SeaMonkey UA. I don't have a Vanguard account, so that may be a factor for me... I don't spoof-UA ever, but using the nightly-Linux-64bit build over broadband ~ Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2a1pre) Gecko/20090716 Lightning/1.0pre SeaMonkey/2.1a1pre ID:20090716013332 on your UA/Flash test-URL at https://personal.vanguard.com/us/VanguardViewsArticlePublic?ArticleJSP=/freshness/News_and_Views/news_ALL_mmyields_01262009_ALL.jspsrc=NMCreturnLink=/freshness/News_and_Views/news_ALL_mmyields_01262009_ALL.jsp I got this :- http://www.flickr.com/photos/22198...@n03/3727717220/sizes/l/ Which I think, renders the page OK? What do you think? Barry. A possible-clue maybe that at the time you made that test, you were using 32bit Flash 10.0.12.36 (10.0 r12), whereas I notice I am now using 64bit Flash-10.0.22.87-2 edition, which is more-stable than that older flash which had many-rendering-problems, including fullscreen-crashes on 32bit-Linux. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.
On 7/16/2009 1:28 PM, Barry Edwin Gilmour wrote: David E. Ross wrote: On 7/15/2009 9:59 PM, Ant wrote: On 7/15/2009 8:38 AM PT, David E. Ross typed: I noticed lately Gizmodo's Web pages are rendering slowly and hogging Web browser's CPU and memory badly. Example: http://gizmodo.com/5313690/why-you-cant-complain-about-the-price-of-todays-gadgets Is anyone else having this problem? If so, then what's going on? Thank you in advance. :) on FF 1.5.0.9 / XP-SP2 that URL is a crapper... there is a script running that refuses to be killed, so I closed FF, disabled JavaScript and re-opened the URL it works properly that way for me. Try disabling JS, see what happens your end! reg I've seen Web pages with scripts that, when rendering of the page is done, a script then downloads additional scripts from a server. Sometimes it seems that one of the addtional scripts then downloads even more scripts. Since I have a dial-up Internet connection, this really slows things down. The Web site for the Vanguard Group (mutual funds) is one such site. I generally disable JavaScript when viewing pages at that site. However, I must enable JavaScript for certain pages to complete transactions or view account statements. Did you ever e-mail the Web team over there? If so, then any luck? :( There is also a problem with viewing parts of the Vanguard site with SeaMonkey, caused by sniffing for Firefox and not Gecko. See bug #417955 athttps://bugzilla.mozilla.org/show_bug.cgi?id=417955. I sent E-mail to the Web team, I called them on the phone, and I sent a postal letter to the CEO. They claim that the security of their Web site requires that they test the site for any browser they allow to view it. (After all, Vanguard is one of the two largest mutual fund groups in the U.S.) They tested the site for Firefox but not for SeaMonkey. They don't agree that Gecko is Gecko. As for the delays caused by the use of scripts that download more scripts, their response was that I should use broadband service instead of dial-up. As for the sniffing for Firefox, I ran into the same problem with my bank and my credit union. I solved the problem by creating a special SeaMonkey profile where I am permanently spoofing Firefox. (The UA string ends with SeaMonkey/1.1.17 NOT Firefox/2.0.0.20.) To make these sites work, I also had to set my preferences to accept all cookies and all popups. I am careful not to browse any other sites from that profile. David, I think it may be a little-more complicated than simply sniffing the Firefox vs SeaMonkey UA. I don't have a Vanguard account, so that may be a factor for me... I don't spoof-UA ever, but using the nightly-Linux-64bit build over broadband ~ Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2a1pre) Gecko/20090716 Lightning/1.0pre SeaMonkey/2.1a1pre ID:20090716013332 on your UA/Flash test-URL at https://personal.vanguard.com/us/VanguardViewsArticlePublic?ArticleJSP=/freshness/News_and_Views/news_ALL_mmyields_01262009_ALL.jspsrc=NMCreturnLink=/freshness/News_and_Views/news_ALL_mmyields_01262009_ALL.jsp https://personal.vanguard.com/us/VanguardViewsArticlePublic?ArticleJSP=/freshness/News_and_Views/news_ALL_mmyields_01262009_ALL.jspsrc=NMCreturnLink=/freshness/News_and_Views/news_ALL_mmyields_01262009_ALL.jsp I got this :- http://www.flickr.com/photos/22198...@n03/3727717220/sizes/l/ Which I think, renders the page OK? What do you think? Barry. Sniffing problems do not afflict all Vanguard pages. They definitely afflict getting my IRS 1099 forms (dividends, interest, etc). Of course, this is where security is important, protecting my personal financial information. On the other hand, the News pages are severely affected by scripts downloading additional scripts. I can't view the pages unless I allow this to happen. It's damned annoying to be reading a news item and suddenly have the whole page blank out and then reload because a script downloaded another script that finally started executing, especially if none of the scripts contribute anything to the content of the page I'm reading (other than JavaScript links to other pages). -- David E. Ross http://www.rossde.com/ Go to Mozdev at http://www.mozdev.org/ for quick access to extensions for Firefox, Thunderbird, SeaMonkey, and other Mozilla-related applications. You can access Mozdev much more quickly than you can Mozilla Add-Ons. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.
On 7/16/2009 1:53 PM, Barry Edwin Gilmour wrote: Barry Edwin Gilmour wrote: David E. Ross wrote: On 7/15/2009 9:59 PM, Ant wrote: On 7/15/2009 8:38 AM PT, David E. Ross typed: I noticed lately Gizmodo's Web pages are rendering slowly and hogging Web browser's CPU and memory badly. Example: http://gizmodo.com/5313690/why-you-cant-complain-about-the-price-of-todays-gadgets Is anyone else having this problem? If so, then what's going on? Thank you in advance. :) on FF 1.5.0.9 / XP-SP2 that URL is a crapper... there is a script running that refuses to be killed, so I closed FF, disabled JavaScript and re-opened the URL it works properly that way for me. Try disabling JS, see what happens your end! reg I've seen Web pages with scripts that, when rendering of the page is done, a script then downloads additional scripts from a server. Sometimes it seems that one of the addtional scripts then downloads even more scripts. Since I have a dial-up Internet connection, this really slows things down. The Web site for the Vanguard Group (mutual funds) is one such site. I generally disable JavaScript when viewing pages at that site. However, I must enable JavaScript for certain pages to complete transactions or view account statements. Did you ever e-mail the Web team over there? If so, then any luck? :( There is also a problem with viewing parts of the Vanguard site with SeaMonkey, caused by sniffing for Firefox and not Gecko. See bug #417955 athttps://bugzilla.mozilla.org/show_bug.cgi?id=417955. I sent E-mail to the Web team, I called them on the phone, and I sent a postal letter to the CEO. They claim that the security of their Web site requires that they test the site for any browser they allow to view it. (After all, Vanguard is one of the two largest mutual fund groups in the U.S.) They tested the site for Firefox but not for SeaMonkey. They don't agree that Gecko is Gecko. As for the delays caused by the use of scripts that download more scripts, their response was that I should use broadband service instead of dial-up. As for the sniffing for Firefox, I ran into the same problem with my bank and my credit union. I solved the problem by creating a special SeaMonkey profile where I am permanently spoofing Firefox. (The UA string ends with SeaMonkey/1.1.17 NOT Firefox/2.0.0.20.) To make these sites work, I also had to set my preferences to accept all cookies and all popups. I am careful not to browse any other sites from that profile. David, I think it may be a little-more complicated than simply sniffing the Firefox vs SeaMonkey UA. I don't have a Vanguard account, so that may be a factor for me... I don't spoof-UA ever, but using the nightly-Linux-64bit build over broadband ~ Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2a1pre) Gecko/20090716 Lightning/1.0pre SeaMonkey/2.1a1pre ID:20090716013332 on your UA/Flash test-URL at https://personal.vanguard.com/us/VanguardViewsArticlePublic?ArticleJSP=/freshness/News_and_Views/news_ALL_mmyields_01262009_ALL.jspsrc=NMCreturnLink=/freshness/News_and_Views/news_ALL_mmyields_01262009_ALL.jsp I got this :- http://www.flickr.com/photos/22198...@n03/3727717220/sizes/l/ Which I think, renders the page OK? What do you think? Barry. A possible-clue maybe that at the time you made that test, you were using 32bit Flash 10.0.12.36 (10.0 r12), whereas I notice I am now using 64bit Flash-10.0.22.87-2 edition, which is more-stable than that older flash which had many-rendering-problems, including fullscreen-crashes on 32bit-Linux. Actually, I block Flash by using the FlashBlock extension. I do not seem to miss any significant content in the Vanguard site by blocking Flash. In general, when a Web page uses Flash, it's merely for a whiz-bang effect and contributes nothing to content. This is true for most Web sites, not just Vanguard. Yes, there are a few sites that require Flash for navigating; for some sites, the home page is merely one large Flash presentation. I consider that to be an abominable practice. (For cases when I cannot avoid viewing a Flash presentation, I'm currently using Flash 10.0.22.87. I'm running WindowsXP SP2.) -- David E. Ross http://www.rossde.com/ Go to Mozdev at http://www.mozdev.org/ for quick access to extensions for Firefox, Thunderbird, SeaMonkey, and other Mozilla-related applications. You can access Mozdev much more quickly than you can Mozilla Add-Ons. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.
I noticed lately Gizmodo's Web pages are rendering slowly and hogging Web browser's CPU and memory badly. Example: http://gizmodo.com/5313690/why-you-cant-complain-about-the-price-of-todays-gadgets Is anyone else having this problem? If so, then what's going on? Thank you in advance. :) -- ... Our world is not an ant farm! --Duncan MacLeod (Highlander Season 3 Finale Part II) /\___/\ / /\ /\ \ Phil/Ant @ http://antfarm.ma.cx (Personal Web Site) | |o o| |Ant's Quality Foraged Links (AQFL): http://aqfl.net \ _ / Nuke ANT from e-mail address: phi...@earthlink.netant ( ) or ant...@zimage.com Ant is currently not listening to any songs on his home computer. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.
On 15.07.2009 10:17, CET - what odd quirk of fate caused Ant to generate the following:? : I noticed lately Gizmodo's Web pages are rendering slowly and hogging Web browser's CPU and memory badly. Example: http://gizmodo.com/5313690/why-you-cant-complain-about-the-price-of-todays-gadgets Is anyone else having this problem? If so, then what's going on? Thank you in advance. :) on FF 1.5.0.9 / XP-SP2 that URL is a crapper... there is a script running that refuses to be killed, so I closed FF, disabled JavaScript and re-opened the URL it works properly that way for me. Try disabling JS, see what happens your end! reg ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.
On 7/15/2009 2:40 AM PT, squaredancer typed: On 15.07.2009 10:17, CET - what odd quirk of fate caused Ant to generate the following:? : I noticed lately Gizmodo's Web pages are rendering slowly and hogging Web browser's CPU and memory badly. Example: http://gizmodo.com/5313690/why-you-cant-complain-about-the-price-of-todays-gadgets Is anyone else having this problem? If so, then what's going on? Thank you in advance. :) on FF 1.5.0.9 / XP-SP2 that URL is a crapper... there is a script running that refuses to be killed, so I closed FF, disabled JavaScript and re-opened the URL it works properly that way for me. Try disabling JS, see what happens your end! Yeah, that did work. Thanks for reproducing it. -- Size isn't everything. The whale is endangered, while the ant continues to do just fine. --Bill Vaughan /\___/\ / /\ /\ \ Phil/Ant @ http://antfarm.ma.cx (Personal Web Site) | |o o| |Ant's Quality Foraged Links (AQFL): http://aqfl.net \ _ / Nuke ANT from e-mail address: phi...@earthlink.netant ( ) or ant...@zimage.com Ant is currently not listening to any songs on his home computer. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.
On 7/15/2009 2:40 AM PT, squaredancer typed: I noticed lately Gizmodo's Web pages are rendering slowly and hogging Web browser's CPU and memory badly. Example: http://gizmodo.com/5313690/why-you-cant-complain-about-the-price-of-todays-gadgets Is anyone else having this problem? If so, then what's going on? Thank you in advance. :) on FF 1.5.0.9 / XP-SP2 that URL is a crapper... there is a script running that refuses to be killed, so I closed FF, disabled JavaScript and re-opened the URL it works properly that way for me. Try disabling JS, see what happens your end! Looks like a known issue: http://getsatisfaction.com/gawker/topics/gawker_media_sites_on_firefox_suck_my_cpu_dry# but OLD. :( -- I go out of my way to avoid stepping on ants. --Terry McGovern, daughter of Senator George and Eleanor McGovern, subject of the book Terry by her father /\___/\ / /\ /\ \ Phil/Ant @ http://antfarm.ma.cx (Personal Web Site) | |o o| |Ant's Quality Foraged Links (AQFL): http://aqfl.net \ _ / Nuke ANT from e-mail address: phi...@earthlink.netant ( ) or ant...@zimage.com Ant is currently not listening to any songs on his home computer. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.
On 15.07.2009 15:07, CET - what odd quirk of fate caused Ant to generate the following:? : On 7/15/2009 2:40 AM PT, squaredancer typed: On 15.07.2009 10:17, CET - what odd quirk of fate caused Ant to generate the following:? : I noticed lately Gizmodo's Web pages are rendering slowly and hogging Web browser's CPU and memory badly. Example: http://gizmodo.com/5313690/why-you-cant-complain-about-the-price-of-todays-gadgets Is anyone else having this problem? If so, then what's going on? Thank you in advance. :) on FF 1.5.0.9 / XP-SP2 that URL is a crapper... there is a script running that refuses to be killed, so I closed FF, disabled JavaScript and re-opened the URL it works properly that way for me. Try disabling JS, see what happens your end! Yeah, that did work. Thanks for reproducing it. 'tis why we are here, is it not ?? :-D reg ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.
On 7/15/2009 2:40 AM, squaredancer wrote: On 15.07.2009 10:17, CET - what odd quirk of fate caused Ant to generate the following:? : I noticed lately Gizmodo's Web pages are rendering slowly and hogging Web browser's CPU and memory badly. Example: http://gizmodo.com/5313690/why-you-cant-complain-about-the-price-of-todays-gadgets Is anyone else having this problem? If so, then what's going on? Thank you in advance. :) on FF 1.5.0.9 / XP-SP2 that URL is a crapper... there is a script running that refuses to be killed, so I closed FF, disabled JavaScript and re-opened the URL it works properly that way for me. Try disabling JS, see what happens your end! reg I've seen Web pages with scripts that, when rendering of the page is done, a script then downloads additional scripts from a server. Sometimes it seems that one of the addtional scripts then downloads even more scripts. Since I have a dial-up Internet connection, this really slows things down. The Web site for the Vanguard Group (mutual funds) is one such site. I generally disable JavaScript when viewing pages at that site. However, I must enable JavaScript for certain pages to complete transactions or view account statements. -- David E. Ross http://www.rossde.com/ Go to Mozdev at http://www.mozdev.org/ for quick access to extensions for Firefox, Thunderbird, SeaMonkey, and other Mozilla-related applications. You can access Mozdev much more quickly than you can Mozilla Add-Ons. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.
On 7/15/2009 7:52 AM PT, squaredancer typed: On 15.07.2009 15:07, CET - what odd quirk of fate caused Ant to generate the following:? : On 7/15/2009 2:40 AM PT, squaredancer typed: On 15.07.2009 10:17, CET - what odd quirk of fate caused Ant to generate the following:? : I noticed lately Gizmodo's Web pages are rendering slowly and hogging Web browser's CPU and memory badly. Example: http://gizmodo.com/5313690/why-you-cant-complain-about-the-price-of-todays-gadgets Is anyone else having this problem? If so, then what's going on? Thank you in advance. :) on FF 1.5.0.9 / XP-SP2 that URL is a crapper... there is a script running that refuses to be killed, so I closed FF, disabled JavaScript and re-opened the URL it works properly that way for me. Try disabling JS, see what happens your end! Yeah, that did work. Thanks for reproducing it. 'tis why we are here, is it not ?? :-D :D -- The life of an ant and that of my child should be granted equal consideration. --Michael W. Fox, Vice President, The Human Society of the United States, The Inhumane Society, New York, 1990. /\___/\ / /\ /\ \ Phil/Ant @ http://antfarm.ma.cx (Personal Web Site) | |o o| |Ant's Quality Foraged Links (AQFL): http://aqfl.net \ _ / Nuke ANT from e-mail address: phi...@earthlink.netant ( ) or ant...@zimage.com Ant is currently not listening to any songs on his home computer. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.
On 7/15/2009 8:38 AM PT, David E. Ross typed: I noticed lately Gizmodo's Web pages are rendering slowly and hogging Web browser's CPU and memory badly. Example: http://gizmodo.com/5313690/why-you-cant-complain-about-the-price-of-todays-gadgets Is anyone else having this problem? If so, then what's going on? Thank you in advance. :) on FF 1.5.0.9 / XP-SP2 that URL is a crapper... there is a script running that refuses to be killed, so I closed FF, disabled JavaScript and re-opened the URL it works properly that way for me. Try disabling JS, see what happens your end! reg I've seen Web pages with scripts that, when rendering of the page is done, a script then downloads additional scripts from a server. Sometimes it seems that one of the addtional scripts then downloads even more scripts. Since I have a dial-up Internet connection, this really slows things down. The Web site for the Vanguard Group (mutual funds) is one such site. I generally disable JavaScript when viewing pages at that site. However, I must enable JavaScript for certain pages to complete transactions or view account statements. Did you ever e-mail the Web team over there? If so, then any luck? :( -- It's them!... Not THEM, the giant ants?! --Girl and Crow /\___/\ / /\ /\ \ Phil/Ant @ http://antfarm.ma.cx (Personal Web Site) | |o o| |Ant's Quality Foraged Links (AQFL): http://aqfl.net \ _ / Nuke ANT from e-mail address: phi...@earthlink.netant ( ) or ant...@zimage.com Ant is currently not listening to any songs on his home computer. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
