What other problems did the second fix (or hack, as it's more aptly called) cause? Just wondering what sort of things I should test as I try and find a better solution to it. Any suggestions for accomplishing the same behavior for the second fix without resorting to an IE specific "hack"?

On 10/11/06, Jörn Zaefferer <[EMAIL PROTECTED]> wrote:
Peter Woods schrieb:
> The fix is quite simple, as far as I can tell... simply replace the
> line in question with this:
>
> // Handle HTML strings
> var m;
> if (typeof a == "string") m = /^[^<]*(<.+>)[^>]*$/.exec(a);
This works and is now in SVN, tested.
>
> } else if ( jQuery.browser.msie && elem.getAttribute(name) !=
> undefined ) {
>     if ( value != undefined ) elem.setAttribute( name, value );
>     return elem.getAttribute( name );
This caused quite a lot of other problems
> contains: "((a.firstChild &&
> a.firstChild.nodeValue)||a.innerText||a.innerHTML).indexOf(m[3])>=0",
Is added to SVN, but yet untested...

-- Jörn

_______________________________________________
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

_______________________________________________
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Reply via email to