| > To be perfectly honest, I think it's a bit of a reach to suggest that I "probably need jQuery" because strict mode limitations caused problems within jQuery once upon a time (like, isn't that basically jQuery fixing a problem it introduced?), No, the point was that it highlights an issue that exists with some browser. Also, I didn't name this thread, notice in my gist it doesn't say anything about needing anything. I was merely presenting facts. > I'd be surprised if none of the others were at all questionable. If you'd like to spend the time going through each one of them with me, we can meet on IRC and work through them all. We might even be productive in eliminating some unnecessary code if we find issues that no longer exist in a browser's current and last current release. Let me know? To your last point, I again, I didn't name or post this thread. Did you read what I wrote in the gist? I think you can't really argue with this: "The following links will bring you to line in the jQuery (current master, is a 2.1.x build with no oldIE-specific code) source above. The line (and probably adjacent lines) will identify some existing browser issue that jQuery must account for when providing an API for consistent browser/DOM programming semantics." That's all I said. So are we square? Wanna work on these with me? I'm a nice guy, I promise. |