I'm sorry... I thought that jQuery's prime goal was to provide a cross-browser library that saved developers the hassle of having to account for browser bugs...?
I'm aware that you probably never tested v2.0 on FF 3.6 and didn't know it failed loading completely until now, and that's why I created this bug report.
The release of jQuery 2.0 is good news, because we could simply provide a different version of jQuery depending on the current browser (a cleaner, tighter one for modern browsers, a more convoluted, bigger one for oldIE). So, my code had $version = we::is('ie[-8]') ? '1.9.0' : '2.0.0b1', which should be easy enough to understand. But the jQuery blog does NOT mention that other older browsers were dropped. After confirming that Firefox 4 ran jQuery just fine, I had to change my code to we::is('ie[-8],firefox[-3.6]').
So, yes, at the minimum, I'd appreciate that the jQuery team updates the browser compatibility tables saying precisely whether the software will fail *loading at all* on an older browser. Would also be good to announce such things on the blog.
For your information, I managed to make Firefox 3.6 run jQ 2.0 by changing just four lines. My select box works, and it's a rather complex custom piece of code, but full FF3.6 compat might need more work. Is it worth it? I don't know. I don't think so. I'm just posting the diff patch for those interested.