3 ms·
That wasn't a bug that jQuery reported or has encountered. The ones we report probably aren't half a line of code to fix. And as for why we don't fix them ourse
by dmethvin 14y ago
That wasn't a bug that jQuery reported or has encountered. The ones we report probably aren't half a line of code to fix. And as for why we don't fix them ourselves, I can't speak for the rest of the jQuery team but one unpaid volunteer open source job is plenty for me.
- bdash 14y agoIs it safe to assume that any bugs that you're running in to are being reported to the browser vendors?
- jgraham 14y agoThe most telling thing that jQuery (or any other library) could do would be to have a policy that any browser bug workaround has to be accompanied by both a) a bug report to the browser vendor and b) a corresponding test to the relevant W3C testsuite. That would put public pressure on browser vendors to fix the issue, and provide the jQuery team with a convenient way of telling when the workaround was no longer needed.
- bdash 14y agoSpeaking as someone that has spent time working on a web browser, that would be a fantastic policy, both for browser developers and for web standards in general.
- bzbarsky 14y agoSadly, from what I can tell, at least some browser vendors (and more importantly the developers working for them) don't particularly care about whether they pass W3C test suites....
- dmethvin 14y agoYes, we try to put a link into our tracker with the ticket in their tracker for both bugs and spec ambiguities. Note that several are a few years old and are still open. http://bugs.jquery.com/ticket/11663 http://bugs.jquery.com/ticket/11663 http://bugs.jquery.com/ticket/12986 http://bugs.jquery.com/ticket/12986 http://bugs.jquery.com/ticket/12968 http://bugs.jquery.com/ticket/12968 http://bugs.jquery.com/ticket/12964 http://bugs.jquery.com/ticket/12964 http://bugs.jquery.com/ticket/10509 http://bugs.jquery.com/ticket/10509 http://bugs.jquery.com/ticket/12577 http://bugs.jquery.com/ticket/12577