- From: Boris Zbarsky <bzbarsky@MIT.EDU>
- Date: Tue, 23 Nov 2004 13:03:00 -0600
- To: www-svg@w3.org
7.1: Perhaps I'm missing something, but I see nothing that prevents an SVG element referencing resources by ID that come later in the document (if there is such a restriction, I would love to be pointed to it). So while the use case described (with <page>) still behaves somewhat reasonably, due to the constraints on placing content after the pageSet and the constraints on referencing resources across pages, in general the onStart value of timelineBegin would lead to problems (that is, under-defined behavior). I think that some thought should be given to defining this behavior for the less-obvious cases (for example, setting <page> elements to onStart). It's also not clear to me what it means for the timeline to start. Is a UA allowed to not start rendering the document until it has been fully parsed? If it does so, how does that behavior interact with timelines? If this behavior is fully specified elsewhere (the SMIL specification?) please link to the appropriate section of the relevant specification. 7.2: What happens if streamedContents is set to "discard" exactly? Are the discarded <page>s removed from the DOM? What happens if a script in one <page> (eg off a click event handler) attempts to access objects in another <page>? Is content allowed to do this, in general? If it does, will it just see an inconsistent DOM depending on what, if anything, the UA has discarded? This all needs to be clearly defined. -Boris
Received on Tuesday, 23 November 2004 19:05:45 UTC