- From: Mike West <notifications@github.com>
- Date: Fri, 16 Oct 2015 00:45:21 -0700
- To: heycam/webidl <webidl@noreply.github.com>
Received on Friday, 16 October 2015 07:45:55 UTC
Thanks, @bzbarsky. This is exactly what I needed. :) I've uploaded a second pass at the patch, and I hope you'll indulge a few more newbie questions. 1. I think it makes sense to perform this check at more or less the same time we're performing "a security check", and to use the incumbent settings object, as I think we ought to care about the context that's using a tool to do some work, rather than the context from which the tool came. Does that make sense? (As an aside: WebIDL refers to "incumbent script" and "stack of incumbent scripts". Those ought to be renamed to "[stack of] incumbent settings object", right? I can throw you a patch if that's accurate.) 2. Should I leave the descriptive text in the `[SecureContext]` section? Or is the normative description in the operations section good enough? --- Reply to this email directly or view it on GitHub: https://github.com/heycam/webidl/pull/65#issuecomment-148639968
Received on Friday, 16 October 2015 07:45:55 UTC