> > [
http://dev.jquery.com/ticket/3054]
> > That ticket is actually true, did that happen all the time ?
>
> I'm not sure about this - is this an issue with the select event?
> Maybe it's not firing as we expect it to?
But it does fire on FF. Maybe that event doesn't even work on IE
(that'd be ODD).
> > [
http://dev.jquery.com/ticket/2997]
> > There's a cool patch, but it breaks some tests, I'm not sure why.
>
> I think we looked at using outerHTML back when we first re-wrote this
> method - but it didn't provide us with the functionality we required.
> I don't remember the exact details offhand - which tests are failing?
Some tests of wrap(), wrapAll() and 1 from clone().
> > [
http://dev.jquery.com/ticket/2652]
> > The patch fixes that, but... do we want to support the situation ?
>
> It seems like a good thing to support. Do you think we could try and
> remove the use of jQuery.browser here? It seems like it may not be
> necessary.
Done, fixed. FF required a little tweak. val() was lacking some more
tests.
> > [
http://dev.jquery.com/ticket/2968]
> > What do you think ? I'd go for the short approach.
>
> I'm trying to think of a situation where the DOM node methods would be
> passed in - but can't think of one. Let's go for the short method.
Done.
> > [
http://dev.jquery.com/ticket/3116]
> > I can't really test that.. does the patch fixes it ? do we want to
> > support SVG ?
>
> I don't think your patch would be sufficient here - since it would
> have to work on every SVG element. Maybe a check to see if the
> nodeName of the documentElement is not equal to 'html' would do the
> trick?
I don't know much about SVG, but aren't svg nodes descendants of the
document element ? they're still in the DOM.
--
Ariel Flesler
http://flesler.blogspot.com
