Calling jQuery("html")[0].removeAttribute throws exception in IE <9

[Rick Waldron]

As reported on twitter:

​http://twitter.com/#!/angusTweets/status/75758118943993856

[Rick Waldron]

See also: ​https://gist.github.com/1001726

[Rick Waldron]

Initially I assumed this would be straight forward, however attempts at writing a failing test ( based on Line 6-7 of the gist provided by Angus Croll [ here: ​https://gist.github.com/1001726 ]) are unsuccessful.

This test case produced by jdalton was also unsuccessful in reproducing the issue. ​https://dl.dropbox.com/u/513327/jq_removeAttribute.html

Verification of approach is appreciated, here is the current test I've written:

​https://github.com/rwldrn/jquery/blob/a3a301bb5d2b7dcdc1ba12f53b70cddc10607774/test/unit/data.js#L512-535

[Timmy Willison]

This is a common enough problem, I don't think we need a working test case for it. IE calls the function even when accessed. This often works anyway, but it's best practice to check with typeof or do "removeAttribute" in elem (I prefer the latter).

[anonymous]

I don't think it's a common enough problem. I am pretty well versed on IE bugs and this one I am not familiar with. Without a working (failing) test case I would simply consider this dev error in diagnosing the problem.

[jdalton]

I forgot to login. The previous comment was mine :P

However I do use an isHostType() function to help avoid these kinda of errors in IE for known problem properties and unknown properties.

​http://jsbin.com/erukiv

[dmethvin]

Lacking a test case, I'm going to close this bug. Twitter is not a good way to report bugs, and his suggested fix of checking for typeof==function doesn't work in IE anyway, as I'm sure we all know.

[dmethvin]

Oh, I see what timmywil is saying and yes, IE will sometimes call a host function even if you just access it as a property. If you think there's enough info and it can/should be fixed, feel free to reopen.

[Timmy Willison]

I'm just now seeing the responses. Yes, the common IE issue i was referring to was calling the function when only accessed as a property. We've run into that several times, but it is not an issue with every function.