Unresponsive Script

February 22nd, 2013 by 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

Posted in General | 34 comments

Previous post:
Next post:

34 comments on this post.

  1. Erik Loomis:

    February 22nd, 2013 at 11:37 am

    We have management?

  2. zombie rotten mcdonald:

    February 22nd, 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.

  3. rea:

    February 22nd, 2013 at 11:53 am

    You need to strike, then.

  4. The Dark Avenger:

    February 22nd, 2013 at 12:22 pm

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

  5. MobiusKlein:

    February 22nd, 2013 at 12:28 pm

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

  6. BlueLoom:

    February 22nd, 2013 at 1:16 pm

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

  7. Steve LaBonne:

    February 22nd, 2013 at 1:25 pm

    NoScript is your friend.

  8. Dr.KennethNoisewater:

    February 22nd, 2013 at 1:31 pm

    I WON’T BE IGNORED, SCRIPT!

  9. zombie rotten mcdonald:

    February 22nd, 2013 at 1:38 pm

    what, are you going to throw yourself into the boiling water?

  10. Manju:

    February 22nd, 2013 at 2:16 pm

    an unresponsive script warning in FF

    There’s a viagra joke lurking in there somewhere

  11. Barry:

    February 22nd, 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.

  12. Michael H Schneider:

    February 22nd, 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?

  13. Vance Maverick:

    February 22nd, 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.)

  14. Substance McGravitas:

    February 22nd, 2013 at 2:41 pm

    Those who don’t use Twitter can just put the whole Twitter domain into their adblocker.

    Satisfying!

  15. Dr.KennethNoisewater:

    February 22nd, 2013 at 3:09 pm

    Talk about a rabbit, stewing!

  16. Steve LaBonne:

    February 22nd, 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.

  17. Linkmeister:

    February 22nd, 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.

  18. Robert Farley:

    February 22nd, 2013 at 4:07 pm

    One of the twitter buttons removed; script still there?

  19. partisan:

    February 22nd, 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.

  20. Manju:

    February 22nd, 2013 at 4:52 pm

    Its worse than that. You are Management.

  21. Linkmeister:

    February 22nd, 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.

  22. BlueLoom:

    February 22nd, 2013 at 5:43 pm

    Script still there at 5:43 EST.

  23. Book:

    February 22nd, 2013 at 10:01 pm

    It’s a write-to-work blog, alas.

  24. hylen:

    February 22nd, 2013 at 10:59 pm

    NoScript is your friend.

    Yup. Word to the wise.

  25. hylen:

    February 22nd, 2013 at 11:00 pm

    Good summary.

  26. STH:

    February 22nd, 2013 at 11:06 pm

    The script errors will continue until morale improves.

  27. Vance Maverick:

    February 23rd, 2013 at 12:11 am

    I like it. Quicker response even than Chrome. (Perhaps there’s an equivalent there? Whatever.)

  28. Timb:

    February 23rd, 2013 at 7:33 am

    No problems with he Ipad

  29. Woodrowfan:

    February 23rd, 2013 at 9:44 am

    thanks for the suggestion. I’ve notice more and more websites hang FF. I added No Script. let’s see if that helps.

    I just don’t want to use Chrome, as I don;t trust Google not to record every single thing.

  30. Bill Murray:

    February 23rd, 2013 at 11:41 am

    this deserves several harrumphs

  31. grackle:

    February 23rd, 2013 at 12:53 pm

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

  32. The Dark Avenger:

    February 23rd, 2013 at 1:47 pm

    NoScript works in SeaMonkey, and I would think works in MF.

  33. bloviator:

    February 24th, 2013 at 5:18 pm

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

  34. Hanspeter:

    February 25th, 2013 at 1:55 pm

    Seems fixored?

Leave a comment