ISSUE-112 - Public View
Should progress run a UI or rely on other stuff too?
- State:
- CLOSED
- Product:
- Progress Event
- Raised by:
- Charles Mccathienevile
- Opened on:
- 2007-02-10
- Description:
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?
- Related emails:
- ISSUE-112: Should progress run a UI or rely on other stuff too? (from dean+cgi@w3.org on 2007-02-10)
- Re: ISSUE-112: Should progress run a UI or rely on other stuff too? (from ian@hixie.ch on 2007-02-10)
- Re: ISSUE-112: Should progress run a UI or rely on other stuff too? (from chaals@opera.com on 2007-02-10)
- Re: ISSUE-112: Should progress run a UI or rely on other stuff too? (from ian@hixie.ch on 2007-02-10)
- Re: ISSUE-112: Should progress run a UI or rely on other stuff too? (from chaals@opera.com on 2007-02-10)
- Re: ISSUE-112: Should progress run a UI or rely on other stuff too? (from mjs@apple.com on 2007-02-10)
- Re: ISSUE-112: Should progress run a UI or rely on other stuff too? (from Ellen.Siegel@Sun.COM on 2007-02-13)
Note: Some of these links may be accessible only to W3C Members.
Related notes:
2007-04-24: There should be enough to run a UI for progress now.