Menu
By:
Filters
What's new

Upgrading to jQuery v1.9.1

K

kbambz

Mastermind of Pretty Things
Staff member
The forum software we use relies on a very outdated version of jQuery (v1.5.3 if anyone's curious; to put this in perspective, v1.9.1 is the current release and v2.0.x is already in beta).
Despite a rather nasty web of dependencies, I'm going to attempt to migrate AltTabMe to jQuery v1.9.1 over the next few days. /allthethings

Chances are this will break things. We try to keep your experience on AltTabMe as bug-free as we can, but these changes are broad enough where our basic testing is likely to miss at least something obscure somewhere.

If you encounter an error while navigating the site (Ajax errors in particular; you'll know them by a generic error message along the lines of "There was an error with your request; details can be found in your browser's console"), please respond to this thread and let us know ASAP.


HOW TO PROVIDE USEFUL ERROR REPORTS
(and make Katie <3 you)

First, you'll need a tool to view your browser's console. Chrome and IE 8+ come with tools out of the box. Firefox has a nifty add-on that gives you almost an identical view to what you'd see in Chrome.

Chrome
  • Chrome Developer Tools: Overview
  • Chrome Developer Tools: Using the Console: Errors & Warnings
  • View > Developer > Javascript Console
    assert-failed.png
    filter-errors.png
Firefox
Internet Explorer

Now that you have the ability to inspect console output, the next time you receive an error on the site, follow these steps:
  1. Open the console (you will need to have completed the instructions above based on your browser beforehand).
  2. You'll most likely want to filter your console output to only show "Errors" (it's generally a tab in the console view; in Chrome it's at the bottom of the window and in Firebug it's right above the console view). Don't worry about this if it's not clear how to.
  3. Depending on your browser and the particular error, there may be an "expand" upside-down triangle or [+] icon to the left of any given error. For all such errors, click the icon to expand and reveal a few more lines of text (this provides a brief stack trace).
  4. Simply copy and paste the contents of the console into a post in response to this thread, along with the time of error, what browser you were using, and a summary of what action(s) you were performing leading up to the error. The more detail you can and are willing to provide, the better and faster we'll be able to address the issue!
Thanks everyone! If you have questions or concerns, as always, don't hesitate to speak up.
 
By the way, the obnoxious Unsafe JavaScript attempt to access frame with URL... errors are generated by embedded content from YouTube and Adsense. You can thank Google for them. :angrybirds11:

After an hour or two of digging, I had found a whole lot of people reporting the same issue for both services dating as far back as 2009, and zero applicable solutions (or should I say workarounds, since the real issue is in the way they serve their iframe content). I'll continue to poke around for a solution, but for now just regard these errors as innocuous, as the rest of the internet appears to be doing.

TL;DR: Ignore those errors. If you feel like it, you're welcome to yell at Google alongside the masses:
 
They obviously don't want to fix it because they are getting $20 each time one part of the thing happens. They are raking in the cash it looks like.
 
Java.. is that a fruit?[DOUBLEPOST=1363270603,1363270591][/DOUBLEPOST]No waitt..... that is Guava..
 
You must log in or register to reply here.
Top Bottom