Re:You might not need jQuery (2014)
by cosmotic on Wednesday January 13, 2021 @10:39PM
(#25771591)
I thought a big part of the initial sales pitch was not having to deal with cross-browser compatibility issues.
[ Parent
| on HN ]
document.querySelector was not available in IE 6 and 7.
Dealing with those versions was where jQuery really earned its spot in the JS universe. It was a lot to remember where all the quirks were and the incantations to work around them.
Re:You might not need jQuery (2014)
by codeisawesome on Thursday January 14, 2021 @12:04AM
(#25772317)
IE 6. Now that's a name I haven't heard in a long time...
Just patched a problem in a WordPress site due to (now broken) support for IE7 two days ago. The elders of the Internet are still around. ;-)
Re:You might not need jQuery (2014)
by spicybright on Thursday January 14, 2021 @08:50AM
(#25776204)
I'm so sorry. Do you want to talk about it? :P
I'm not sure. It was kind of traumatic, but on the other hand it's a very old site, so it was obvious that there might be some dead bodies in the basement. Found one, ignored the others.
The IE 7 compatibility code broke the site in modern browsers, or did you really get a visitor on a Windows 98 machine?
It was a bug in an old version of superfish.js which relied on a deprecated jQuery function to detect the browser. $.browser broke in the new(er/est) version of jQuery which is integrated in that site.
Re:You might not need jQuery (2014)
by user3939382 on Thursday January 14, 2021 @06:52AM
(#25775293)
The longer the better. What a neverending nightmare it was.
Re:You might not need jQuery (2014)
by np_tedious on Wednesday January 13, 2021 @11:43PM
(#25772127)
Maybe there was more than one big part!