Stephen Woodbridge schrieb:
> Dave Methvin wrote:
>>>> I'd would like to know if possible what is the
>>>> status on the bug 164 in jquery.
>>> As far as I know this is still an open issue. I am hoping
>>> the one of the developers that has some expertise in
>>> IE will take pity on us and try to fix this bug sooner
>>> rather than later ;).
>> If it's being ignored that either means it's hard, it's not fun, or both. :)
>
> Yeah, I figured as much. But hey, no pain, no gain! The bigger the
> challenge, the bigger the glory! ;) or something like that.
>
>> Was the problem the .getAttribute(..., 2) in .attr()? That was probably put
>> in as a patch to the situation where IE fiddles with href attributes unless
>> you call it like .getAttribute('href', 2). Maybe you could just take out the
>> second argument as a workaround for now? It's worth a try.
>>
>> Perhaps a permanent fix would be to only use the two-arg form of
>> getAttribute if it's one of the troublesome attributes like href. I guess
>> there is no way to know if we're working on an XML document?
>
> I think there are actually more than one problem here. I can't speak to
> Clem's problem, but my is that the that xpath searches on xml documents
> are failing in IE as documented in the bug. I spent about two days
> poking at it in IE, but I just don't have the knowledge or experience to
> sort out this type of problem. So I'm just stuck until some of you
> wizards put you minds to squashing this bug.
>
> Many thanks to all of you that work so hard to make jQuery so wonderful.
> I really love working with it.
>
> -Steve
Hey Steve, as Dave said, this one is hard *and* no fun... But the bug
didn't occur in pre 1.0, so theres still hope!
-- Klaus
_______________________________________________
jQuery mailing list
[email protected]
http://jquery.com/discuss/
