W3C home > Mailing lists > Public > public-html-commits@w3.org > December 2008

html5/spec Overview.html,1.1700,1.1701

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 16 Dec 2008 00:55:41 +0000
To: public-html-commits@w3.org
Message-Id: <E1LCODt-0007CY-5A@lionel-hutz.w3.org>

Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv27662

Modified Files:
	Overview.html 
Log Message:
Update terminology to help Workers specification. (whatwg r2530)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1700
retrieving revision 1.1701
diff -u -d -r1.1700 -r1.1701
--- Overview.html	12 Dec 2008 08:46:29 -0000	1.1700
+++ Overview.html	16 Dec 2008 00:55:38 -0000	1.1701
@@ -8,7 +8,7 @@
    <p><a href=http://www.w3.org/><img alt=W3C height=48 src=http://www.w3.org/Icons/w3c_home width=72></a></p>
    <h1>HTML 5</h1>
    <h2 class="no-num no-toc" id=a-vocabulary-and-associated-apis-for-html-and-xhtml>A vocabulary and associated APIs for HTML and XHTML</h2>
-   <h2 class="no-num no-toc" id=editor-s-draft-date-zzz-9-june-2008><!-- "W3C Working Draft" --> Editor's Draft <!--ZZZ-->12 December 2008</h2>
+   <h2 class="no-num no-toc" id=editor-s-draft-date-zzz-9-june-2008><!-- "W3C Working Draft" --> Editor's Draft <!--ZZZ-->16 December 2008</h2>
    <dl><!-- ZZZ: update the month/day
     <dt>This Version:</dt>
     <dd><a href="http://www.w3.org/TR/2008/WD-html5-20080610/">http://www.w3.org/TR/2008/WD-html5-20080610/</a></dd>
@@ -97,7 +97,7 @@
   specification's progress along the W3C Recommendation
   track.
   <!--ZZZ:-->
-  This specification is the 12 December 2008 <!--ZZZ "Working Draft"-->Editor's Draft.
+  This specification is the 16 December 2008 <!--ZZZ "Working Draft"-->Editor's Draft.
   <!--:ZZZ-->
   </p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- relationship to other work (required) --><p>This specification is also being produced by the <a href=http://www.whatwg.org/>WHATWG</a>. The two specifications are
   identical from the table of contents onwards.</p><!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- context and rationale (required) --><p>This specification is intended to replace (be a new version of)
@@ -1255,8 +1255,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=#references>[RFC2119]</a></p><!-- XXX but they should be
-  marked up --><p>Requirements phrased in the imperative as part of algorithms
+  not appear in all uppercase letters in this specification. <a href=#references>[RFC2119]</a><p>Requirements phrased in the imperative as part of algorithms
   (such as "strip any leading space characters" or "return false and
   abort these steps") are to be interpreted with the meaning of the
   key word ("must", "should", "may", etc) used in introducing the
@@ -7939,7 +7938,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>
@@ -27224,7 +27223,7 @@
   following steps:<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
@@ -27253,8 +27252,8 @@
   group. The character encoding and base URL for the resulting <a href=#concept-script title=concept-script>script</a> are not important as no APIs
   are exposed to the script.</p><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><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:<ol><li><p>Let <var title="">document</var> be the
    <code>Document</code> of <var title="">node</var> (or <var title="">node</var> itself if it is a
    <code>Document</code>).</li>
@@ -27284,7 +27283,8 @@
   context</a>. If an <a href=#event-loop>event loop</a>'s <a href=#browsing-context title="browsing context">browsing contexts</a> all go away, then
   the <a href=#event-loop>event loop</a> goes away as well. A <a href=#browsing-context>browsing
   context</a> always has an <a href=#event-loop>event loop</a> coordinating
-  its activities.<p>An <a href=#event-loop>event loop</a> has one or more <dfn id=task-queue title="task
+  its activities.<p class=note>Other specifications can define new kinds of event
+  loops that aren't associated with browsing contexts.<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:<dl><dt>Events</dt>
 
@@ -27842,7 +27842,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
@@ -27850,11 +27850,11 @@
   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><dfn id=fire-a-simple-event title="fire a simple event">Firing a simple event called
+  target.<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><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
+  target.<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
   modifier information (shift/ctrl etc), as well as having a pointer
   to the node on which the menu was fired, and with which the menu was
Received on Tuesday, 16 December 2008 00:55:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 16 December 2008 00:55:51 GMT