Skip to content
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

Suggest use of origin in warning text (Fixes #429) #430

Merged
merged 2 commits into from
Feb 11, 2019

Conversation

mozfreddyb
Copy link
Contributor

@mozfreddyb mozfreddyb commented Feb 8, 2019

This is my first attempt at fixing #429.


Preview | Diff

@mozfreddyb mozfreddyb closed this Feb 8, 2019
@mozfreddyb mozfreddyb reopened this Feb 8, 2019
url.bs Outdated
<a>same site</a>. HTML's <a>same origin-domain</a> concept is a reasonable example of this
consideration in practice.
<p class=warning>Specifications should prefer the <a for=/>origin</a> concept for security
decisions. The notion of "<a for=host>public suffix</a>","<a for=host>registrable domain</a>",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

space after the comma

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed, thanks!

@annevk annevk merged commit 0c6e51d into whatwg:master Feb 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants