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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

馃悰 Have purifier.js allow unknown protocols #20710

Merged
merged 5 commits into from Feb 8, 2019

Conversation

delima02
Copy link
Contributor

@delima02 delima02 commented Feb 6, 2019

@choumx

@dreamofabear dreamofabear changed the title Have purifier.js allow unknown protocols. 馃悰 Have purifier.js allow unknown protocols Feb 6, 2019
@dreamofabear
Copy link

Nice work. Can you add a unit test to test-purifier.js please?

@@ -280,6 +280,8 @@ export function purifyConfig() {
FORCE_BODY: true,
// Avoid need for serializing to/from string by returning Node directly.
RETURN_DOM: true,
// BLACKLISTED_ATTR_VALUES are enough. Other unknown protocols are safe.

Choose a reason for hiding this comment

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

Let's also mention that this allows native app deeplinks specifically.

@dreamofabear dreamofabear merged commit d87152d into ampproject:master Feb 8, 2019
nbeloglazov pushed a commit to nbeloglazov/amphtml that referenced this pull request Feb 12, 2019
* Have purifier.js allow unknown protocols.

* Add unit test for allowing arbitrary protocols.

* Add required 'target' attribute to tags in arbitrary protocols test.

* Lint fix for unknown protocols test.
noranazmy pushed a commit to noranazmy/amphtml that referenced this pull request Mar 22, 2019
* Have purifier.js allow unknown protocols.

* Add unit test for allowing arbitrary protocols.

* Add required 'target' attribute to tags in arbitrary protocols test.

* Lint fix for unknown protocols test.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants