This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 6529 - value DOM attribute for input element in File Upload state
Summary: value DOM attribute for input element in File Upload state
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P4 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Keywords: NoReply
Depends on:
Reported: 2009-02-04 11:56 UTC by Anne
Modified: 2010-10-04 14:29 UTC (History)
4 users (show)

See Also:


Description Anne 2009-02-04 11:56:16 UTC
When the input element is in the File Upload state the value DOM attribute does apply (the specification says it does not). The DOM attribute does nothing on setting and on getting returns the filename.

In case of multiple selected files Opera currently returns just the filename of the first. That can be changed, I do not really care.
Comment 1 Anne 2009-02-04 13:25:08 UTC
FWIW, I forgot to mention we changed our policy in Opera 10 for compatibility reasons with deployed scripts. We return a fake path so scripts searching for something path-like will not break. From then on we will return:


It has been suggested to us that avoiding the underscore might be good, making it


We would be ok with that.
Comment 2 Anne 2009-02-13 09:51:46 UTC
Please make the C uppercase. At least two implementations will start doing that and although lowercase might be slightly neater and consistent it's hardly worth the trouble.
Comment 3 Maciej Stachowiak 2010-03-14 13:16:46 UTC
This bug predates the HTML Working Group Decision Policy.

If you are satisfied with the resolution of this bug, please change the state of this bug to CLOSED. If
you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:

This bug is now being moved to VERIFIED. Please respond within two weeks. If this bug is not closed, reopened or escalated within two weeks, it may be marked as NoReply and will no longer be considered a pending comment.