Re: LC Comment - Script & Progressive Rendering / Multiple Pages

"Boris Zbarsky" <bzbarsky@MIT.EDU>
> Every <html:script> node has a flag to indicate whether the associated 
> script has been executed.  For any given script node, the script is 
> executed only if the flag is false; once the script has been executed, the 
> flag is set to true.

How is defer handled?  and if you're inserting 2 script elements and some 
HTML at the same time, what's the order of execution, and what happens with:

fred=alert
addChild(document.body,'<script 
type="text/javascript">fred=confirm</script>');
fred()

(where addChild is an appropriate script to insert that HTML into the 
current document)

does the defer attribute make a difference?

Whilst your prose is a good starting point, I don't think it actually 
defines it well enough for a specification.

> Note that the HTML working group has been ignoring errata suggestions to 
> HTML 4.01 for years now, so I wish you luck with getting them to specify 
> it.

Well I've got a process issue about that, a timelimit on the current open 
ended obligation to track issues in specifications of course that equally 
needs them to address that issue first, but I'm hopeful one day it will 
happen.  There's a similar problem with every working group of course, 
there's no CSS2 errata and no SVG 1.1 errata, I'm still hopeful of WG's 
doing things properly, simply not raising issues is not a sensible approach.

>> How did you manage to do this without raising it as an issue in those 
>> technologies?
>
> By carefully reverse-engineering the relevant de-facto standard ("do what 
> IE does").

but that isn't what IE does.   IE requires the defer attribute to execute 
scripts inserted after the document has loaded (or at least it did a few of 
years back, I've not checked recently.)

Cheers,

Jim.

Received on Wednesday, 1 December 2004 17:52:20 UTC