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.

Sign up for GitHub

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

Jump to bottom

Snapshot sandbox at start of navigation. #5098

Merged
merged 3 commits into from Nov 25, 2019
Merged

Snapshot sandbox at start of navigation. #5098

merged 3 commits into from Nov 25, 2019

Commits on Nov 18, 2019

  1. Snapshot sandbox at start of navigation. 

    This change fixes a race condition where an iframe's sandboxing flag set could
be changed in between the start of a navigation and when the response is
returned, and the new document created. In that case, it was unclear how
the new document could reliably synchronously get the updated flags, or
just exactly how late those flags could be changed and still impact the
new document. Now, the sandboxing flag set is routed from the beginning of the
navigation to the eventual document creation.

Ref: whatwg#4783, and also see
w3c/webappsec-permissions-policy#256
    @clelland
    clelland committed Nov 18, 2019
    Configuration menu
    Copy the full SHA
    a8cc209 View commit details
    Browse the repository at this point in the history

Commits on Nov 20, 2019

  1. Remove unused arg from "Determine active sandboxing flags"

    @clelland
    clelland committed Nov 20, 2019
    Configuration menu
    Copy the full SHA
    ad77f73 View commit details
    Browse the repository at this point in the history

  2. Rename determine sandbox flags algorithm

    @clelland
    clelland committed Nov 20, 2019
    Configuration menu
    Copy the full SHA
    742ee8d View commit details
    Browse the repository at this point in the history