Permalink
Commits on Aug 26, 2016
  1. @jyasskin @domenic

    Editorial: export more definitions for Bikeshed-using specs

    In particular, this takes care of the terms that Bluetooth and
    Permissions use.
    jyasskin committed with domenic Aug 26, 2016
  2. @domenic

    Make quality an explicit argument for canvas image conversion

    Fixes #452, by making canvas's toDataURL and toBlob explicitly accept a
    quality argument. This replaces the generic argument-passing
    infrastructure that was in place previously, but was only used for JPEG
    quality.
    
    While there:
    
    - Allowed the quality argument to be used by any format that has
    variable quality, such as WebP, since (according to
    https://developer.mozilla.org/en-US/docs/Web/API/HTMLCanvasElement/toDataURL)
    Chrome supports it alongside a type of "image/webp"
    - Removed the now-unused "native flag" from this section
    domenic committed on GitHub Aug 26, 2016
  3. @domenic

    Rename and expose the TransferHelper abstract operation

    Fixes #1616.
    domenic committed on GitHub Aug 26, 2016
  4. @domenic @annevk

    Change minlength/maxlength behavior around linebreaks

    As discussed in #1467, the current situation around these attributes is
    not very interoperable. Some browsers count line breaks as two
    characters (per the spec before this change), others as one character.
    
    Per discussions, this updates minlength and maxlength to count line
    breaks as one character. We believe this is the most developer-friendly
    approach, as evidenced in part by repeated complaints against Chromium
    for its behavior following the previous standard.
    
    While here, updated the textLength property to return the code-point
    length of the element's API value, instead of the element's value, since
    as per http://software.hixie.ch/utilities/js/live-dom-viewer/?saved=4304
    that is what browsers actually do. Similarly, updated the conformance
    requirement on the text content of the textarea element to match
    maxlength's actually-implemented behavior.
    
    Fixes part of #1467, but the debate remains about code-unit length vs.
    code-point length vs. number of grapheme clusters.
    domenic committed with annevk Aug 26, 2016
Commits on Aug 25, 2016
  1. @domenic

    Do not repeat the referrer policies

    Instead, simply delegate to the referrer policy spec. This makes it
    easier to add new referrer policies without editing HTML.
    
    Fixes #1656. See also
    w3c/webappsec-referrer-policy#62.
    domenic committed on GitHub Aug 25, 2016
  2. @domenic

    Fix reloads to not wipe out future session history

    Fixes #1578. When performing a reload via location.reload() or a user
    interface element, it seems more correct to go down the "entry update"
    path, instead of going down the normal path and turning on "replacement
    enabled". The normal path wipes out all session history entries after
    the current one, which is not what browsers do when reloading.
    domenic committed on GitHub Aug 25, 2016
  3. @domenic @annevk

    Update advice to favor the relevant realm over the current one

    Fixes #1653, and also clarifies and tidies up some stuff while in the area.
    domenic committed with annevk Aug 25, 2016
Commits on Aug 24, 2016
  1. @domenic @annevk
  2. @domenic @annevk

    Process custom element connectedCallback immediately during parsing

    Fixes w3c/webcomponents#551 by ensuring that
    insertions into the DOM trigger connectedCallback immediately, instead
    of putting the callback reaction on the the backup element queue and
    letting it get triggered at the next microtask checkpoint. This means
    connectedCallback will generally be invoked when the element has zero
    children, as expected, instead of a random number depending on when the
    next custom element is seen.
    domenic committed with annevk Aug 24, 2016
Commits on Aug 23, 2016
  1. @domenic @annevk

    Move the check on registering an element interface as a custom element

    Previously, this would be prevented at definition time. However, that
    required extra work to know all of the possible element interfaces, and
    was inconsistent with other failure cases. This moves the necessary
    check to construction time, which allows it to be simplified. Fixes
    w3c/webcomponents#541.
    domenic committed with annevk Aug 23, 2016
Commits on Aug 22, 2016
  1. @jyasskin @domenic

    Editorial: fix the metadata of "origin" <dfn>s

    The definition of origins in general should have for="", while
    definitions of a foo's origin should have for="foo".
    
    This contains some workarounds for Bikeshed bugs where it picks up dfns
    even though they are explicitly marked as "noexport", by giving them
    for="" values.
    jyasskin committed with domenic Aug 22, 2016
  2. @annevk @zcorpan

    Editorial: hober's name changed

    annevk committed with zcorpan Aug 22, 2016
Commits on Aug 20, 2016
  1. @domenic @annevk

    Simplify the reentrance guard for custom element definition

    Previously, we would allow reentrance as long as it was not with the
    same name or constructor as was currently being defined, using the
    mechanism of a "set of being-defined names" and "set of being-defined
    constructors". This was overly complex, given that there are not really
    any use cases for defining a custom element in a getter triggered by the
    element definition algorithm. So instead, we move to just using an
    overall reentrance-guard flag.
    
    Fixes w3c/webcomponents#545.
    domenic committed with annevk Aug 20, 2016
Commits on Aug 19, 2016
  1. @domenic

    Do not throw for zero colgroup/col.span and textarea.rows/cols

    Instead, fall back to the default value.
    
    For col/colgroup, 3/4 engines do not throw; this aligns with the
    majority. For textarea, 2/4 engines do not throw, and Firefox would like
    to align with not throwing. More detail at
    #1200 (comment).
    
    Fixes #1200.
    domenic committed on GitHub Aug 19, 2016
  2. @mikewest @annevk

    Editorial: moar bikeshed metadata

    This should cover the few remaining terms that CSP needs, and does some drive-by work for MIX and REFERRER-POLICY as well.
    mikewest committed with annevk Aug 19, 2016
Commits on Aug 18, 2016
  1. @xidachen @domenic

    Correct a small mistake in TextMetrics

    When the given baseline is the top of the em square, then its distance
    to the lowest bottom of the em square cannot be 0.
    xidachen committed with domenic Aug 18, 2016
  2. @zcorpan @annevk
  3. @annevk @zcorpan

    Editorial: "actually disabled" is also used for :enabled now

    PR #1672 made :enabled use the actually disabled definition. This fixes
    the note below actually disabled to reflect that change.
    annevk committed with zcorpan Aug 18, 2016
  4. @mikewest @annevk

    Upstream navigation hooks from CSP

    This will enable implementation of 'frame-ancestors' and 'form-action', and makes a bit of progress towards #1230.
    mikewest committed with annevk Aug 18, 2016
  5. @mikewest @annevk

    Editorial: add bikeshed metadata

    This patch adds bikeshed metadata for various concepts and terms used by CSP and related specifications.
    mikewest committed with annevk Aug 18, 2016
  6. @annevk
Commits on Aug 17, 2016
  1. @zcorpan

    Upstream the innerText spec

    From https://rocallahan.github.io/innerText-spec/
    with the following normative changes:
    
    * Defined behavior for non-CSS UAs.
    * The setter is better defined.
    * Added [CEReactions, TreatNullAs=EmptyString]
      to the IDL.
    
    Fixes #465.
    
    Remaining issues: #1679
    zcorpan committed on GitHub Aug 17, 2016
  2. @gibson042 @domenic

    Define :enabled by reference to "actually disabled"

    This makes it obvious that the list of conditions for :enabled and
    :disabled are inverses of each other.
    
    Removes a no-longer-accurate comment about disabling a/area/link
    elements.
    gibson042 committed with domenic Aug 17, 2016
  3. @domenic @annevk

    Make document.write etc. throw during parsing custom elements

    That is, document.open/close/write/writeln now all throw immediately if
    used while the parser is invoking a custom element constructor, to
    prevent them from messing with the token stream. Closes #1630 and closes
    w3c/webcomponents#537.
    domenic committed with annevk Aug 17, 2016
Commits on Aug 16, 2016
  1. @annevk @domenic

    Editorial: export more terms for usage by Bikeshed

    In particular:
    
    * associated `Document`
    * current settings object
    * current global object
    * relevant settings object
    * relevant Realm
    * relevant global object
    
    This should help the DOM Standard:
    whatwg/dom#296.
    annevk committed with domenic Aug 16, 2016
  2. @mathiasbynens @annevk

    Remove references to the JavaScript Standard

    The JavaScript Standard has accomplished its goal. Some remaining
    web compatibility issues are tracked over at
    https://github.com/tc39/ecma262/labels/web%20reality, to which
    https://javascript.spec.whatwg.org/ now redirects. The rest of the
    contents of the JavaScript Standard have been upstreamed into
    ECMAScript, Annex B.
    
    https://blog.whatwg.org/javascript
    
    Fixes #1660.
    mathiasbynens committed with annevk Aug 16, 2016
  3. @domenic @zcorpan
  4. @zcorpan @sideshowbarker

    Editorial: change alt text of outline image (#1671)

    Image introduced in bd6758b
    
    Also fix a nearby typo.
    zcorpan committed with sideshowbarker Aug 16, 2016
Commits on Aug 15, 2016
  1. @domenic
  2. @zcorpan @domenic

    Fix broken cross-references to CSSOM

    Fixes #848 by updating things related to CSS style sheet sets to the
    latest CSSOM terminology.
    zcorpan committed with domenic Aug 15, 2016
  3. @domenic @annevk

    Clarify the note about reentrant parsing in document.write()

    Closes #1603. Discussion is ongoing about how custom elements and
    document.write() interact, in both #1630 and in
    w3c/webcomponents#537, but this at least
    clears up the source of confusion in #1603.
    domenic committed with annevk Aug 15, 2016
Commits on Aug 12, 2016
  1. @sideshowbarker @domenic

    Editorial: hgroup makes multi-level heading in outline

    This change clarifies the fact that the outline algorithm requires
    implementations to make any hgroup element in the source result in a
    multi-level heading in the generated outline.
    sideshowbarker committed with domenic Aug 12, 2016
  2. @foolip @domenic

    Drop the name propagation for the object element's name attribute

    Introduced with 0a2ab22, but it appears
    that <object name> as a target for <a target> was never implemented.
    
    Fixes #1623.
    foolip committed with domenic Aug 12, 2016
  3. @foolip

    Handle the timeupdate/pause/ended events in a single task (#1659)

    The motivation for this is to have the "still ended playback" bit as a
    real step, more like how it would be implemented.
    
    Drive-by "run the following substeps" for consistency.
    
    Follow-up to #1646 and #1647.
    foolip committed on GitHub Aug 12, 2016
  4. @mounirlamouri @foolip