This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
In step 8 of <http://www.whatwg.org/specs/web-apps/current-work/#running-a-script>, the spec adds external scripts to the <http://www.whatwg.org/specs/web-apps/current-work/#set-of-scripts-that-will-execute-as-soon-as-possible>. When the fetching algorithm is complete, the spec invokes <http://www.whatwg.org/specs/web-apps/current-work/#executing-a-script-block>. However, that sequence of steps does not save the current insertion point (among other things), which seems very unlikely to be compatible with the web. In implementing the above requirement in WebKit, we assumed the spec meant to invoke <http://www.whatwg.org/specs/web-apps/current-work/#scriptTagParserResumes>, which saves the current insertion point (and does other things that would make sense at that point). Should we change the spec to say this explicitly?
The spec is unambiguous and intentional in its current requirements. The insertion point is only saved when the script is inserted by the parser. Do you have a specific example of something incompatible with the exact requirements in the spec?
Ah, I see. I misunderstood how "ready to be parser-executed" worked. Thanks.