On Thu, 24 Jan 2008, Mikko Rantalainen wrote:
Consider a form with a file input. User selects a huge file and hits
submit. Most UAs do not display nothing but an animated throbber until
the full submit is done and the download progress bar only starts to do
anything after the full submit
On Fri, 25 Jan 2008, Mikko Rantalainen wrote:
I'm not sure I see what value is added by somehow mandating this
feature. Evolving browsers will probably add this feature anyway
through competition.
If it will probably be added in the future anyway shouldn't the spec
recommend doing
On Jan 25, 2008 2:48 PM, Mikko Rantalainen [EMAIL PROTECTED] wrote:
It's wise to always trying to minimize the battery usage in a battery
operated device. However, if the device is already using wireless or
wired communication for transmitting the data set it cannot just do
nothing.
from my
timeless wrote:
On 1/24/08, Mikko Rantalainen [EMAIL PROTECTED] wrote:
I think that WF2 section 5.6
(http://www.whatwg.org/specs/web-forms/current-work/#methodAndEnctypes)
should be modified to say something along the lines
User agents with interactive user interfaces should inform the user
Consider a form with a file input. User selects a huge file and hits
submit. Most UAs do not display nothing but an animated throbber until
the full submit is done and the download progress bar only starts to do
anything after the full submit part is already done. An another example
could be a
On 1/24/08, Mikko Rantalainen [EMAIL PROTECTED] wrote:
Consider a form with a file input. User selects a huge file and hits
submit. Most UAs do not display nothing but an animated throbber until
the full submit is done and the download progress bar only starts to do
anything after the full
