-
Notifications
You must be signed in to change notification settings - Fork 549
Conversation
pointing out that use in the body can trigger unwanted side effects. See Issue w3c#544.
that this needs for completeness (attribute defs, IDL, etc.)
<a>removed from the document</a>, or existing <code>meta</code> elements have their <code>name</code> | ||
or <code>content</code> attributes changed, user agents must run the following algorithm: | ||
|
||
<ol> |
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.
Could use the short hand ol list syntax.
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 have 2 comments but only the link wrapping one is necessary to correct. Once that is corrected anyone can merge this. The rest of this is fine.
@@ -963,6 +974,75 @@ | |||
inappropriate keywords. | |||
</p> | |||
|
|||
: <dfn><code>referrer</code></dfn> | |||
|
|||
:: The value must be a <a>referrer policy</a>, which defines the default <a>referrer |
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.
Wrapping a link is bad. Could you fix this one link so we don't line break in the middle of an link element.
Fixes for review are in d9217b6 - could someone check and merge please? |
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.
OK, this seems good to go now - thanks.
Alex seems to have made the change requested
Changes for Issue #560 plus some manual diffs for referrerpolicy at various places in the spec. that weren't obvious from the issue.