4 ms·

That doesn't stop their need to work around the bugs in the existing version. It's easier for the jQuery maintainers to work around a Webkit bug than to submit

That doesn't stop their need to work around the bugs in the existing version. It's easier for the jQuery maintainers to work around a Webkit bug than to submit a patch and hope that it gets applied in the next few years. EDIT: I misread the article on how the bug was actually handled, and that it was fixed five years after it was reported, not that it took five years to apply the patch. However, it still is easier for the library maintainers to use a workaround than to patch the browser itself, especially when legacy versions still need to be supported.

PavlovsCat 14y ago
"submit a patch and hope that it gets applied in the next few years." What are you talking about? Comment #5 From Morten Stenshorne 2013-02-13 00:01:06 PST Created an attachment (id=188026) 12 hours and 12 minutes later: Comment #11 From WebKit Review Bot 2013-02-13 12:13:22 PST Clearing flags on attachment: 188026
- kevingadd 14y ago
  If you read the linked post the complaint is that vendors like Apple and the developers of packages like PhantomJS regularly ship versions of WebKit that are months or years out of date. the jQuery dev team could fix every outstanding bug in WebKit and they would still have to ship compatibility hacks in jQuery for years-old builds of WebKit.
  - PavlovsCat 14y ago
    If you read the linked post the point is that if they fixed every outstanding bug via a JavaScript workaround, everybody else would have even less incentive to fix anything. Also, if there is a long delay in the pipeline, that is no justification for even more delay in putting something into it, just like things being put into it quickly would be no justification for not trying to shorten that delay. If you don't fix any bugs, but Apple etc. update overnight everything via WiFi or Ninjas, jQuery will still keep accumulating fixes for old bugs and explode - on the other hand, if you fix bugs quickly, even a 3 year delay with vendors means that jQuery will "only" have to carry fixes for bugs of the last 4-5 years, not for bugs that existed since the dawn of time. I think that is not even the job of jQuery, anyway; it fixes bugs that have to do with using jQuery and plugins, providing a consistent baseline despite browser bugs.
- dmethvin 14y ago
  I suspect that was a well-orchestrated commit to show that Opera had joined the WebKit collective. It was mentioned in Opera's press release.

PavlovsCat 14y ago

"submit a patch and hope that it gets applied in the next few years." What are you talking about? Comment #5 From Morten Stenshorne 2013-02-13 00:01:06 PST Created an attachment (id=188026) 12 hours and 12 minutes later: Comment #11 From WebKit Review Bot 2013-02-13 12:13:22 PST Clearing flags on attachment: 188026

kevingadd 14y ago
If you read the linked post the complaint is that vendors like Apple and the developers of packages like PhantomJS regularly ship versions of WebKit that are months or years out of date. the jQuery dev team could fix every outstanding bug in WebKit and they would still have to ship compatibility hacks in jQuery for years-old builds of WebKit.
- PavlovsCat 14y ago
  If you read the linked post the point is that if they fixed every outstanding bug via a JavaScript workaround, everybody else would have even less incentive to fix anything. Also, if there is a long delay in the pipeline, that is no justification for even more delay in putting something into it, just like things being put into it quickly would be no justification for not trying to shorten that delay. If you don't fix any bugs, but Apple etc. update overnight everything via WiFi or Ninjas, jQuery will still keep accumulating fixes for old bugs and explode - on the other hand, if you fix bugs quickly, even a 3 year delay with vendors means that jQuery will "only" have to carry fixes for bugs of the last 4-5 years, not for bugs that existed since the dawn of time. I think that is not even the job of jQuery, anyway; it fixes bugs that have to do with using jQuery and plugins, providing a consistent baseline despite browser bugs.
dmethvin 14y ago
I suspect that was a well-orchestrated commit to show that Opera had joined the WebKit collective. It was mentioned in Opera's press release.