This repository has been archived by the owner on Mar 30, 2021. It is now read-only.
Add referrerpolicy
to <layer>
's content attributes
#26
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #23.
@prushforth does this look good to you?
I noticed the way the IDL attributes are defined is different from e.g. how WHATWG HTML does it for iframe: https://html.spec.whatwg.org/multipage/iframe-embed-object.html#the-iframe-element:dom-iframe-referrerpolicy - the IDL attributes have links to definitions of how they reflect a particular content attribute.
I dug into this a bit and I found that the HTML Portals spec got a request to separate src IDL and content attributes.
But changing that now to include explicit definitions of each IDL attribute separate from content attributes means we should probably do that for everything, and that's perhaps something we can do later as part of (or after) the merge of this spec into MapML? This way we can just get the attribute in this spec for now...?