Subscribe via RSS Feed

Unresponsive Script

[ 34 ] February 22, 2013 | Robert Farley

All,

Have received word from several people that we’re getting an unresponsive script warning in FF.  We’re working on it.

The Management

Comments (34)

Trackback URL | Comments RSS Feed

  1. Erik Loomis says:
    February 22, 2013 at 11:37 am

    We have management?

    Reply
  2. zombie rotten mcdonald says:
    February 22, 2013 at 11:38 am

    thought it was just me. FWIW, I thought it might be related to the most recent update of FF, it showed up right after I updated.

    Reply
  3. The Dark Avenger says:
    February 22, 2013 at 12:22 pm

    I just updated my SeaMonkey browser, and it shows up in it as well.

    Reply
  4. MobiusKlein says:
    February 22, 2013 at 12:28 pm

    http://platform.twitter.com/widgets.js:5 , but you already knew that.

    Reply
  5. BlueLoom says:
    February 22, 2013 at 1:16 pm

    1:15 EST, still getting error msg. Using most recent FF update.

    Reply
  6. Steve LaBonne says:
    February 22, 2013 at 1:25 pm

    NoScript is your friend.

    Reply
  7. Dr.KennethNoisewater says:
    February 22, 2013 at 1:31 pm

    I WON’T BE IGNORED, SCRIPT!

    Reply
  8. Manju says:
    February 22, 2013 at 2:16 pm

    an unresponsive script warning in FF

    There’s a viagra joke lurking in there somewhere

    Reply
  9. Barry says:
    February 22, 2013 at 2:27 pm

    What’s worse is that Firefox keeps getting hung up, despite having an option to terminate the script in the future without asking.

    Reply
    • Vance Maverick says:
      February 22, 2013 at 2:36 pm

      I’ve been using Chrome for work and FF for personal stuff — since this problem, I’m using Chrome for both, with separate user profiles. (I had tried the feature before, and hit some bugs, but now it’s working perfectly.)

      Reply
      • Steve LaBonne says:
        February 22, 2013 at 3:36 pm

        IMHO Firefox with NoScript > Chrome > Firefox without NoScript. Nothing can beat not letting ANY scripts run unless you say they can. Adblock Plus and NoScript are the two things that make FF still worth using.

        Reply
  10. Michael H Schneider says:
    February 22, 2013 at 2:34 pm

    That’s not an unresponsive script.

    That’s a stalwart and principled insistence on abiding by traditional American conservative political and cultural values.

    Also: We can haz management?

    Reply
  11. Linkmeister says:
    February 22, 2013 at 3:57 pm

    Looks like it might be the widget that allows readers to Tweet the post. You could remove that and see if the script errors continue.

    Reply
  12. Robert Farley says:
    February 22, 2013 at 4:07 pm

    One of the twitter buttons removed; script still there?

    Reply
  13. partisan says:
    February 22, 2013 at 4:47 pm

    Yes, I noticed the problem. Good to know that I wasn’t being punished for disagreeing with the blog on the constitutionality of same sex marriage.

    Reply
  14. Linkmeister says:
    February 22, 2013 at 4:55 pm

    Yeah, I still got the error, but the link to Twitter.com/share is still there at the bottom of the post, too.

    Reply
  15. Timb says:
    February 23, 2013 at 7:33 am

    No problems with he Ipad

    Reply
  16. grackle says:
    February 23, 2013 at 12:53 pm

    script still there @12:56 PM 02/23 EST

    Reply
  17. bloviator says:
    February 24, 2013 at 5:18 pm

    Still doing it, not worth dealing with. Will check back in a week.

    Reply
  18. Hanspeter says:
    February 25, 2013 at 1:55 pm

    Seems fixored?

    Reply

Leave a Reply




If you want a picture to show with your comment, go get a Gravatar.

    • Switch to our mobile site