26836 2014-09-17 16:10:36 +0000 Extend script settings objects to be environment settings objects for use by fetch et al 2014-10-10 23:43:24 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED P3 normal Unsorted 24080 26603 1 ian ian adrianba annevk ap bzbarsky eoconnor hober0 ian mike w3c zcorpan contributor oldest_to_newest 111695 0 ian 2014-09-17 16:10:36 +0000 112412 1 ian 2014-09-29 20:27:52 +0000 Just a quick heads-up: to help the Fetch spec, I'm going to be extending the existing Script Setting Object concept to be usable even when scripts are not running. This won't affect the Stack of Settings Objects, but it will mean that Settings Objects might be passed around when no script is running. I plan to rename the concept to Environment Settings Objects accordingly. 112416 2 annevk 2014-09-29 20:46:24 +0000 Currently, a bunch of specifications have checks along the lines of "if the JavaScript global environment is a document environment, ..." It would be good if these kind of checks could be rewritten using this new construct, if we don't want to tie the platform to JavaScript at a conceptual level. (No strong feelings about that either way personally.) 112432 3 ian 2014-09-29 23:43:01 +0000 Those can be trivially patched to just check the "specified global object" of the settings object, or some such, but we could also add an explicit "environment kind" which has a 1:1 mapping to that and makes it clearer. 112976 4 ian 2014-10-10 23:43:24 +0000 I ended up not adding the environment kind because I couldn't come up with terms that didn't suck or clash with something already. So just refer to the specified global object (or, the global object specified by the environment settings object, or whatever) when testing its type. Anyway, we now have environment settings objects. You can get them from the global and pass them around, and you'll have everything you need including a reference to the event loop which you likely need for various reasons. I recommend using this widely instead of the "client" concept, "realm" concept, or the global itself, since we can more trivially hang things from it if necessary.