Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.

2009-07-19 Thread Ant
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

Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.

2009-07-19 Thread Philip Chee
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 Addon

Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.

2009-07-18 Thread Ant
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 extension

Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.

2009-07-18 Thread NoOp
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 o

Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.

2009-07-18 Thread Ant
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 to

Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.

2009-07-18 Thread NoOp
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, Ant 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? >>>

Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.

2009-07-18 Thread Ant
On 7/18/2009 12:42 PM PT, Benoit Renard typed: Paul Hartman wrote: On Fri, Jul 17, 2009 at 9:30 AM, Ant 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

Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.

2009-07-18 Thread Benoit Renard
Paul Hartman wrote: On Fri, Jul 17, 2009 at 9:30 AM, Ant 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 glob

Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.

2009-07-17 Thread Ant
On 7/17/2009 9:07 AM PT, Paul Hartman typed: On Fri, Jul 17, 2009 at 9:30 AM, Ant 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 s

Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.

2009-07-17 Thread Paul Hartman
On Fri, Jul 17, 2009 at 9:30 AM, Ant 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 maili

Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.

2009-07-17 Thread Ant
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 Quali

Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.

2009-07-16 Thread David E. Ross
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

Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.

2009-07-16 Thread David E. Ross
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. >> >> Examp

Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.

2009-07-16 Thread Barry Edwin Gilmour
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

Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.

2009-07-16 Thread Barry Edwin Gilmour
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-gad

Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.

2009-07-16 Thread Ron Hunter
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/

Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.

2009-07-16 Thread G. R. Woodring
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-co

Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.

2009-07-16 Thread David E. Ross
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-g

Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.

2009-07-15 Thread Ant
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

Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.

2009-07-15 Thread Ant
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 lat

Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.

2009-07-15 Thread squaredancer
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

Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.

2009-07-15 Thread squaredancer
On 15.07.2009 17:38, CET - what odd quirk of fate caused David E. Ross to generate the following:? : 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 s

Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.

2009-07-15 Thread David E. Ross
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/w

Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.

2009-07-15 Thread squaredancer
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

Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.

2009-07-15 Thread Ant
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, the

Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.

2009-07-15 Thread Ant
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-

Re: Rendering problem in Firefox v2.0.0.20 and SeaMonkey v1.1.17.

2009-07-15 Thread squaredancer
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