- From: Cameron McCormack <cam@mcc.id.au>
- Date: Sat, 6 Sep 2008 14:49:18 +1000
- To: public-svg-wg@w3.org
Cameron McCormack: > > Execution of a given 'script' element occurs at most once. There is a > > conceptual flag associated with each 'script' element (referred to > > here as the "already processed" flag) that enforces this behavior. > > When 'script' elements are executed depends on how they came to be in > > the document. Doug Schepers: > The phrase "how they came to be in the document" sounds chatty to me, > but I don't have a better alternative. Maybe just: When 'script' elements are executed depends on whether they were inserted into the document by the parser. > > A 'script' element is processed as follows: > > > > 1. If the 'script' element’s "already processed" flag is true or if > > the element is not in the document tree, then no action is > > performed and these steps are ended. > > 2. If the 'script' element references external script content (that > > is, it has an 'xlink:href' attribute specified), then processing > > blocks until that external script content referenced by the > > current value of 'xlink:href' has been fetched or is determined > > to be an _invalid IRI reference_. > > This wording is muddled. Maybe: > > [[ 2. If the 'script' element references external script content > (that is, it has an 'xlink:href' attribute specified), then > further processing is dependent upon the externally referenced > script content, and will not proceed until that the resource > has been fetched or is determined to be an _invalid IRI > reference_. > ]] That sounds OK. I might split that step up into two so I can explicitly state that the @xlink:href value at that time is used to fetch the script. > > 3. The 'script' element’s "already processed" flag > > The sentence seems to cut off here. Maybe: > > [[ > 3. The 'script' element’s conceptual "already processed" flag is > set to true. > ]] Yeah. -- Cameron McCormack ≝ http://mcc.id.au/
Received on Saturday, 6 September 2008 04:49:56 UTC