I already explained that in my previous email. Parsing and compilation on a
background thread removes some of the problem but not all of it. Ultimately,
even if the script is just a function waiting to be called, the browser still
executes it in a blocking fashion after parsing and compilation.
On Tue, 24 May 2011, Stewart Brodie wrote:
The section on the structured cloning algorithm has a Note that says
Property descriptors, setters, getters, and analogous features are
not copied in this process.
Is this note part of the normative definition of the algorithm, or just
a
On Tue, May 24, 2011 at 12:34 PM, Nicholas Zakas nza...@yahoo-inc.com wrote:
Moving parsing and compilation to a background thread solves part of the
problem, the problem where doing so freezes the UI currently. It doesn't
solve what I consider to be the important part of the problem, and
On Wed, May 25, 2011 at 8:05 PM, Aryeh Gregor simetrical+...@gmail.com wrote:
There's a big conceptual difference between parsing the script and
executing it. We need to be careful not to conflate the two, even if
browsers don't *currently* separate them.
I just discussed this on IRC with
