4 ms·

It's always nice with new features and enhancements but some bugs should first be fixed, like e.g. this one (i cannot update my code to a version higher than 1.

• raleec 15y ago
  Hear hear. I had to work around this insidious creation http://bugs.jquery.com/ticket/8205 http://bugs.jquery.com/ticket/8205 It creates a memory leak (it hit my getJSON calls) that slowly strangled one of my apps until it crashed the browser. I list a lot of hours on that one...
• dmethvin 15y ago
  We closed a huge number of bugs in 1.7, but yes there are about 100 open bugs plus another roughly 100 more that are either feature requests or unverified. For a project the size of jQuery and considering the installed base, I think that is pretty good. And the way these bugs get fixed is by someone spending a lot of time to track them down. As the 1.7 blog post mentions, we definitely welcome any help we can get. We are all volunteers so we don't have the time to quickly track down and fix every bug. In the triage process we put priority on fixing the worst bugs that affect the most people. I personally triaged both #9646 and #8205 so we could mark them as verified, but tracking down and solving older-IE problems can be torture given the crude stone debugging tools available in those environments. If you have a high threshold for pain, we could certainly use your help.