W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > January 2011

[Bug 11796] HTML5 SUGGESTIONS ------------------------------ This file contains suggestions of tags / features that can be added to HTML5. I sincerely hope that these features are added especially the file tag (<file></file>) which is the last I would write on. I hav

From: <bugzilla@jessica.w3.org>
Date: Wed, 19 Jan 2011 01:21:23 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1PfMjj-0003Ny-LG@jessica.w3.org>

Tab Atkins Jr. <jackalmage@gmail.com> changed:

           What    |Removed                     |Added
                 CC|                            |jackalmage@gmail.com

--- Comment #1 from Tab Atkins Jr. <jackalmage@gmail.com> 2011-01-19 01:21:23 UTC ---
#1 and #2 are already handled via the @accept attribute on <input type=file>. 
You declare what type of file you'd like to accept, and the browser can then
ask the user if they wish to provide a file, or use their mic/camera to create
one on the fly.

#3 is already handled by XHR, and has been for a while.

For #4, <object> is already designed to accept arbitrary files, with more
specialized elements (<img>, <audio>, <video>) accepting particular types of
files for better handling.

Your assertion that <img src=foo.php> may not work in some browsers is false -
no browser rejects images based on file extension, nor do any of them try to
automatically save images referenced through <img>.  If they did, they'd have
massive compatibility problems, precisely because so many images are generated
by php scripts in that way.  The correct way to load an image, dynamically
generated or not, is to use <img>.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 19 January 2011 01:21:25 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:04 UTC