Ok, I sense resistance to putting it in .name. What about .path, undefined in most cases except where there is an upload including files from multiple directories, in which case .path contains the path less any path components common to all 3 (sorry, it's early morning and I can't write well before having coffee).<div>
<br></div><div>e.g. </div><div><br></div><div>input.files[0].name="1.jpg"</div><div>input.files[0].path="a/b"<br><div>input.files[1].name="2.jpg"</div><div>input.files[1].path="a/b"<br>
</div></div><div><div>input.files[2].name="3.jpg"</div><div>input.files[2].path="a/c"<br></div><div><br></div><div>(Need to figure out the exact wording, as "a" is common to all 3 but if you're uploading the entire directory "a", it may make sense to include that in the path -- but I don't feel quite as strongly about that -- subfolders are certainly more important IMO.)</div>
<div><br></div><div class="gmail_quote">2009/12/11 Jeremy Orlow <span dir="ltr"><<a href="mailto:jorlow@chromium.org">jorlow@chromium.org</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5">On Fri, Dec 11, 2009 at 2:30 AM, Markus Ernst <span dir="ltr"><<a href="mailto:derernst@gmx.ch" target="_blank">derernst@gmx.ch</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Jeremy Orlow schrieb:<div><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Fri, Dec 11, 2009 at 12:47 AM, Anne van Kesteren <<a href="mailto:annevk@opera.com" target="_blank">annevk@opera.com</a> <br>
</blockquote>
<br>
</div><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
And I mean that if it is important to application developers we<br>
should make it available as a feature and not endorse some plug-in<br>
dependency.<br>
<br>
<br>
I (and I think most of us) strongly agree. That's the whole point of standardization. :-)<br>
<br>
Personally, I don't think the case Markus pointed out is at all a show stopper. In the case of images, the server could easily recognize and reconcile duplicates (by hashing them and looking for duplicate hashes or something). If the image has been tweaked some in the mean time, the EXIF data can help. And so on....this seems like the type of thing clever developers can work around.<br>
<br>
But regardless.....I don't think you could argue that having _some_ path information is worse than _none_, right?<br>
<br>
I also agree with Jonas that if some path information is added, it might be better to create a new property (other than .name) for it.<br>
<br>
And, with or without that extra property, I think what Ian's suggesting would be useful to users.<br>
</blockquote>
<br></div>
Yes I see Anne's and your points. Anyway I don't see yet how to get _useful_ path information, as the same file can be posted as /a/b/1.jpg, and at the next occasion as 1.jpg or /b/1.jpg, just based on where in the upload dialog you did make the start point.<br>
<br>
Relying on information contained in the uploaded file does not seem to make sense to me, as you might want to upload a new file with the same name in order to replace the old one.<br>
</blockquote></div><br></div></div><div>The information in the path could be seen as a hint that may or may not be provided. I feel like it'd be difficult security wise to guarantee that the hint will be there and/or consistent from upload to upload. But, once again, some hint is better than none, right? If you as a web developer don't think it's useful, you can ignore it, right?</div>
</blockquote></div><br></div>