Side navigation
#8038 closed bug (wontfix)
Opened January 22, 2011 08:51PM UTC
Closed February 06, 2011 04:03PM UTC
wrap cause selectedIndex reset in opera
Reported by: | sayer_jim@hotmail.com | Owned by: | sayer_jim@hotmail.com |
---|---|---|---|
Priority: | low | Milestone: | 1.next |
Component: | manipulation | Version: | 1.5rc1 |
Keywords: | opera | Cc: | |
Blocked by: | Blocking: |
Description
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
Attachments (0)
Change History (7)
Changed January 22, 2011 09:14PM UTC by comment:1
owner: | → sayer_jim@hotmail.com |
---|---|
status: | new → pending |
Changed January 23, 2011 09:09AM UTC by comment:2
Sorry a mistake, yes it should be $('#test') instead of $('#id')
Changed January 23, 2011 09:13PM UTC by comment:3
priority: | undecided → low |
---|---|
resolution: | → worksforme |
status: | pending → closed |
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.
Changed January 24, 2011 07:29AM UTC by comment:4
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?
Changed January 25, 2011 12:19AM UTC by comment:5
_comment0: | I can [http://www.vidup.de/v/oGzJN/ reproduce this too] 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 [http://jsfiddle.net/3ManY/3/ test case] with plain js shows. This produces the exact same bug for me with Opera 10.63 → 1295914862717927 |
---|---|
component: | unfiled → manipulation |
resolution: | worksforme |
status: | closed → reopened |
version: | 1.4.4 → 1.5rc1 |
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
Changed January 26, 2011 03:37AM UTC by comment:6
keywords: | → opera |
---|
Changed February 06, 2011 04:03PM UTC by comment:7
resolution: | → wontfix |
---|---|
status: | reopened → closed |
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.
You do realize there is no element that matches $("#id"), right?