On 5/27/11 1:10 PM, Aryeh Gregor wrote:
Also, consider a third possibility: currently, the part of<script
async> that's captured by the first timing in Ian's/Boris' example
(whether it's parsing or compilation or whatever) blocks the main
thread in browsers, even though it's async. (Right?)
This is true at the moment in Gecko+Spidermonkey. I can't speak for others.
> Suppose that for whatever reason, it wouldn't be easy for
implementers to move this
work to a separate thread. (Boris/James/other implementers: is this
true?)
Nothing involving threads is "easy".
In Gecko's case, there is a definite desire to try to do this, but no
timeframe yet.
-Boris