On Sat, Sep 27, 2014 at 4:03 AM, Boris Zbarsky bzbar...@mit.edu wrote:
Now that JS is growing an event loop, what should happen to it in
navigated-away-from windows?
I still don't understand why JavaScript needs to have the loop itself
and can't just queue jobs for the Host to take care of.
What happens if someone runs
(function f() {setImmediate(f);})();
in a web page?
On Fri, Sep 26, 2014 at 10:03 PM, Boris Zbarsky bzbar...@mit.edu wrote:
Now that JS is growing an event loop, what should happen to it in
navigated-away-from windows?
To make this concrete:
1) Say I
What confusion is being caused? AFAICT, this change is causing only the
clarification of things that were/are confusing, such as Boris' question.
On Sat, Sep 27, 2014 at 2:20 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Sat, Sep 27, 2014 at 4:03 AM, Boris Zbarsky bzbar...@mit.edu wrote:
On Sat, Sep 27, 2014 at 3:52 PM, Mark S. Miller erig...@google.com wrote:
What happens if someone runs
(function f() {setImmediate(f);})();
in a web page?
As far as I can tell from
https://developer.mozilla.org/en-US/docs/Web/API/Window.setImmediate
that seems like a proprietary API from
On Sat, Sep 27, 2014 at 3:54 PM, Mark S. Miller erig...@google.com wrote:
What confusion is being caused? AFAICT, this change is causing only the
clarification of things that were/are confusing, such as Boris' question.
Well, I for one find it confusing that while HTML had a fairly worked
out
My intent was not to refer to a nonstd api. Instead, what happens with
(function f() {setTimeout(f, 0);})();
in a web page that is navigated away from?
On Sat, Sep 27, 2014 at 9:56 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Sat, Sep 27, 2014 at 3:52 PM, Mark S. Miller
On Sat, Sep 27, 2014 at 4:02 PM, Mark S. Miller erig...@google.com wrote:
My intent was not to refer to a nonstd api. Instead, what happens with
(function f() {setTimeout(f, 0);})();
in a web page that is navigated away from?
Now we get to why having two loops is bad...
Tasks in a
On 9/27/14, 9:52 AM, Mark S. Miller wrote:
What happens if someone runs
(function f() {setImmediate(f);})();
in a web page?
You get into
https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/setImmediate/Overview.html#processingmodel
step 5, which waits forever (modulo back/forward
On 9/27/14, 10:02 AM, Mark S. Miller wrote:
My intent was not to refer to a nonstd api. Instead, what happens with
(function f() {setTimeout(f, 0);})();
in a web page that is navigated away from?
See
https://html.spec.whatwg.org/multipage/webappapis.html#processing-model-9 step
1 and
Hi all, as a heads up we’re going to be doing an experiment in our tree to see
if we can kill off the function.arguments property entirely.
We’re super hopeful we can make it go away safely, and we’ll post a follow up
when we have some actual information about what happens.
If you’re
Huzzah!
IIRC, http://nba.com had some JS in it many years ago. While still in
development, V8 developers noticed it. I hope it's all gone.
/be
Oliver Hunt wrote:
Hi all, as a heads up we’re going to be doing an experiment in our
tree to see if we can kill off the function.arguments property
I took a look at Google's internal code index for reference to
Function.prototype.arguments and turned up many references to it
(PhpMyAdmin, some Intel benchmark, some internal code, etc). This is only
code used internally at Google (or was at one time) and not by any means
an index of the entire
I would like to see some way to preload everything, and be able to retrieve
them synchronously, something like:
System.loader.addNoAsync('...'); // throw if all imports aren't
available already
So that the script could be used during initial render. I understand that
this would mean that the
From: es-discuss [mailto:es-discuss-boun...@mozilla.org] On Behalf Of John Lenz
I would like to see some way to preload everything, and be able to retrieve
them synchronously, something like:
Sounds like a good custom loader extension that you could write.
I would like to get see stack traces standardized for ES7, to that end, I
would like to define a minimal set of behaviors that would need to be
defined:
* the stack property (a string)
* when the stack property is attached (at Error object creation or at throw)
* what happens when Error object
I would also like to see this standardized. Comments inline.
On Sep 27, 2014, at 10:15 PM, John Lenz concavel...@gmail.com wrote:
I would like to get see stack traces standardized for ES7, to that end, I
would like to define a minimal set of behaviors that would need to be defined:
*
16 matches
Mail list logo
