I'm using jQuery 1.3.2 with JBoss RichFaces 3.3.0 and found some strange behavior after the upgrade from jQuery 1.2.6. In particular, on Firefox 3.0.x and earlier, certain selectors will now break after an AJAX update to the DOM using replaceChild (which is apparently what RichFaces/a4j does in FF).
Part of the issue is explained and demonstrated at http://dev.jquery.com/ticket/4218 The workaround patch included by the author only fixes part of the issue (a few instances of undesirable case-sensitivity), but after some more tests it looks like there are other issues and this might be just one of multiple bugs or maybe part of a bigger bug? The additional tests are on the attachment: http://dev.jquery.com/attachment/ticket/4218/ajax-test2.html Feel free to test on Firefox and on Opera as well. This is probably an issue(s) that should be filed separate from 4218, so before I overload that ticket even more, my question is -- whose bug is it? Is it jQuery/ Sizzle's, since some of the selectors worked in 1.2.6 but not in 1.3.2? Is it JBoss/RichFace's since their use of replaceChild in Firefox might be the culprit? Is it Mozilla/Firefox's for their possibly-buggy implementation of replaceChild? Some confluence of bugs/ culpas? Just want to get it filed away, so any advice would be greatly appreciated! Thanks, Usman --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to jquery-dev@googlegroups.com To unsubscribe from this group, send email to jquery-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
