On 2/3/14 1:21 PM, Allen Wirfs-Brock wrote:
Speaking from the perspective of a ES language designer WTF is a "script setting object stack" and why have I never heard about it?
_Precisely_ my point about the world most spec writers find themselves in! ;)
More seriously, it's <http://www.whatwg.org/specs/web-apps/current-work/multipage/webappapis.html#script-settings-for-browsing-contexts> and <http://www.whatwg.org/specs/web-apps/current-work/multipage/webappapis.html#calling-scripts> with particular emphasis on <http://www.whatwg.org/specs/web-apps/current-work/multipage/webappapis.html#entry-settings-object> and <http://www.whatwg.org/specs/web-apps/current-work/multipage/webappapis.html#incumbent-settings-object>.
You probably haven't heard of it because it was only recently formalized. Previously this behavior was defined in terms of JS syntactic constructs attempting to explain the behavior of APIs like the location setter and postMessage, but of course when the event loop directly invokes functions there is no JS syntactic construct on the stack. Hence the redefinition in terms of concepts that make sense in the event loop case.
You also probably haven't heard of it because it wasn't relevant to ES until an event loop was introduced to the language.
That said, if you're following public-script-coord you probably saw at least <http://lists.w3.org/Archives/Public/public-script-coord/2014JanMar/0080.html>... Unfortunately a lot of the other discussion on the matter happened directly in bugzilla bugs, and wasn't mirrored to public-script-coord, for which I apologize. :(
-Boris _______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
