Dave Watts wrote: > Well, strictly speaking, this isn't a JavaScript thing as much as an HTML > DOM thing. It's up to the DOM to specify what's what in the > browser. In the case of SELECT fields:
Right... and actually, as I suggested in a subsequent paragraph, the value property may have been added as part of the browsers' support for the DOM. I just found a reference to the value property in the DOM Level 1 spec: http://www.w3.org/TR/2000/WD-DOM-Level-1-20000929/level-one-html.html#ID-942 82980 So it would seem that this is now per the standard. I'd still like to know (I really should just test this myself and stop asking other to do it 8^>) how the ability to write to this property is implemented. > If the above URL is correct, it's writeable. Again, though, if I want to > change an option's value, I just delete and recreate the option using the > Option constructor. That's how I've always done it too. Or just modify the option's value directly. But this seems to suggest a new, more direct way of doing it. Of course, backwards compatibility could be an issue. -- Mosh Teitelbaum evoch, LLC Tel: (301) 942-5378 Fax: (301) 933-3651 Email: [EMAIL PROTECTED] WWW: http://www.evoch.com/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:256169 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
