From e0863d93ec8c0b48f1c44d8d81a409eb08dee28c Mon Sep 17 00:00:00 2001 From: Mike West Date: Thu, 14 Apr 2016 15:55:19 +0200 Subject: [PATCH] Add a source argument to CSP's inline behavior algorithm To support hash-based whitelisting of inline event handlers, CSP has added a _source_ argument to the "Should _element_'s inline behavior be blocked by Content Security Policy?" (in w3c/webappsec#13). This patch adds the same argument to the four callsites in HTML. --- source | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/source b/source index 69e26ae285a..24f8974201e 100644 --- a/source +++ b/source @@ -11343,9 +11343,9 @@ Transport Protocol">HTTP</abbr> today.</p>
  • If the Should element's inline behavior be blocked by Content Security Policy? algorithm returns "Blocked" when executed upon the - style element and "style", then abort these steps. -

  • + style element, "style", and the style + element's style data, then abort these steps.

    @@ -58629,9 +58629,9 @@ o............A....e
  • If the script element does not have a src content attribute, and the Should element's inline behavior be blocked by Content Security Policy? algorithm returns "Blocked" when executed upon the script element and "script", then abort these steps. The script is not executed.

  • + data-x="">Blocked" when executed upon the script element, "script", and the script element's child text content, + then abort these steps. The script is not executed.

  • @@ -88425,8 +88425,8 @@ dictionary PromiseRejectionEventInit : EventInit {
    1. If the Should element's inline behavior be blocked by Content Security Policy? algorithm returns "Blocked" when executed upon the - attribute's element and "script attribute", then abort these - steps.

    2. + attribute's element, "script attribute", and the attribute's + value, then abort these steps.

    3. Set the corresponding event handler to an internal raw uncompiled handler consisting of the attribute's new value and the