[] (0) Make scripts not run in non-active documents; add issue regard…

…ing this for events.

git-svn-id: http://svn.whatwg.org/webapps@848 340c8d12-0b0e-0410-8428-c7bf67bfef74

index

@@ -18958,11 +18958,13 @@ notes on what would need to be defined for dashed lines:
 
   <p>If the load was successful, then first the user agent must <a
    href="#firing4">fire a <code title=event-load>load</code> event</a> at the
-   element, and then, if <a href="#scripting2">scripting is enabled</a> and
+   element, and then, if <a href="#scripting2">scripting is enabled</a>, and
    the <code>Document</code> does not have <code
    title=dom-document-designMode><a href="#designMode">designMode</a></code>
-   enabled, the user agent must run the script according to the semantics of
-   the relevant scripting language defines.
+   enabled, and the <code>Document</code> is the <a href="#active">active
+   document</a> in its <a href="#browsing0">browsing context</a>, the user
+   agent must run the script according to the semantics that the relevant
+   scripting language defines.
 
   <p>If the script is from an external file, then that file must be used as
    the file to execute.
@@ -26112,6 +26114,12 @@ JSURI: http://ietfreport.isoc.org/all-ids/draft-hoehrmann-javascript-scheme-00.t
 
   <h4 id=events><span class=secno>4.9.5. </span>Events</h4>
 
+  <p class=big-issue>We need to define how to handle events that are to be
+   fired on a Document that is no longer the active document of its browsing
+   context, and for Documents that have no browsing context. Do the events
+   fire? Do the handlers in that document not fire? Do we just define
+   scripting to be disabled when the document isn't active?
+
   <h5 id=event-handler-attributes><span class=secno>4.9.5.1. </span>Event
    handler attributes</h5>
 

source

@@ -16798,11 +16798,13 @@ notes on what would need to be defined for dashed lines:
 
   <p>If the load was successful, then first the user agent must
   <span>fire a <code title="event-load">load</code> event</span> at
-  the element, and then, if <span>scripting is enabled</span> and the
+  the element, and then, if <span>scripting is enabled</span>, and the
   <code>Document</code> does not have <code
-  title="dom-document-designMode">designMode</code> enabled, the user
-  agent must run the script according to the semantics of the relevant
-  scripting language defines.</p>
+  title="dom-document-designMode">designMode</code> enabled, and the
+  <code>Document</code> is the <span>active document</span> in its
+  <span>browsing context</span>, the user agent must run the script
+  according to the semantics that the relevant scripting language
+  defines.</p>
 
   <p>If the script is from an external file, then that file must be
   used as the file to execute.</p>
@@ -23602,6 +23604,13 @@ JSURI: http://ietfreport.isoc.org/all-ids/draft-hoehrmann-javascript-scheme-00.t
 
   <h4>Events</h4>
 
+  <p class="big-issue">We need to define how to handle events that are
+  to be fired on a Document that is no longer the active document of
+  its browsing context, and for Documents that have no browsing
+  context. Do the events fire? Do the handlers in that document not
+  fire? Do we just define scripting to be disabled when the document
+  isn't active?</p>
+
   <h5 id="event-handler-attributes">Event handler attributes</h5>
 
   <p><span>HTML elements</span> can have <dfn>event handler