Skip to content

Conversation

@foolip
Copy link
Member

@foolip foolip commented Jan 28, 2016

The spec as a whole is written in en-GB-x-hixie, but this is the name of
an algorithm, similar to InitializeHostDefinedRealm, so do not use
data-x="..." to change the spelling in the prose.

The "Initialize a global object's CSP list" algorithm is actually
unused.

Part of #573

@foolip
Copy link
Member Author

foolip commented Jan 28, 2016

@mikewest, can you PTAL? Is it a bug that "Initialize a global object's CSP list" is not used by HTML?

@foolip
Copy link
Member Author

foolip commented Jan 28, 2016

@Hixie, I see that you have added lang="en-US" in a few places that use US spelling, like "DOM Parsing and Serialization". Is that part of some tooling you have for checking that the document consistently uses Hixie-English, or just because it's true?

@mikewest
Copy link
Member

Hrm. Initialize a global object's CSP list should be used when running a worker. I think we need to replace step ~16 of "Run a worker" (https://html.spec.whatwg.org/#run-a-worker) with something like "Execute the Initialize a global object's CSP list on |worker global scope| and |response|."

Would you like to do that in this patch, or shall I put something together separately?

@foolip
Copy link
Member Author

foolip commented Jan 29, 2016

I'd like to limit this patch to fixing link issues, so please go ahead and do that separately, sounds like you know exactly what's needed.

@foolip
Copy link
Member Author

foolip commented Jan 29, 2016

Gave you an issue so that I can reference it in my commit message.

The spec as a whole is written in en-GB-x-hixie, but this is the name of
an algorithm, similar to InitializeHostDefinedRealm, so do not use
data-x="..." to change the spelling in the prose.

Part of #573
@sideshowbarker
Copy link
Member

LGTM. (Sorry for delay, was away for most of the evening til now…)

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.

4 participants