This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The executeScript and executeAsyncScript algorithms make no mention of the script timeout global. They should timeout when this is reached, or run indefinitely if -1 (negative integer) is given. Section 13.1.1 mentions that "script timeout" can be used in this way, but the algorithms don't reflect this.
executeAsyncScript does reference timeout (step 1 in the algorithm in 10.3.1). Link to the timeout command needs to be updated though.