- From: Jon Ferraiolo <jonf@adobe.com>
- Date: Wed, 1 Mar 2006 10:19:43 -0800
- To: "Maciej Stachowiak" <mjs@apple.com>
- Cc: <www-svg@w3c.org>
Hi Maciej, This is the official response to your email (http://lists.w3.org/Archives/Public/www-svg/2005Dec/0244.html). We agree with your suggestion and have changed the spec accordingly. On almost all issues having to do with scripting, we want SVG and HTML to have the same processing models. The old text was: ------------------ Script execution happens just after the load event occurs for the given script element. ------------------ The new text reads as follows: ------------------ Script execution happens just before the load event occurs for the given script element. ------------------ Thanks for your feedback. Please respond within two weeks if this response is not satisfactory. Jon Ferraiolo Member SVG WG ---------------------- From: Maciej Stachowiak <mjs@apple.com> Date: Wed, 28 Dec 2005 04:43:39 -0700 Message-Id: <D6990EFD-7A94-4207-ABAA-EC818141C649@apple.com> To: www-svg@w3c.org The SVGT 1.2 spec says: "Script execution happens just after the load event occurs for the given script element." This is opposite of the order in HTML, where the script executes before the corresponding element's load event occurs. It seems to me this reversed order will be confusing to content authors in a CDF enviornment. Also, I think the HTML behavior is more useful. When you dynamically add a <script> element, the time you really want an event to fire is after it has executed, so you know the functions defined in your external library are now available. An event right before the script executes is useless. I recommend reversing the ordering here. Regards, Maciej
Received on Wednesday, 1 March 2006 18:21:53 UTC