Given the HTML:

<select id="mySelect">
    <option value="1">test1</option>
    <option value="2">test2</option>
    <option value="3">test3</option>
</select>

and the javascript:

var e = document.getElementById('mySelect');

To get the value of the select I can use e.value and e.options[e.selectedIndex].value.

I am aware that e.options[e.selectedIndex].value will give me the selected value (1,2 or 3) and e.options[e.selectedIndex].text would give me test1, test2, test3 depending on which is selected.

Is it ok to use just e.value? was this a problem in old browsers?
which is more correct: e.value vs e.options[e.selectedIndex].value?

jsFiddle

Given the HTML:

<select id="mySelect">
    <option value="1">test1</option>
    <option value="2">test2</option>
    <option value="3">test3</option>
</select>

and the javascript:

var e = document.getElementById('mySelect');

To get the value of the select I can use e.value and e.options[e.selectedIndex].value.

I am aware that e.options[e.selectedIndex].value will give me the selected value (1,2 or 3) and e.options[e.selectedIndex].text would give me test1, test2, test3 depending on which is selected.

Is it ok to use just e.value? was this a problem in old browsers?
which is more correct: e.value vs e.options[e.selectedIndex].value?

jsFiddle

• javascript
• html
• html-select
• selectedvalue
• selectedindex

• I can't see why not use the standard e.value. There're no browsers patibility issues documented: developer.mozilla/en-US/docs/Web/HTML/Element/select – emerson.marini Commented Aug 11, 2014 at 18:31
• 1 @Rikard As you have suggested, it was an issue in very old browsers. You could not use .value on the select itself, you had to get the selected option and take the value of that. – James Montagne Commented Aug 11, 2014 at 18:38
• 1 @Rikard A quick google found that it didn't work at all in Netscape 4 and that IE6&7 had some oddities, though it wasn't fully broken. – James Montagne Commented Aug 11, 2014 at 18:41
• 1 @RickHitchcock: you need to learn about the difference between DOM properties and HTML attributes. Select elements do indeed have a .value – Bergi Commented Aug 11, 2014 at 19:15
• 3 @Bergi, I stand corrected! Nice to know select.value is safe to use. But is that new as of HTML5? All the discussion here says we should use options ... selectedIndex: stackoverflow./questions/1085801/… – Rick Hitchcock Commented Aug 11, 2014 at 19:28

3 Answers 3

The HTMLSelectElement interface includes the value attribute at least since Document Object Model (DOM) Level 1 Specification, from 1998.

However, like it is explained in this w3c mailing list, the problem was that HTML4.01 spec was vague:

It's true that HTML4.01 doesn't explicitly specify a value attribute for SELECT, but it does seem to be implied:

• 'Menu' is a control type. (HTML4.01 17.2.1)

• "Each control has both an initial value and a current value, both of which are character strings" (HTML4.01 17.2)

• And SELECT may have an onchange attribute which implies a value. (HTML4.01 17.6)

But there's no mention of what the value represents, nor of what the initial or default values might be.

However, checking in IE5 and Mozilla, the value of SELECT does indeed return a string corresponding to the value of the currently selected OPTION.

(...) Probably wouldn't be a problem if HTML4.01 had been more explicit.

This was fixed in following definitions.

You can see it defined here:

• HTMLSelectElement's value in DOM Level 1, W3C Remendation, 01 October 1998

  The current form control value.

• HTMLSelectElement's value in DOM Level 2, W3C Remendation, 09 January 2003

  The current form control value (i.e. the value of the currently selected option), if multiple options are selected this is the value of the first selected option.

• HTMLSelectElement's value in HTML5, W3C Candidate Remendation

  The value IDL attribute, on getting, must return the value of the first option element in the list of options in tree order that has its selectedness set to true, if any. If there isn't one, then it must return the empty string.

So I think it's safe to use.

Some old (~2005) threads from the p.lang.javascript newsgroup, as well as their FAQ [1], mention that .value access was not supported in Netscape Navigator 4 (i.e. pre-2000), and some other mobile and desktop browsers that were considered "old" even at that time.

Conclusion (backed by @Oriol's DOM spec excerpts): It's totally safe to use today.

document.getElementById('submit').onclick = function() {
    var e = document.getElementById("pets");
    var text = e.options[e.selectedIndex].text;
    document.getElementById("container").innerHTML = 'The selected text is ' + text;
}