wrap cause selectedIndex reset in opera

[sayer_jim@…]

Tested in opera 10.62/windows XP sp2

Test case: <select id='test'> <option>option1</option> <option>option2</option> </select> <input id='go' value='go' type='button'></input>

$('#go').click(function(){

$('#id').wrap('<div/>');

)}

the above code will reset selectedIndex to 0(option1) for 'test' element tested both with 1.4.2 and 1.4.4 version of jquery

[Rick Waldron]

You do realize there is no element that matches $("#id"), right?

[anonymous]

Sorry a mistake, yes it should be $('#test') instead of $('#id')

[addyosmani]

I've reproduced your code here with an additional check for selectedIndex ​Live Test Case. Testing this on XP SP2 using Opera 10.62 (and jQuery 1.4.4) I'm getting the same output and behavior as per what I'm seeing in the latest versions of Firefox, Chrome and Safari. I've also run this against jQuery 1.3.2 and it's also working fine there too.

Closing as worksforme, however if you have additional information or tests you're able to provide us with which we can confirm as having broken behaviour for older versions of Opera we would be happy to investigate.

[anonymous]

Just tested live case on jsFiddle, still broken in my browser.

Some additional information: Opera 10.62 is international version, version details: 编制 3500 平台 Win32 系统 Windows XP 浏览器识别 Opera/9.80 (Windows NT 5.1; U; zh-cn) Presto/2.6.30 Version/10.62

All other browsers (Chrome,FF,IE and Safari) tested normal. I then upgraded to version 11 and the bug is still there. However a version 11 installed in XP virtual machine is free of this bug, maybe this is related to OS?

[jitter]

I can ​reproduce this too (video) with Opera 10.63, Windows XP SP2 and jQuery 1.4.4 . Opera 11 is fine for me.

But it's not jQuery doing something inherently wrong as this ​test case with plain js shows. This produces the exact same bug for me with Opera 10.63

[snover]

Works in Opera 11, and this won’t get looked at/patched before O10 support is discontinued, so closing wontfix in order to avoid having latent open low-priority bugs.