Permalink
Browse files

port Upstream `plugin-types` hooks from CSP3

refer to #547
  • Loading branch information...
stevefaulkner committed Nov 17, 2016
1 parent fdb3cbc commit d8d548111835d6042d46585d0d8c43b14f5e261a
Showing with 7 additions and 2 deletions.
  1. +2 −0 sections/infrastructure.include
  2. +2 −0 sections/obsolete.include
  3. +3 −2 sections/semantics-embedded-content.include
@@ -1339,6 +1339,8 @@
<a><code>sandbox</code></a> <a>directives</a>
* The <a>EnsureCSPDoesNotBlockStringCompilation</a> abstract algorithm
* The <a>Is base allowed for Document?</a> algorithm
* The <a>Should element be blocked <i lang="li">a priori</i> by Content Security Policy?</a> algorithm
:: The following terms are defined in <cite>Content Security Policy: Document Features</code> <!-- [[!CSPDOCUMENT]] when published -->
* The <a><code>frame-ancestors</code> directive</a>
@@ -419,6 +419,8 @@
<a>fallback content</a>.
* No Java Language runtime <a>plugin</a> is available.
* A Java runtime <a>plugin</a> is available but it is disabled.
* The <a>Should element be blocked <i lang="li">a priori</i> by Content Security Policy?</a>
algorithm returns "Blocked" when executed on the element. [[!CSP3]]
Otherwise, the user agent should instantiate a Java Language runtime <a>plugin</a>, and should
pass the names and values of all the attributes on the element, in the order they were added to
@@ -4463,8 +4463,9 @@ attribute's value is a type that a <a>plugin</a> supports, then the value of the
if the element is not <a>in a <code>Document</code></a> with a
<a>browsing context</a>, or if the element's <a>node document</a> is not <a>fully
active</a>, or if the element is still in the <a>stack of open elements</a> of an
<a>HTML parser</a> or <a>XML parser</a>, or if the element is not <a>being
rendered</a>, then jump to the step below labeled <i>fallback</i>.
<a>HTML parser</a> or <a>XML parser</a>, or if the element is not <a>being rendered</a>, or if the
<a>Should element be blocked <i lang="li">a priori</i> by Content Security Policy?</a> algorithm
returns "Blocked" when executed on the element, then jump to the step below labeled fallback. [[!CSP3]].
</li>

5 comments on commit d8d5481

@stevefaulkner

This comment has been minimized.

Show comment
Hide comment
@stevefaulkner

stevefaulkner Nov 17, 2016

Contributor

when building locally got: LINK ERROR: No 'dfn' refs found for 'should element be blocked a priori by content security policy?' that are marked for export. which suggests the anchors.data file needs updating, but unsure how? ping @travisleithead @arronei @adanilo

Contributor

stevefaulkner replied Nov 17, 2016

when building locally got: LINK ERROR: No 'dfn' refs found for 'should element be blocked a priori by content security policy?' that are marked for export. which suggests the anchors.data file needs updating, but unsure how? ping @travisleithead @arronei @adanilo

@stevefaulkner

This comment has been minimized.

Show comment
Hide comment
@stevefaulkner

stevefaulkner Nov 17, 2016

Contributor

So i found the ref in anchors.data, the word "plugin" was missing in the spec commit, so i added, but made no difference, still got linking error.

Contributor

stevefaulkner replied Nov 17, 2016

So i found the ref in anchors.data, the word "plugin" was missing in the spec commit, so i added, but made no difference, still got linking error.

@chaals

This comment has been minimized.

Show comment
Hide comment
@chaals

chaals Nov 17, 2016

Collaborator

@stevefaulkner what if you remove the markup in the link?

Collaborator

chaals replied Nov 17, 2016

@stevefaulkner what if you remove the markup in the link?

@travisleithead

This comment has been minimized.

Show comment
Hide comment
@travisleithead

travisleithead Nov 29, 2016

Member

Our master branch is not compatible with the latest Bikeshed, see: #726. The PR to fix this is not closed yet.

Member

travisleithead replied Nov 29, 2016

Our master branch is not compatible with the latest Bikeshed, see: #726. The PR to fix this is not closed yet.

@travisleithead

This comment has been minimized.

Show comment
Hide comment
@travisleithead

travisleithead Nov 29, 2016

Member

(Not sure if this is the same issue, but without looking deeply it just occurred to me to check.) To verify, follow the new building instructions in the README.md at https://github.com/w3c/html/tree/html5.1

Member

travisleithead replied Nov 29, 2016

(Not sure if this is the same issue, but without looking deeply it just occurred to me to check.) To verify, follow the new building instructions in the README.md at https://github.com/w3c/html/tree/html5.1

Please sign in to comment.