Hrm, not sure, that workaround always works for me, but I have had issues with pathing in the past so I usually just use an absolute path instead. You can see it in action at: http://www.crosscreekplantation.com .

SB

It's not something I do in the skin file, I upload the .js file to the wwwroot/js folder and edit the default.aspx as per the instructions. I'm not sure how you'd go about doing this via the skin file.

SB

I read somewhere not too long ago that this is only an issue with IE and it is the result of litigation against Microsoft.  I haven't run into this problem with Firefox or Opera.

If I remember correctly, Microsoft does not own the intellectual property for these controls; they are licensed to use them.  But apparently Micosoft wasn't living up to their end of the licensing agreement.  They were sued and lost.  Part of the judgement against them was to remove native functioning of these controls in IE.