From 80f3639e018b515c35f8f4b80a57f160003edb1d Mon Sep 17 00:00:00 2001 From: Domenic Denicola Date: Fri, 21 Oct 2016 16:39:12 -0400 Subject: [PATCH] Meta: export more terms for Bikeshed-based specs This exports all the terms used by Service Worker, DOM, File API, and IndexedDB. Closes #998. --- source | 159 ++++++++++++++++++++++++++++++--------------------------- 1 file changed, 84 insertions(+), 75 deletions(-) diff --git a/source b/source index c7a4be34348..ffd4eaa8b2f 100644 --- a/source +++ b/source @@ -6791,8 +6791,8 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d

  • Return document's URL.

    • -

    The document base URL of a Document object is the absolute - URL obtained by running these substeps:

    +

    The document base URL of a Document object is the + absolute URL obtained by running these substeps:

      @@ -72097,9 +72097,10 @@ END:VCARD

      Processing model

      -

      The focusing steps for an object new focus target that is - either a focusable area, or an element that is not a focusable area, or a - browsing context, are as follows. They can optionally be run with a fallback target.

      +

      The focusing steps for an object new focus target that is + either a focusable area, or an element that is not a focusable area, or + a browsing context, are as follows. They can optionally be run with a fallback + target.

        @@ -76263,8 +76264,8 @@ dictionary DragEventInit : MouseEventInit {

        Browsing contexts

        -

        A browsing context is an environment in which Document objects are - presented to the user.

        +

        A browsing context is an environment in which Document + objects are presented to the user.

        A tab or window in a Web browser typically contains a browsing context, as does an iframe or frames in a @@ -76276,10 +76277,11 @@ dictionary DragEventInit : MouseEventInit { Document objects that the browsing context has presented, is presenting, or will present. At any time, one Document in each browsing context is designated the active document. - A Document's browsing context - is the browsing context whose session history contains the - Document, if any such browsing context exists and has not been discarded.

        + A Document's browsing context is the browsing context + whose session history contains the Document, if any such browsing + context exists and has not been discarded.

        In general, there is a 1-to-1 mapping from the Window object to the Document object, as long as the Document object has a DragEventInit : MouseEventInit {

        -

        A browsing context can have a creator browsing context, the - browsing context that was responsible for its creation. If a browsing +

        A browsing context can have a creator browsing context, + the browsing context that was responsible for its creation. If a browsing context has a parent browsing context, then that is its creator browsing context. Otherwise, if the browsing context has an opener browsing context, then that is its creator browsing context. Otherwise, the @@ -76427,9 +76429,9 @@ dictionary DragEventInit : MouseEventInit { data-x="browsing context nested through" data-export="">nested through the browsing context container's node document.

        -

        A browsing context child is said to be a child browsing - context of another browsing context parent, if all of the following - conditions hold:

        +

        A browsing context child is said to be a child + browsing context of another browsing context parent, if all of the + following conditions hold:

        • child is a nested browsing context of a browsing context @@ -76683,8 +76685,9 @@ console.assert(iframeWindow.frameElement === null);

          It is possible to create new browsing contexts that are related to a top-level browsing context without being nested through an element. Such browsing contexts are called auxiliary browsing contexts. Auxiliary - browsing contexts are always top-level browsing + data-x="auxiliary browsing context" data-lt="auxiliary browsing context" data-export="">auxiliary + browsing contexts. Auxiliary browsing contexts are always top-level browsing contexts.

          An auxiliary browsing context has an opener browsing @@ -78123,8 +78126,8 @@ callback FrameRequestCallback = void (DOMHighResTimeStamp, and responsible document (if any).

          -

          When a browsing context is to discard a Document, the user - agent must run the following steps:

          +

          When a browsing context is to discard a + Document, the user agent must run the following steps:

            @@ -78151,8 +78154,8 @@ callback FrameRequestCallback = void (DOMHighResTimeStampdiscarded, it is also removed from the list of the worker's Documents of each worker whose list contains that Document.

            -

            When a browsing context is discarded, the strong reference from the user - agent itself to the browsing context must be severed, and all the +

            When a browsing context is discarded, the strong reference + from the user agent itself to the browsing context must be severed, and all the Document objects for all the entries in the browsing context's session history must be discarded as well.

            @@ -80961,15 +80964,15 @@ State: <OUTPUT NAME=I>1</OUTPUT> <INPUT VALUE="Increment" TYPE=BUTTON O and payload. Similarly, an iframe srcdoc document needs to know the data it is to use.

            -

            Navigation always involves source browsing context, which is the browsing context which - was responsible for starting the navigation.

            +

            Navigation always involves source browsing context, which is the + browsing context which was responsible for starting the navigation.

            To navigate a browsing context browsingContext to a - resource resource, optionally with an exceptions - enabled flag, the user agent must run these steps:

            + resource resource, optionally with an exceptions enabled flag, the user agent must run these steps:

            1. If resource is a URL, then set resource to a new 1</OUTPUT> <INPUT VALUE="Increment" TYPE=BUTTON O old URL be the current entry's URL and new URL be entry's URL. Otherwise, let hash changed be false.

              2. -

            2. If the traversal was initiated with replacement enabled, remove the entry - immediately before the specified entry in the session history.

              3. +

            3. If the traversal was initiated with replacement enabled, remove + the entry immediately before the specified entry in the session history.

            4. If entry is not an entry with persisted user state, but its URL's fragment is non-null, then @@ -82658,8 +82661,8 @@ dictionary PageTransitionEventInit : EventInit {

            -

            When a user agent is to unload a document, it must run the following steps. These - steps are passed an argument, recycle, which is either true or false, +

            When a user agent is to unload a document, it must run the following + steps. These steps are passed an argument, recycle, which is either true or false, indicating whether the Document object is going to be re-used. (This is set by the document.open() method.)

            @@ -83111,7 +83114,7 @@ NETWORK:

            Application caches

            -

            An application cache is a set of cached resources consisting of:

            +

            An application cache is a set of cached resources consisting of:

              @@ -85413,12 +85416,12 @@ interface NavigatorOnLine {
              Definitions
              -

              A script is one of two possible structures. All scripts - have:

              +

              A script is one of two possible structures. + All scripts have:

              -
              A settings object
              +
              A settings object
              @@ -85430,7 +85433,7 @@ interface NavigatorOnLine {
              -

              A classic script additionally has:

              +

              A classic script additionally has:

              @@ -85455,7 +85458,7 @@ interface NavigatorOnLine {
              -

              A module script additionally has:

              +

              A module script additionally has:

              @@ -86428,10 +86431,11 @@ interface NavigatorOnLine {
              -

              Each unit of related similar-origin browsing contexts has a global script - clean-up jobs list, which must initially be empty. A global script clean-up job cannot run - scripts, and cannot be sensitive to the order in which other clean-up jobs are executed. The File - API uses this to release blob: URLs.

              +

              Each unit of related similar-origin browsing contexts has a global script clean-up jobs list, which must initially be empty. A global + script clean-up job cannot run scripts, and cannot be sensitive to the order in which other + clean-up jobs are executed. The File API uses this to release blob: URLs.

              When the user agent is to run the global script clean-up jobs, the user agent must perform each of the jobs in the global script clean-up jobs list and then empty the @@ -87250,8 +87254,9 @@ document.querySelector("button").addEventListener("click", bound);

              Runtime script errors in documents
              -

              When the user agent is to report an exception - E, the user agent must report the error for the relevant When the user agent is to report an exception E, the user + agent must report the error for the relevant script, with the problematic position (line number and column number) in the resource containing the script, using the global object specified by the script's @@ -87458,9 +87463,10 @@ dictionary PromiseRejectionEventInit : EventInit {

              Definitions

              To coordinate events, user interaction, scripts, rendering, networking, and so forth, user - agents must use event loops as described in this section. There are - two kinds of event loops: those for browsing contexts, and - those for workers.

              + agents must use event loops as + described in this section. There are two kinds of event loops: those for browsing contexts, and those for workers.

              There must be at least one browsing context event loop per user agent, and at most one per unit of related similar-origin browsing contexts.

              @@ -87483,8 +87489,8 @@ dictionary PromiseRejectionEventInit : EventInit {

              An event loop has one or more task queues. A - task queue is an ordered list of tasks, which are - algorithms that are responsible for such work as:

              + task queue is an ordered list of tasks, which are algorithms that are responsible for such work as:

              @@ -87543,9 +87549,9 @@ dictionary PromiseRejectionEventInit : EventInit { one of the task queues of the relevant event loop.

              -

              Each task is defined as coming from a specific task - source. All the tasks from one particular task source and destined to a - particular event loop (e.g. the callbacks generated by timers of a +

              Each task is defined as coming from a specific task source. All the tasks from one particular task source and + destined to a particular event loop (e.g. the callbacks generated by timers of a Document, the events fired for mouse movements over that Document, the tasks queued for the parser of that Document) must always be added to the same task queue, but tasks from different PromiseRejectionEventInit : EventInit {

              -

              Each event loop has a microtask queue. A microtask is a - task that is originally to be queued on the microtask - queue rather than a task queue. There are two kinds of microtasks: solitary callback - microtasks, and compound microtasks.

              +

              Each event loop has a microtask queue. A microtask is a task that is originally to + be queued on the microtask queue rather than a task queue. There are two + kinds of microtasks: solitary callback + microtasks, and compound microtasks.

              This specification only has solitary callback microtasks. Specifications that use compound @@ -87745,9 +87753,9 @@ dictionary PromiseRejectionEventInit : EventInit { loop.

              When an algorithm requires a microtask to be queued, it must be appended to the relevant event loop's - microtask queue; the task source of such a microtask is the - microtask task source.

              + microtask" data-lt="queue a microtask" data-export="">queued, it must be appended to the + relevant event loop's microtask queue; the task source of + such a microtask is the microtask task source.

              It is possible for a microtask to be moved to a regular task queue, if, during its initial execution, it spins the @@ -87798,8 +87806,8 @@ dictionary PromiseRejectionEventInit : EventInit {

          If, while a compound microtask is running, the user agent is required to - execute a compound microtask subtask to run a series of steps, the user agent must run - the following steps:

          + execute a compound microtask subtask to run a series of steps, the user + agent must run the following steps:

            @@ -87935,7 +87943,7 @@ dictionary PromiseRejectionEventInit : EventInit {
            -
            The DOM manipulation task source
            +
            The DOM manipulation task source
            @@ -87945,7 +87953,7 @@ dictionary PromiseRejectionEventInit : EventInit {
            -
            The user interaction task source
            +
            The user interaction task source
            @@ -87960,7 +87968,7 @@ dictionary PromiseRejectionEventInit : EventInit {
            -
            The networking task source
            +
            The networking task source
            @@ -87969,7 +87977,7 @@ dictionary PromiseRejectionEventInit : EventInit {
            -
            The history traversal task source
            +
            The history traversal task source
            @@ -87990,8 +87998,9 @@ dictionary PromiseRejectionEventInit : EventInit { -

            Many objects can have event handlers specified. These act as - non-capture event listeners for the object on which they are specified.

            +

            Many objects can have event handlers + specified. These act as non-capture event listeners for the object on which they are specified. +

            An event handler has a name, which always starts with "on" and is followed by the name of the event for which it is intended.

            @@ -88041,10 +88050,10 @@ dictionary PromiseRejectionEventInit : EventInit { -

            An event handler content attribute is a - content attribute for a specific event handler. The name of - the content attribute is the same as the name of the event - handler.

            +

            An event handler content + attribute is a content attribute for a specific event + handler. The name of the content attribute is the same as the name of the event handler.

            Event handler content attributes, when specified, must contain valid JavaScript code which, when parsed, would match the FunctionBody @@ -88145,7 +88154,7 @@ dictionary PromiseRejectionEventInit : EventInit {

            If E is an ErrorEvent object and the event handler IDL attribute's type is + handler IDL attributes" data-export="">event handler IDL attribute's type is OnErrorEventHandler
            @@ -89655,9 +89664,9 @@ document.body.appendChild(frame)
            -

            Objects that implement the WindowOrWorkerGlobalScope mixin have a list of - active timers. Each entry in this lists is identified by a number, which must be unique - within the list for the lifetime of the object that implements the +

            Objects that implement the WindowOrWorkerGlobalScope mixin have a list of active timers. Each entry in this lists is identified by a number, + which must be unique within the list for the lifetime of the object that implements the WindowOrWorkerGlobalScope mixin.

            @@ -98642,7 +98651,7 @@ dictionary StorageEventInit : EventInit {

            User agents must use the parsing rules described in this section to generate the DOM trees from text/html resources. Together, these rules define what is referred to as the - HTML parser.

            + HTML parser.