"Ian Hickson" <[EMAIL PROTECTED]>
On Sat, 27 Jan 2007, Jim Ley wrote:
"Ian Hickson" <[EMAIL PROTECTED]>
> >
> > MUST fire again at the end, even if that is zero bytes
>
> ...so that progress bars can be easily guarenteed to reach the 100%
> mark, which is important for usability.
Using onload is sensible for that, there is no point to require an extra
event which breaks backwards compatibility.
Could you elaborate on this backwards compatibility problem?
Sure, if authors go
.post() -> update UI to indicate something's started happening
event.onprogress -> indicate progress
event.onprogress (complete) -> update UI to indicate things have finished
Then user agents which do not get progress events never see the complete
status reflected in the UI, however if the UI uses onload to indicate things
have finished then the script is compatible with images and XHR in user
agents today.
Jim.
