Conversation

Notices

  1. Drew Drew

    @haganbmj If it helps, it's only been an issue the last week or two. Before that there was no issue.

    Thursday, 14-Jul-11 19:34:05 UTC from web
    1. Brendan Brendan

      @drewdle Mmkay, so it seems that Firefox wants to run a native 1.4.4 jQuery on the page, instead of the 1.3.2 that runs on Chrome. Greasemonkey apparently doesn't fully support 1.4.4 so I'm working on a hack to degrade the version just for this page q.q

      Thursday, 14-Jul-11 20:10:05 UTC from web
      1. Drew Drew

        @haganbmj Thank you for the effort! I would literally send you cupcakes if I could! I am so much more a hardware than software kind of person, so I had no idea how to interpret that error.

        Thursday, 14-Jul-11 20:12:52 UTC from web
        1. Brendan Brendan

          @drewdle I was just reading online about Firefox jQuery errors - and that seems to be the most common problem with Greasemonkey. Soo, we'll see what happens ~ if worst comes to worst, I'll just embed the full jQuery library in the script and hopefully that'll do it.

          Thursday, 14-Jul-11 20:14:42 UTC from web
          1. ★ ★

            @haganbmj Doesn't StatusNet already use JQuery for everything? Seems you should be able to just hijack that.

            Thursday, 14-Jul-11 20:16:40 UTC from web
            1. Brendan Brendan

              @starshine Yeah - it does, and that's what I was doing and it worked fine on Chrome. For some reason Firefox uses jQ 1.4.4 and that seems to have issues with Firefox?

              Thursday, 14-Jul-11 20:18:30 UTC from web
              1. Brendan Brendan

                @haganbmj @starshine *issues with greasemonkey

                Thursday, 14-Jul-11 20:20:04 UTC from web