W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2013

Re: File Save As

From: Bronislav Klučka <Bronislav.Klucka@bauglir.com>
Date: Sun, 06 Jan 2013 10:39:11 +0100
Message-ID: <50E9463F.3050103@bauglir.com>
To: public-webapps@w3.org

On 6.1.2013 0:51, Jonas Sicking wrote:
> 3. What should the UI in the browser look like in order to communicate
> to the user that this is different from the <input type=file>
> file-picker which only allows reading.
>

Well generally OS do have dialogs for Open and Save As, users use those 
allhe time in applications (browser included, when downloading content) 
so what is the problem here?

Or do you mean UI within the page? The actual input rendered on the 
page? First of all, do we need one? One thing is to have input for 
reading file, as a part of form, file (file content) as one property of 
a form, this have been working for web rot 2 decades, desktop 
application works the same way. But why special input here? Why this 
cannot be JS API only trigger by click/whatever?

BTW current input file is an exaple of poor design... the thole thing is 
unstylable, if your application has certain look and feel, this thing 
sticks up like sore thumb and you probably end up with stylable regular 
button and crete fileinput on demand with JS a calling .click() in JS as 
well.

Brona
Received on Sunday, 6 January 2013 09:39:38 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:57 GMT