We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm using imgsrc to support high-resolution display images: https://webkit.org/demos/srcset/
<img src="image.jpg" srcset="image-1x.jpg 1x, image-2x.jpg 2x, image-3x.jpg 3x">
Your XSS strips this down to
<img src="image.jpg">
It just gets rid of the srcset. Why, and if srcset isn't really dangerous, can you consider whitelisting it?
srcset
The text was updated successfully, but these errors were encountered:
This is easy to add: I pushed a srcset branch.
However, this attribute is not in my reference implementation: https://github.com/html5lib/html5lib-python/blob/master/html5lib/filters/sanitizer.py A goal of this library is to have 3rd-party vetting of the safety of the sanitization.
Sorry, something went wrong.
ok, that implementation is stalled. srcset looks like it can be treated just like src
Successfully merging a pull request may close this issue.
I'm using imgsrc to support high-resolution display images: https://webkit.org/demos/srcset/
Your XSS strips this down to
It just gets rid of the
srcset
. Why, and ifsrcset
isn't really dangerous, can you consider whitelisting it?The text was updated successfully, but these errors were encountered: