Permalink
Browse files

[e] (0) Lay the groundwork for DOM Core to handle reentrant mutation …

…observers.

Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=20821
Affected topics: HTML

git-svn-id: http://svn.whatwg.org/webapps@7980 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information...
Hixie committed Jun 14, 2013
1 parent a5c38e0 commit 32122252553357b90931174485560d1932b51232
Showing with 36 additions and 3 deletions.
  1. +10 −1 complete.html
  2. +10 −1 index
  3. +16 −1 source
@@ -71481,7 +71481,8 @@ <h5 id=processing-model-4><span class=secno>7.1.4.2 </span>Processing model</h5>

<p><a href=#concept-mo-invoke title=concept-mo-invoke>Invoke <code>MutationObserver</code> objects</a> for the
<a href=#unit-of-related-similar-origin-browsing-contexts>unit of related similar-origin browsing contexts</a> to which the <a href="#script's-browsing-context">script's
browsing context</a> belongs.</p>
browsing context</a> belongs, using the <a href=#task-wrapper-algorithm>task wrapper algorithm</a> as the steps to
invoke each callback.</p>

<p class=note>This will typically invoke scripted callbacks, which calls the <a href=#jump-to-a-code-entry-point>jump to a
code entry-point</a> algorithm, which calls this <a href=#perform-a-microtask-checkpoint>perform a microtask checkpoint</a>
@@ -71504,6 +71505,14 @@ <h5 id=processing-model-4><span class=secno>7.1.4.2 </span>Processing model</h5>
<p class=note>Steps in <a href=#synchronous-section title="synchronous section">synchronous sections</a> are marked
with &#8987;.</p>

<hr><p>The <dfn id=task-wrapper-algorithm>task wrapper algorithm</dfn>, which is implicitly invoked in the context of an
<a href=#event-loop>event loop</a> and is used to invoke a given <var title="">callback</var> in a specific
way, is as follows:</p>

<ol><li><p>Invoke <var title="">callback</var> as specified.</li>

</ol><p class=XXX>The above will change shortly.</p>

<hr><p>When an algorithm says to <dfn id=spin-the-event-loop>spin the event loop</dfn> until a condition <var title="">goal</var> is met, the user agent must run the following steps:</p>

<ol><li><p>Let <var title="">task source</var> be the <a href=#task-source>task source</a> of the currently
11 index
@@ -71481,7 +71481,8 @@ interface <dfn id=navigatoronline>NavigatorOnLine</dfn> {

<p><a href=#concept-mo-invoke title=concept-mo-invoke>Invoke <code>MutationObserver</code> objects</a> for the
<a href=#unit-of-related-similar-origin-browsing-contexts>unit of related similar-origin browsing contexts</a> to which the <a href="#script's-browsing-context">script's
browsing context</a> belongs.</p>
browsing context</a> belongs, using the <a href=#task-wrapper-algorithm>task wrapper algorithm</a> as the steps to
invoke each callback.</p>

<p class=note>This will typically invoke scripted callbacks, which calls the <a href=#jump-to-a-code-entry-point>jump to a
code entry-point</a> algorithm, which calls this <a href=#perform-a-microtask-checkpoint>perform a microtask checkpoint</a>
@@ -71504,6 +71505,14 @@ interface <dfn id=navigatoronline>NavigatorOnLine</dfn> {
<p class=note>Steps in <a href=#synchronous-section title="synchronous section">synchronous sections</a> are marked
with &#8987;.</p>

<hr><p>The <dfn id=task-wrapper-algorithm>task wrapper algorithm</dfn>, which is implicitly invoked in the context of an
<a href=#event-loop>event loop</a> and is used to invoke a given <var title="">callback</var> in a specific
way, is as follows:</p>

<ol><li><p>Invoke <var title="">callback</var> as specified.</li>

</ol><p class=XXX>The above will change shortly.</p>

<hr><p>When an algorithm says to <dfn id=spin-the-event-loop>spin the event loop</dfn> until a condition <var title="">goal</var> is met, the user agent must run the following steps:</p>

<ol><li><p>Let <var title="">task source</var> be the <a href=#task-source>task source</a> of the currently
17 source
@@ -79949,7 +79949,8 @@ interface <dfn>NavigatorOnLine</dfn> {

<p><span title="concept-mo-invoke">Invoke <code>MutationObserver</code> objects</span> for the
<span>unit of related similar-origin browsing contexts</span> to which the <span>script's
browsing context</span> belongs.</p>
browsing context</span> belongs, using the <span>task wrapper algorithm</span> as the steps to
invoke each callback.</p>

<p class="note">This will typically invoke scripted callbacks, which calls the <span>jump to a
code entry-point</span> algorithm, which calls this <span>perform a microtask checkpoint</span>
@@ -79979,6 +79980,20 @@ interface <dfn>NavigatorOnLine</dfn> {

<hr>

<p>The <dfn>task wrapper algorithm</dfn>, which is implicitly invoked in the context of an
<span>event loop</span> and is used to invoke a given <var title="">callback</var> in a specific
way, is as follows:</p>

<ol>

<li><p>Invoke <var title="">callback</var> as specified.</p></li>

</ol>

<p class="XXX">The above will change shortly.</p>

<hr>

<p>When an algorithm says to <dfn>spin the event loop</dfn> until a condition <var
title="">goal</var> is met, the user agent must run the following steps:</p>

0 comments on commit 3212225

Please sign in to comment.