Bug Tracker

#6662 closed bug (invalid)

Opened June 12, 2010 12:43AM UTC

Closed October 06, 2010 12:22AM UTC

Selector doesn't seem to work in Chrome

Reported by: ross Owned by:
Priority: undecided Milestone: 1.4.3
Component: selector Version: 1.4.2
Keywords: Cc: select, option, chrome
Blocked by: Blocking:
Description

This test case explains the problem: http://jsfiddle.net/n7GjN/

Essentially the second <option> should be changed.

This occurs in Google Chrome 5.0.375.70 (Official Build 48679) beta. (WebKit 533.4; V8 2.1.10.13).

In case the test case goes down:

<select name="label" id="label"> 
    <option value="1" label="testLabel">testLabel</option> 
    <option value="newLabel" label="New Label">New Label</option> 
</select>

$(function(){
    $("#label option[value=newLabel]").html("Other Label");
});​
Attachments (0)
Change History (2)

Changed June 12, 2010 01:10AM UTC by dmethvin comment:1

cc: → select, option, chrome
description: This test case explains the problem: http://jsfiddle.net/n7GjN/ \ \ Essentially the second <option> should be changed. \ \ This occurs in Google Chrome 5.0.375.70 (Official Build 48679) beta. (WebKit 533.4; V8 2.1.10.13). \ \ In case the test case goes down: \ \ <select name="label" id="label"> \ <option value="1" label="testLabel">testLabel</option> \ <option value="newLabel" label="New Label">New Label</option> \ </select> \ \ $(function(){ \ $("#label option[value=newLabel]").html("Other Label"); \ });​ → This test case explains the problem: http://jsfiddle.net/n7GjN/ \ \ Essentially the second <option> should be changed. \ \ This occurs in Google Chrome 5.0.375.70 (Official Build 48679) beta. (WebKit 533.4; V8 2.1.10.13). \ \ In case the test case goes down: \ {{{ \ <select name="label" id="label"> \ <option value="1" label="testLabel">testLabel</option> \ <option value="newLabel" label="New Label">New Label</option> \ </select> \ \ $(function(){ \ $("#label option[value=newLabel]").html("Other Label"); \ });​ \ }}}

Changed October 06, 2010 12:22AM UTC by addyosmani comment:2

priority: → undecided
resolution: → invalid
status: new → closed

Invalid bug. I think what happened here is that you may have misconfigured JSFiddle. Setting the first option to 'onLoad' or 'onDomReady' you will see that in both Chrome and any other webkit browsers that your test case is working fine.

Please see here: http://jsfiddle.net/n7GjN/4/