W3C home > Mailing lists > Public > www-svg@w3.org > November 2004

SVG 1.2 Comment: Progressive rendering

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Tue, 23 Nov 2004 13:19:42 -0600
Message-ID: <41A38D4E.3050904@mit.edu>
To: www-svg@w3.org

If a node's child references a resource (eg a paint server) that either has not 
been parsed yet (no startElement for it) or is in the "unresolved" state, what 
state is the node in?  Note that the node itself may have been fully parsed by 
this point, as far as I can see.  Based on the examples, it sounds like it would 
be in the "unresolved" state, but this isn't clear from the prose.

The requirement that the rendering be updated following each startElement or 
endElement SAX event is rather onerous from a performance standpoint.  It forces 
document loading to be O(N^2) in the content size, since UAs are not allowed to 
use any heuristics to slow down the update rate as the size of the DOM grows.

The prose makes it sounds like referencing an image that returns an HTTP 404 
response would put the relevant image node in the error state, which would stop 
rendering of the document.  Is this intended?  If so, why?  If not, the prose 
needs to be fixed accordingly.

"no proceed" in item 4 of the 'Forward reference on use with eRR="true"' example 
should be "not proceed".

The 'Forward reference with use to an element under a container with eRR="true"' 
example, item 3, the antecedent of "it" is wrong -- it can't possibly mean the 
"#myRect" reference.

Received on Tuesday, 23 November 2004 19:24:53 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 09:47:01 UTC