ISSUE-112: Should progress run a UI or rely on other stuff too? from Web APIs Issue Tracker on 2007-02-10 (public-webapi@w3.org from February 2007)

From: Web APIs Issue Tracker <dean+cgi@w3.org>
Date: Sat, 10 Feb 2007 06:23:01 +0000 (UTC)
To: public-webapi@w3.org
Message-Id: <20070210062301.4C83CDAF47@w3c4-bis.w3.org>

ISSUE-112: Should progress run a UI or rely on other stuff too?

http://www.w3.org/2005/06/tracker/webapi/issues/112

Raised by: Charles Mccathienevile
On product: Progress Event

Maciej has outlined some use cases based on the progress events being 
sufficient to run an entire UI.

There is an existing thread at http://www.w3.org/mid/8FDB961A-31D4-40CB-
BFC9-0CE780CD20AB@apple.com and following.

Is it worth adding to progress events to support this use case, or 
should it stay as small as possible?

Received on Saturday, 10 February 2007 06:23:06 UTC