- From: Andrew Sledd <Andrew.Sledd@ikivo.com>
- Date: Wed, 12 Jul 2006 16:49:29 +0200
- To: "Boris Zbarsky" <bzbarsky@mit.edu>
- Cc: <www-svg@w3.org>
Dear Boris, This is the response to your Last Call comment from email (http://lists.w3.org/Archives/Public/www-svg/2006Jan/0446.html), which is copied at the bottom. The load event will not trigger due to the methods you specify as they do not add the element to the DOM tree. However, methods like appendNode() which do add the node to the tree must a load event on the element which is added to the tree. In reviewing your comment, the WG agrees that the description of the load event need be improved to better clarify. The following is the new text for the description of the load event. "The event is triggered at the point at which the user agent finishes loading the element and any dependent resources (such as images, style sheets, or scripts). In the case the element references a script, the event will be raised only after an attempt to interpret the script has been made. Dependent resources that fail to load will not prevent this event from firing if the element that referenced them is still accessible via the DOM unless they are designated as. The event is independent of the means by which the element was added to DOM tree." Thanks for you feedback, please let us know shortly if you are unsatisfied with this answer. Andy Sledd on behalf of the SVG WG. ---------------------------------------------------------------------- Dear SVG Working Group, The description of the load event [1] is completely in terms of parsing. Does this mean that load events do not fire on nodes created via createElementNS(), cloneNode(), etc? I would much appreciate a clarification of this point, -Boris _______________________________________ Andrew Sledd Ikivo AB
Received on Wednesday, 12 July 2006 14:45:05 UTC