- From: Aryeh Gregor <Simetrical+w3c@gmail.com>
- Date: Mon, 20 Sep 2010 14:11:48 -0400
On Sun, Sep 19, 2010 at 11:42 PM, Shiv Kumar <skumar at exposureroom.com> wrote: > At the same time, if I were to use Flash to upload the file, I don't need server side support to show progress and almost every website (that deals with large file uploads) today uses Flash to display upload progress to their users. This is only because the File API and related things aren't widely supported yet. Writing the upload progress in JavaScript is certainly going to be easier than writing it in Flash, when all browsers support the necessary already-specced JS features. Your feature would also work to replace Flash here (for a more limited subset of use-cases), but there's no reason to think it will be specced and implemented before all the stuff that's already being worked on. > I agree! I'd love to see browsers provide their own information in a more noticeable/useful fashion, but I still think surfacing the event and information allows web developers the option to display such information in a consistent manner (across browsers) without having to resort to handling the entire submission process using XMLHttpRequest. I don't think this would be necessary at all if browsers provided good UI, comparable to what they provide for downloads. Very few authors would feel the need to override good native UI -- how many try to override the native download UI? -- so requiring them to use XHR would be fine. Unfortunately, there's not much for us to do to get implementers to improve UI for large uploads, but I don't think speccing features to allow authors to more easily work around bad browser UI is a good strategy.
Received on Monday, 20 September 2010 11:11:48 UTC