W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2008

Re: New Progress draft (1.25)...

From: Garrett Smith <dhtmlkitchen@gmail.com>
Date: Fri, 31 Oct 2008 22:10:53 -0700
Message-ID: <c9e12660810312210q92e9a80l1709b814a6ecbda1@mail.gmail.com>
To: "Charles McCathieNevile" <chaals@opera.com>
Cc: "Jonas Sicking" <jonas@sicking.cc>, "Web Applications Working Group WG" <public-webapps@w3.org>

On Fri, Oct 31, 2008 at 8:05 AM, Charles McCathieNevile
<chaals@opera.com> wrote:
> On Sat, 25 Oct 2008 09:08:56 +0200, Jonas Sicking <jonas@sicking.cc> wrote:
>> Garrett Smith wrote:
>>> On Fri, Oct 24, 2008 at 5:51 AM, Jonas Sicking <jonas@sicking.cc> wrote:
>>>> Garrett Smith wrote:
>>>> I agree. Not sure if that is what you want to do before or after getting
>>>> the
>>>> load/error/abort event though?
>>>> I should mention that I'm not particularly married to having things one
>>>> way
>>>> or another. But I think we should have reasons for choosing.
>>>  Agree. Anyone who has another use case for loadend, please post up.
>> I was also wondering why in your use case it made sense to fire loadend
>> before load/error/abort? I.e. what would you be doing in those events such
>> that you want the progress bar hidden at that point.
>> Though I do agree that it makes sense to say "i'm done" before "here's the
>> data" (or "it failed").
> It seems to me that the order is not that significant - either you are
> trapping the specific end cases ("I'm done" / "It failed"), or you don't
> really care about them so you use the convenience loadend event, e.g. to
> remove your progress bar.

 "I'm done" is the loadend event and "it failed" is the error message
from abort|error.

> Given that whichever comes first will fire whichever comes second, I think
> the symmetry is as good an argument as any for ordering, so I am inclined to
> leave what we have now. Garrett, do you think that is really a wrong
> decision (and if so do others agree we should change it back)?

I've coded to requirements that specify the busy icon being hidden and
a message being shown. In those cases, I wanted a 'done' event.

It would be helpful to have input from HCI and U/X experts. What are
the majority of cases, is it "notify user of progress complete and
display a message," or "display a message, then notify the user of
progress complete."

Having loadend fire last is still better than not having it at all. In
the cases where order is significant, then it's still possible to code
around it.

> Cheers
> Chaals
> --
Received on Saturday, 1 November 2008 05:11:30 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:12 UTC