Bug with CSS Selector E[foo] on Option elements

[djvirgen]

HTML:

<select id="theSelect">

<option>Select a color</option> <option value="blue">Blue</option> <option value="red">Red</option>

</select>

Given the above HTML, the following CSS selector incorrectly returns all 3 options:

$('#theSelect option[value]').length; 3

While the first option would submit a value when the form is submitted, it technically does not have a value attribute.

According to the W3C spec [1], the selector E[foo] should return E elements that contain a foo attribute.

​http://www.w3.org/TR/css3-selectors/#selectors

[flesler]

Can you try with ​this version of jQuery ?

[djvirgen]

I have just tested it with the nightly build, and it is still reporting an incorrect number of matched elements.

Test code:

console.log('Number of options with a "value" attribute: ' + $('option[value]').length); incorrectly reports 3

HTML:

<select name="test">

<option>No Value Attribute</option> <option value="foo">Foo</option> <option value="bar">Bar</option>

</select>

[balazs.endresz]

var el = $('<select><option>text</option></select>').find('option')[0];

el.value;                 //returns "text"

el.getAttribute('value'); //returns: null

In both 1.2.6 and 1.3b2 first the element's property is checked, which returns "text" instead of undefined even if there isn't a value attribute, so there won't be any further checks with getAttribute. Otherwise using .val() would return "text" on the element but you wouldn't be able to select it with the attribute filter.

[dmethvin]

​http://jsfiddle.net/dmethvin/BQQQx/

As balazs.endresz said, this is expected behavior. If jQuery didn't match against the value *property* then the selector would only match the initial value attribute.