JavaScript Turnoff Week

Tuesday, May 10th, 2005 at 7:51 PM | 2 comments Category: Meryl's Notes Blog

April 25 was TV turnoff week. Currently, I’m on hour one of JavaScript turnoff week. I hope it won’t last the whole week because surfing without JavaScript has instantly turned tedious. Why is JavaScript turned off? Because of the Firefox security advisory. Until the the problems go away, Mozilla recommends turning off JavaScript and disabling the browser’s software installation feature. To do this, click Tools, Options, and deselect “Allow web sites to install software” found in the Web Features menu OR deleting all of the allowed sites.

First “I miss JavaScript” encounter. Gmail. I have to use the basic HTML view. If I select messages to trash or move to another folder, instead of selecting them, choosing the action, and it happens. I have to click the Go button. The basic interface isn’t as smooth as the standard. When I want to select all unread items, I can’t. The option went bye-bye.

Next, I go to another web-based email account and I can’t do anything. I selected junk to delete, but the emailbox just stares like a deer caught in the headlights. Gave up.

Decided to go see what the latest free jewelry item is on the stage. Didn’t like it and looked to see how much time was left as new items appear every 15 minutes or when the stock sells out. Uh-oh. No countdown. Also, when 15 minutes are up, the jewelry item sits still, not going anywhere until I hit reload to see the next item. Damned that JavaScript.

That’s the pain of keeping safe for you. I have faith the Mozilla crew resolves the problems quicky.

Ha. Now I can’t post this entry until I turn JavaScript back on. Boy, that didn’t last long.

Subscribe: RSS or E-mail

2 comments

  • Posted by: Robert on May 12th, 2005, 7:43 AM

    Fx 1.0.4 to the rescue!:
    (available at mozilla.org)

    Quick enough? :)

  • Posted by: tndal on August 7th, 2006, 1:13 AM

    Turn it on. You’ll only have to turn it off again when the next Javascript exploit is found. And what do you do when an AJAX page downloaded in your browser starts scanning your internal network’s ports? Hmmm, how will you even know this is happening unless you’re run a tight firewall on each machine on the internal network. And if you’re doing that, why have an internal network anyway?

    Any downloaded code is inherently insecure. That has always been true. The only secure systems are those that do not permit downloading code. Javascript must die.

Post a comment (or leave a trackback)

RSS Subscribe to be notified when new comments are added.