W3C home > Mailing lists > Public > www-svg@w3.org > May 2003

SVG 1.2 12.1.1 The Progress Event

From: Jim Ley <jim@jibbering.com>
Date: Fri, 9 May 2003 08:19:45 -0000
To: www-svg@w3.org
Message-ID: <b9g2s0$er0$6@main.gmane.org>

What would happen in the situation where the referenced URI was a data: URI
or a backwards local reference to a def'd element previously?

The attribute must be fully loaded (but not necessarily ready to be
rendered) at the same time as the event handler is defined (if using the
onPreLoad="..." syntax) so the MUST requirement to dispatch the event before
loading starts seems impossible to provide.

I'd like to see the total attribute not be ignored for a postload event,
since knowing the size of the resource should be available to the UA by this
time, and it seems reasonable to expose it to the user, especially as there
may have been no loadprogress type events fired for a resource to get the
size.

In the situation where the content is gzip-compressed, should the inflated
or gzipped size be returned?

If the server lies about the size of the resource, what should be returned
(consider a situation where the server claims a resource is 5000 bytes but
in reality it's 10000 bytes, then loaded would get above total.) should
total change in this situation to -1 after it's obvious the initial size
reported by the server was wrong?

The document talks about a "progress property"

"the progress property on an 'intermediate progress' event is strictly
greater than zero and strictly smaller than one."

but I don't see it in the IDL definition, assuming it does exist, then my
example above would cause problems with the strict requirement that it does
not get outside the 0-1 range.

Also I believe that a complimentary, onError or something similar needs to
be provided for the situation where for whatever the reason the referenced
resource is not returned, (since people will often use the events for hiding
content until all referenced resources are available, the failure of any 1
resource to be not available will often result in all content not being
shown.

Also what should happen if the returned resource is a 404 or other non-200
status code, should the document that accompanies the 404 be displayed and
made available with progressLoad events (after all it may well be a document
of a type renderable by the UA) or should it be a failure and therefore fire
my proposed ERROR event.


Jim.
Received on Friday, 9 May 2003 08:40:50 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:25 GMT