-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Snapshot the allowpaymentrequest attribute #2195
Conversation
Tests: web-platform-tests/wpt#4369 |
cc @rsolomakhin |
<p>Otherwise, follow these substeps:</p> | ||
|
||
<ol> | ||
<li><p>If <var>document</var> has the <var><var>allowattribute</var> flag</var> set, and |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The nested var
here is maybe a bit unclear? Any ideas? Adding "«" and "»" before/after with CSS helps I think...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wasn't it <var>allow<var>attribute</var> flag</var>
elsewhere? That was reasonbly clear I thought.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess I was misremembering. Some CSS solution is probably good; not sure I'd use those quotes though since we use them to denote Infra lists.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@@ -28485,7 +28485,9 @@ interface <dfn>HTMLIFrameElement</dfn> : <span>HTMLElement</span> { | |||
has a <span>nested browsing context</span>, the user agent must <span data-x="parse a sandboxing | |||
directive">parse the sandboxing directive</span> using the attribute's value as the | |||
<var>input</var> and the <code>iframe</code> element's <span>nested browsing context</span>'s | |||
<span><code>iframe</code> sandboxing flag set</span> as the output.</p> | |||
<span><code>iframe</code> sandboxing flag set</span> as the output. If the <code>iframe</code> has | |||
an <code data-x="attr-iframe-allowpaymentrequest">allowpaymentrequest</code> attribute, then set |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, I put this here because it was here in 9f6b91c but this doesn't make sense. It needs to be in https://html.spec.whatwg.org/#initialise-the-document-object I think.
edit: and https://html.spec.whatwg.org/#creating-a-new-browsing-context
I saw someone mention that |
OK, done. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM assuming that @domenic is happy with the nested var
.
I was about to land this using
as commit message however I noticed that the commit is no longer accurate. |
possible this behavior will go away for the <code | ||
data-x="attr-iframe-allowfullscreen">allowfullscreen</code> and <code | ||
data-x="attr-iframe-allowusermedia">allowusermedia</code> attributes as well, see <a | ||
href="https://github.com/whatwg/html/issues/2143#issuecomment-265514585">issue 2143</a>.</p> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should remove allowusermedia from this message. I'll add a commit.
Thanks Anne. This is good to go now with your added commit? |
Yeah, I didn't land it since I figured someone should review my change. |
New
allow*
attributes should use the snapshot model used by<iframe sandbox>
and Feature Policy. The
allowfullscreen
andallowusermedia
attributes areleft with their current live behavior in this change, because it is not yet
clear if it is Web-compatible to change them (see #2187).
Part of #2143.