Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow use in same-origin children, add Feature Policy integration #13

Merged
merged 11 commits into from
Sep 24, 2019

Commits on May 22, 2018

  1. Stop using incumbent settings object

    This change is editorial.
    
    Tracking bug: whatwg/html#1430
    anssiko committed May 22, 2018
    Configuration menu
    Copy the full SHA
    a369bc9 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    041b059 View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    e9f5442 View commit details
    Browse the repository at this point in the history

Commits on Aug 24, 2018

  1. Fix settings object and global object prose to match the latest HTML

    - Clarify which active document's origin is tested for same origin-domain-ness
    - Use 'relevant settings object' over 'current settings object' where applicable
    - Update 'allowlist' to match the convention
    - Use WHATWG HTML references (except for firing a simple event that's gone)
    - Fix typos
    
    Fix #19
    anssiko committed Aug 24, 2018
    Configuration menu
    Copy the full SHA
    d2458d8 View commit details
    Browse the repository at this point in the history

Commits on Oct 2, 2018

  1. Use 'allowed to use' abstraction, reword Feature Policy integration

    - Use 'allowed to use' as a condition for rejection, move the old
      text to a note
    - Align Feature Policy integration section with the latest prose
    - Fix allowlist notation
    anssiko committed Oct 2, 2018
    Configuration menu
    Copy the full SHA
    fb43978 View commit details
    Browse the repository at this point in the history

Commits on Oct 3, 2018

  1. Clarify note on rejection condition

    Note it is possible to explicitly grant access to cross-origin
    subframes using feature policy, in which case the promise is
    not rejected.
    anssiko committed Oct 3, 2018
    Configuration menu
    Copy the full SHA
    e486c5a View commit details
    Browse the repository at this point in the history

Commits on Jun 26, 2019

  1. Configuration menu
    Copy the full SHA
    a9e3c94 View commit details
    Browse the repository at this point in the history

Commits on Sep 24, 2019

  1. Configuration menu
    Copy the full SHA
    3e08915 View commit details
    Browse the repository at this point in the history
  2. Define EventTarget reference to fix a ReSpec error

    Error message:
    Couldn't match "EventTarget" to anything in the document or in any
    other document cited in this specification: webidl
    anssiko committed Sep 24, 2019
    Configuration menu
    Copy the full SHA
    7ad0dd5 View commit details
    Browse the repository at this point in the history
  3. Merge branch 'issue-10-secure-top-level' of https://github.com/w3c/ba…

    …ttery into issue-10-secure-top-level
    anssiko committed Sep 24, 2019
    Configuration menu
    Copy the full SHA
    e500e98 View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    6d2ce77 View commit details
    Browse the repository at this point in the history