Commits on Nov 17, 2017
  1. Ensure there is an active script while running JS jobs

    domenic committed Nov 17, 2017
    "Fixes" tc39/ecma262#871, at least for HTML,
    given that we have our own version of EnqueueJob. Important for #3117.
  2. Update how DOMMatrix is created from a dictionary

    zcorpan committed Nov 4, 2017
    This follows w3c/fxtf-drafts#218 and should
    have no normative difference.
Commits on Nov 16, 2017
Commits on Nov 14, 2017
  1. Editorial: reduce "abort these steps" usage

    sam0410 committed with annevk Nov 14, 2017
    Helps with #2878.
Commits on Nov 13, 2017
  1. Editorial: remove alternative HTML parser algorithm names

    dauwhe committed with annevk Nov 13, 2017
    Instead, link to a blog post post detailing them and their origins.
Commits on Nov 9, 2017
  1. Editorial: change "has" to "have"

    ibz096 committed with annevk Nov 9, 2017
    Fixes #3206.
Commits on Nov 7, 2017
  1. Add import.meta.url

    domenic committed Oct 18, 2017
    This integrates with the stage 3 import.meta proposal located at This is based on
    although it only includes the easier part, import.meta.url.
    import.meta.scriptElement is still being discussed, at #1013, and as
    such is excluded for now.
  2. Delete and redirect a demo using CGI

    foolip committed Nov 7, 2017
    This is similar to whatwg/, and
    stands in the way of new hosting for HTML:
Commits on Nov 6, 2017
  1. Enumerate fewer cross-origin properties

    annevk committed with domenic Nov 6, 2017
    In 205659f we made all properties on
    cross-origin objects enumerable, equivalent to their same-origin object
    However, this turned out not be web-compatible. This makes them
    non-enumerable again with the exception of array index property names,
    which need to be enumerable.
    Tests: w3c/web-platform-tests#8045
    Fixes #3183.
Commits on Nov 4, 2017
Commits on Oct 31, 2017
  1. Dev edition: show "About this spec" on the index only

    sideshowbarker committed with domenic Oct 31, 2017
    This change causes the dev edition "About this specification" section to
    be shown only on the (index) page
    rather than on every (split) page of the dev edition.
    Fixes #3160.
Commits on Oct 29, 2017
  1. Editorial: Fix “should” in input/textarea domintro

    sideshowbarker committed with domenic Oct 28, 2017
    This change replaces an accidental occurrence of the RFC 2119 keyword
    “should” in the domintro for attributes and methods related to selection
    inside “input” and “textarea” element content.
  2. Editorial: Cut dev-edition event-handler “must”s

    sideshowbarker committed with domenic Oct 28, 2017
    This change fixes a few places in the developer edition that had this language:
    > The following are the event handlers (and their corresponding event handler
    > event types) that must be supported...
    The fix ensure that the developer edition has instead this language:
    > The following are the event handlers (and their corresponding event handler
    > event types) supported...
    That is, the “that must be” part gets suppressed in the developer edition.
Commits on Oct 27, 2017
  1. Add a domintro block for WebSocket interface

    sideshowbarker committed with domenic Oct 27, 2017
    This change adds a domintro block in the section that defines the WebSocket
    interface and also the section that defines the CloseEvent interface.
    Additionally, it adds markup to cause more implementor-specific parts of the
    “Web sockets” section of the spec to be supressed in the developer edition.
Commits on Oct 26, 2017
  1. Add element.focus({ preventScroll: true })

    jihyerish committed with domenic Oct 26, 2017
    Addresses the most basic part of #834, allowing further customizations
    to be done by JavaScript code.
Commits on Oct 25, 2017
  1. Editorial: remove stray heading from dev edition

    sideshowbarker committed with annevk Oct 25, 2017
    This change suppresses a stray “IDL definitions” subheading that otherwise shows
    up at (in the
    dev edition) as a content-less subsection (because all that subsection contains
    is an IDL block, which the dev build already automatically suppresses).
Commits on Oct 22, 2017
  1. Editorial: optons -> options

    cynthia committed with annevk Oct 22, 2017
  2. Drop creator context security

    annevk committed Oct 21, 2017
    We added it for Secure Contexts, but that no longer uses it per w3c/webappsec-secure-contexts#48.
    Reverts 91f1919 (except for the transformation to a description list).
Commits on Oct 20, 2017
  1. Meta: disambiguate focus() and blur() for Window and HTMLElement

    zcorpan committed with domenic Oct 20, 2017
    Add data-dfn-for="" attributes as appropriate. This should help other
    specs (in this case CSSOM View) cross-referencing these terms.
    Also fixes a few cases where data-for="" should have been
Commits on Oct 17, 2017
  1. Editorial: mark "subdfn"s in some places where they were missing

    sideshowbarker committed with domenic Oct 17, 2017
    This change adds the "subdfn" attribute to some elements in "domintro"
    sections that were missing it. This enables the dev edition to have the
    right fragment IDs and cross-references for those items.
Commits on Oct 16, 2017
  1. Fix ordering of custom element upgrade steps

    domenic committed Oct 13, 2017
    This fixes #2876, ensuring that a custom element definition is always
    present when we enqueue a reaction.
Commits on Oct 13, 2017
  1. Fix module script error handling, again

    domenic committed Aug 30, 2017
    Recent investigation determined more problems with the module script
    graph fetching algorithms with regard to error handling. Essentially,
    they were not robust to network races during fetching. Certain errors
    would be propagated nondeterministically; worse, Evaluate() could be
    called on modules with errored dependencies, due to another module
    script graph interleaving its instantiation between a graph's
    instantiation and evaluation.
    This revision avoids all these problems. The strategy is essentially:
    * Do not record instantiation errors of dependencies. This is mostly a
      feature of a corresponding revision to the JavaScript specification;
      we just no longer look for such errors. Instead, we call
      Instantiate(), which now does a from-scratch re-instantiation attempt,
      finding the appropriate error each time.
    * Do not record parse errors of dependencies. Instead, traverse the
      graph right before instantiation to deterministically find the first
      parse error.
    To implement this strategy, a new error-to-rethrow item was added to the
    script struct, whose purpose is to store an error that is to be re-thrown
    during instantiation. (An alternate implementation would have been to
    find another way of passing the error from "prepare a script" and its
    associated script-fetching algorithms, to "execute a script block" and
    its associated script-running algorithms. But the script struct was a
    convenient place to keep this.)
    Note that with this strategy we no longer inspect the [[Status]] or
    [[ErrorCompletion]] fields of JavaScript's Source Text Module Records;
    instead, we can simply call Instantiate() or Evaluate() and deal with
    any thrown errors. This is a much nicer encapsulation boundary.
    This follows upon
Commits on Oct 11, 2017
Commits on Oct 10, 2017
  1. Fix typo in a canvas example

    annevk committed with domenic Oct 10, 2017
Commits on Oct 9, 2017
  1. Regression fix: tokenize features earlier in

    annevk committed with domenic Oct 9, 2017
    Regressed in a68a1f7.
    Fixes #3107.
Commits on Oct 6, 2017
  1. Editorial: add missing <hr>

    annevk committed with domenic Oct 6, 2017
    Also move a comment to the correct place.
  2. Require UTF-8

    sideshowbarker committed with annevk Oct 6, 2017
    This change adds a “must” requirement for UTF-8 in all but one of the places in the standard that define a means for specifying a character encoding.
    Specifically, it makes UTF-8 required for any “character encoding declaration”, which includes the HTTP Content-Type header sent with any document, the `<meta charset>` element, and the `<meta http-equiv=content-type>` element.
    Along with those, this change also makes UTF-8 required for `<script charset>` but also moves `<script charset>` to being obsolete-but-conforming (because now that both documents and scripts are required to use UTF-8, it’s redundant to specify `charset` on the `script` element, since it inherits from the document).
    To make the normative source of those requirements clear, this change also adds a specific citation to the relevant requirement from the Encoding standard, and updates the in-document IANA registration for text/html media type to indicate that UTF-8 is required. Finally, it changes an existing requirement for authoring tools to use UTF-8 from a “should” to a “must”.
    The one place where this change doesn’t yet add a requirement for UTF-8 is for the `form` element’s `accept-charset` attribute. For that, see issue #3097.
    Closes #3004.