This repository has been archived by the owner on Jul 30, 2019. It is now read-only.
CSP: Reference. #191
Assignees
Milestone
Comments
|
Looks like the latest in specref is [[!CSP3]] which is the latest published WD of CSP3, and includes a link to the ED on GitHub. Should work as upgraded ref :) |
|
(Sorry, was wrong about the ED reference...) |
arronei
pushed a commit
that referenced
this issue
May 16, 2016
…ATWG (#387) * CSP integrations for Issue #201 Had to adapt "resulting URL record" -> "resulting parsed URL" (will fix with changes to 2.5.2 eventually) * Update refs to CSP3 (from CSP1 Note) for Issue #191 Also fix typo 'teh' * Groundwork for realms #190 and scripting updates #165, #189 Importing dependent changes since last sync of WHATWG in mid-Jan. Added JS-related terms * intermediate: translated definitions in scripting section * Imports 3 fetch script algorithms and reorders a few sections to match WHATWG * add algorithms for script creation * WIP: Syncing changes through event handler section * webappapi include mostly synced. script element section remains * syncing changes for the script element * pulling in more required sections for linking issues * Further reducing linking issues * fixes more linking issues * Finally builds CLEAN! * Adding some missing CSP changes * Adding a few more CSP dependencies * All CSP changes validated and builds clean * Removed script modules * tables in DTs don't render nicely; also fixed backtick use in a few places * Fixes for @arronei's PR feedback
arronei
pushed a commit
that referenced
this issue
Jun 17, 2016
* CSP integrations for Issue #201 Had to adapt "resulting URL record" -> "resulting parsed URL" (will fix with changes to 2.5.2 eventually) * Update refs to CSP3 (from CSP1 Note) for Issue #191 Also fix typo 'teh' * Groundwork for realms #190 and scripting updates #165, #189 Importing dependent changes since last sync of WHATWG in mid-Jan. Added JS-related terms * intermediate: translated definitions in scripting section * Imports 3 fetch script algorithms and reorders a few sections to match WHATWG * add algorithms for script creation * WIP: Syncing changes through event handler section * webappapi include mostly synced. script element section remains * syncing changes for the script element * pulling in more required sections for linking issues * Further reducing linking issues * fixes more linking issues * Finally builds CLEAN! * Adding some missing CSP changes * Adding a few more CSP dependencies * All CSP changes validated and builds clean * removing tables from dt elements for readability * Fix a minor bad merge issue
arronei
pushed a commit
to arronei/html
that referenced
this issue
Apr 17, 2017
* CSP integrations for Issue w3c#201 Had to adapt "resulting URL record" -> "resulting parsed URL" (will fix with changes to 2.5.2 eventually) * Update refs to CSP3 (from CSP1 Note) for Issue w3c#191 Also fix typo 'teh' * Groundwork for realms w3c#190 and scripting updates w3c#165, w3c#189 Importing dependent changes since last sync of WHATWG in mid-Jan. Added JS-related terms * intermediate: translated definitions in scripting section * Imports 3 fetch script algorithms and reorders a few sections to match WHATWG * add algorithms for script creation * WIP: Syncing changes through event handler section * webappapi include mostly synced. script element section remains * syncing changes for the script element * pulling in more required sections for linking issues * Further reducing linking issues * fixes more linking issues * Finally builds CLEAN! * Adding some missing CSP changes * Adding a few more CSP dependencies * All CSP changes validated and builds clean * removing tables from dt elements for readability * Fix a minor bad merge issue
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Since you're pulling in algorithms from CSP, it ought to be a normative, not informative reference. Also, it would be preferable to refer to https://w3c.github.io/webapsec-csp/ rather than the (very old) CSP1 NOTE.
The text was updated successfully, but these errors were encountered: