One for the Home Team (but see PS) <g>
Okay, here is todays update. As I said, so far I have Adblock enabled, CNET cookies were deleted with CCleaner, and this morning I finally enabled NoScript.
For more than 12 hours today, I have had no crashes. I guess our side won one <grin>. However, Ill tell you for sure, working the internet with NoScript enabled is like trying to run in a sack race <g>. With no scripts allowed, many of the most user-friendly parts of every web page are no longer available.
With NoScript you dont get drop-down menus and embedded videos (e.g., YouTube). Other elements are probably missing, too, that I dont even know about yet. And it took me a while to even figure out that you can temporarily enable scripts on a page to get work done. Still, its like having to do everything twice.
I wonder if thats the price some of us have to pay to use FireFox? Even with that, FF is still more enjoyable to work with than other browsers Ive tried. But Im telling you, with Firefox partially neutered, its not exactly like the modern age of digital communication anymore <g>.
As Mark said, I cant figure out why Mozilla doesnt throw everything it has got at these major, wide-spread problems. All the problems I know about only started with Version 3.0 . This crashing problem is clearly evident by just Googling a search for Firefox and crash. I just checked an there were 1,010,000 search returns. Isnt that enough to make Mozilla want to do something drastic?
Thanks for your continued help with this. I will soon try to disable NoScript to see if that really is the key to not having crashes. Ill let you know what I find. Meanwhile, if anyone things of something new, please post it. Ill be paying close attention.
PS - I spoke too soon. Just as I clicked "Preview Post" for this message, I lost my entire message. This is an old problem at CNET and it predates FF versions 3+. I'm going to try again now by just directly posting but I bet I lose this post, too.
PPS - That's two attempts to post and two losses of messages. Remember, this problem was prevalent a few years ago among many people. Right now I'm attempting a post with Maxthon. If this works, Firefox is still junk as it works with CNET.
Was this reply helpful? (0) (0)