[html5] r2530 - [e] (0) Update terminology to help Workers specification.
whatwg at whatwg.org
whatwg at whatwg.org
Mon Dec 15 16:55:33 PST 2008
Author: ianh
Date: 2008-12-15 16:55:33 -0800 (Mon, 15 Dec 2008)
New Revision: 2530
Modified:
header-whatwg
index
source
Log:
[e] (0) Update terminology to help Workers specification.
Modified: header-whatwg
===================================================================
--- header-whatwg 2008-12-12 08:46:24 UTC (rev 2529)
+++ header-whatwg 2008-12-16 00:55:33 UTC (rev 2530)
@@ -18,6 +18,10 @@
#configUI p { padding: 0.3em; background: #EEEEEE; color: black; border: inset thin; }
#configUI input[type=button] { display: block; margin: auto; }
@media print { #configUI { display: none; } }
+ .rfc2119 { font-variant: small-caps; text-shadow: 0 0 0.5em yellow; position: static; }
+ .rfc2119::after { position: absolute; left: 0; width: 25px; text-align: center; color: yellow; text-shadow: 0.075em 0.075em 0.2em black; }
+ .rfc2119.m\ust::after { content: '\2605'; }
+ .rfc2119.s\hould::after { content: '\2606'; }
</style>
<link rel="stylesheet" href="status.css">
<script src="status.js"></script>
Modified: index
===================================================================
--- index 2008-12-12 08:46:24 UTC (rev 2529)
+++ index 2008-12-16 00:55:33 UTC (rev 2530)
@@ -12,12 +12,16 @@
#configUI p { padding: 0.3em; background: #EEEEEE; color: black; border: inset thin; }
#configUI input[type=button] { display: block; margin: auto; }
@media print { #configUI { display: none; } }
+ .rfc2119 { font-variant: small-caps; text-shadow: 0 0 0.5em yellow; position: static; }
+ .rfc2119::after { position: absolute; left: 0; width: 25px; text-align: center; color: yellow; text-shadow: 0.075em 0.075em 0.2em black; }
+ .rfc2119.m\ust::after { content: '\2605'; }
+ .rfc2119.s\hould::after { content: '\2606'; }
</style><link href=status.css rel=stylesheet><script src=status.js></script><script src=dfn.js></script><body class=draft onload=initAnnotations()>
<div class=head>
<p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG src=/images/logo></a></p>
<h1>HTML 5</h1>
- <h2 class="no-num no-toc" id=draft-recommendation-—-date:-01-jan-1901>Draft Recommendation — 12 December 2008</h2>
+ <h2 class="no-num no-toc" id=draft-recommendation-—-date:-01-jan-1901>Draft Recommendation — 16 December 2008</h2>
<p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
<p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
<dl><dt>Multiple-page version:</dt>
@@ -1547,8 +1551,7 @@
NOT",--> "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
"OPTIONAL" in the normative parts of this document are to be
interpreted as described in RFC2119. For readability, these words do
- not appear in all uppercase letters in this specification. <a href=#refsRFC2119>[RFC2119]</a></p> <!-- XXX but they should be
- marked up -->
+ not appear in all uppercase letters in this specification. <a href=#refsRFC2119>[RFC2119]</a></p>
<p>Requirements phrased in the imperative as part of algorithms
(such as "strip any leading space characters" or "return false and
@@ -9671,7 +9674,7 @@
<ol><li>
- <p>Initialise <dfn id="the-script-block's-source"><var>the script block's source</var></dfn> as
+ <p>Initialize <dfn id="the-script-block's-source"><var>the script block's source</var></dfn> as
follows:</p>
<dl class=switch><dt>If the script is from an external file</dt>
@@ -33602,7 +33605,7 @@
<ol><li><p>Set up a <a href=#script-execution-environment>script execution environment</a> as
appropriate for the scripting language.</li>
- <li><p>Parse/compile/initialise the source of the script using the
+ <li><p>Parse/compile/initialize the source of the script using the
<a href=#script-execution-environment>script execution environment</a>, as appropriate for the
scripting language, and thus obtain the <a href=#list-of-code-entry-points>list of code
entry-points</a> for the script. If the semantics of the
@@ -33633,8 +33636,8 @@
<hr><p>When the specification says that a <a href=#concept-script title=concept-script>script</a> is to be <dfn id=create-a-script-from-a-node title="create a
script from a node">created from a node</dfn> <var title="">node</var>, given some script source and its scripting
- language, the user agent <a href=#create-a-script>create a script</a>, using the
- given script source and scripting language, and using <a href=#the-script-settings-determined-from-the-node>the
+ language, the user agent must <a href=#create-a-script>create a script</a>, using
+ the given script source and scripting language, and using <a href=#the-script-settings-determined-from-the-node>the
script settings determined from the node</a> <var title="">node</var>.</p>
<p><dfn id=the-script-settings-determined-from-the-node>The script settings determined from the node</dfn> <var title="">node</var> are computed as follows:</p>
@@ -33676,6 +33679,9 @@
context</a> always has an <a href=#event-loop>event loop</a> coordinating
its activities.</p>
+ <p class=note>Other specifications can define new kinds of event
+ loops that aren't associated with browsing contexts.</p>
+
<p>An <a href=#event-loop>event loop</a> has one or more <dfn id=task-queue title="task
queue">task queues</dfn>. A <a href=#task-queue>task queue</a> is an ordered
list of <dfn id=concept-task title=concept-task>tasks</dfn>, which can be:</p>
@@ -34301,7 +34307,7 @@
event with no
namespace, which bubbles and is cancelable, and which uses the
<code>MouseEvent</code> interface, must be dispatched at the given
- element. The event object must have its <code title="">screenX</code>, <code title="">screenY</code>, <code title="">clientX</code>, <code title="">clientY</code>, and <code title="">button</code> attributes set to 0, its <code title="">ctrlKey</code>, <code title="">shiftKey</code>, <code title="">altKey</code>, and <code title="">metaKey</code> attributes
+ target. The event object must have its <code title="">screenX</code>, <code title="">screenY</code>, <code title="">clientX</code>, <code title="">clientY</code>, and <code title="">button</code> attributes set to 0, its <code title="">ctrlKey</code>, <code title="">shiftKey</code>, <code title="">altKey</code>, and <code title="">metaKey</code> attributes
set according to the current state of the key input device, if any
(false for any keys that are not available), its <code title="">detail</code> attribute set to 1, and its <code title="">relatedTarget</code> attribute set to null. The <code title="">getModifierState()</code> method on the object must return
values appropriately describing the state of the key input device at
@@ -34311,13 +34317,13 @@
a <code title=event-contextmenu>contextmenu</code> event with no
namespace, which bubbles and is cancelable, and which uses the
<code>Event</code> interface, must be dispatched at the given
- element.</p>
+ target.</p>
<p><dfn id=fire-a-simple-event title="fire a simple event">Firing a simple event called
<var title="">e</var></dfn> means that an event with the name <var title="">e</var>, with no namespace, which does not bubble but is
cancelable (unless otherwise stated), and which uses the
<code>Event</code> interface, must be dispatched at the given
- element.</p>
+ target.</p>
<p><dfn id=fire-a-show-event title="fire a show event">Firing a <code title=event-show>show</code> event</dfn> means <a href=#fire-a-simple-event title="fire a
simple event">firing a simple event called <code title=event-show>show</code></a>. <span class=XXX>Actually this should fire an event that has
Modified: source
===================================================================
--- source 2008-12-12 08:46:24 UTC (rev 2529)
+++ source 2008-12-16 00:55:33 UTC (rev 2530)
@@ -589,8 +589,7 @@
"OPTIONAL" in the normative parts of this document are to be
interpreted as described in RFC2119. For readability, these words do
not appear in all uppercase letters in this specification. <a
- href="#refsRFC2119">[RFC2119]</a></p> <!-- XXX but they should be
- marked up -->
+ href="#refsRFC2119">[RFC2119]</a></p>
<p>Requirements phrased in the imperative as part of algorithms
(such as "strip any leading space characters" or "return false and
@@ -10210,7 +10209,7 @@
<li>
- <p>Initialise <dfn><var>the script block's source</var></dfn> as
+ <p>Initialize <dfn><var>the script block's source</var></dfn> as
follows:</p>
<dl class="switch">
@@ -38226,7 +38225,7 @@
<li><p>Set up a <span>script execution environment</span> as
appropriate for the scripting language.</p></li>
- <li><p>Parse/compile/initialise the source of the script using the
+ <li><p>Parse/compile/initialize the source of the script using the
<span>script execution environment</span>, as appropriate for the
scripting language, and thus obtain the <span>list of code
entry-points</span> for the script. If the semantics of the
@@ -38266,8 +38265,8 @@
title="concept-script">script</span> is to be <dfn title="create a
script from a node">created from a node</dfn> <var
title="">node</var>, given some script source and its scripting
- language, the user agent <span>create a script</span>, using the
- given script source and scripting language, and using <span>the
+ language, the user agent must <span>create a script</span>, using
+ the given script source and scripting language, and using <span>the
script settings determined from the node</span> <var
title="">node</var>.</p>
@@ -38321,6 +38320,9 @@
context</span> always has an <span>event loop</span> coordinating
its activities.</p>
+ <p class="note">Other specifications can define new kinds of event
+ loops that aren't associated with browsing contexts.</p>
+
<p>An <span>event loop</span> has one or more <dfn title="task
queue">task queues</dfn>. A <span>task queue</span> is an ordered
list of <dfn title="concept-task">tasks</dfn>, which can be:</p>
@@ -39051,7 +39053,7 @@
event with no
namespace, which bubbles and is cancelable, and which uses the
<code>MouseEvent</code> interface, must be dispatched at the given
- element. The event object must have its <code
+ target. The event object must have its <code
title="">screenX</code>, <code title="">screenY</code>, <code
title="">clientX</code>, <code title="">clientY</code>, and <code
title="">button</code> attributes set to 0, its <code
@@ -39070,14 +39072,14 @@
a <code title="event-contextmenu">contextmenu</code> event with no
namespace, which bubbles and is cancelable, and which uses the
<code>Event</code> interface, must be dispatched at the given
- element.</p>
+ target.</p>
<p><dfn title="fire a simple event">Firing a simple event called
<var title="">e</var></dfn> means that an event with the name <var
title="">e</var>, with no namespace, which does not bubble but is
cancelable (unless otherwise stated), and which uses the
<code>Event</code> interface, must be dispatched at the given
- element.</p>
+ target.</p>
<p><dfn title="fire a show event">Firing a <code
title="event-show">show</code> event</dfn> means <span title="fire a
More information about the Commit-Watchers
mailing list