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

What’s the point of allowing the accept-charset attribute in the sanitization filter ? #218

Closed
ytrezq opened this issue Sep 9, 2015 · 4 comments

Comments

@ytrezq
Copy link

ytrezq commented Sep 9, 2015

Isn’t theaccept-charsetattribute only used with theformelement which is not allowed ?
The same apply for themethodattribute.

There is also the point of allowing theusemapattribute without the map element.

@ytrezq ytrezq changed the title What’s the point of allowing the accept-charset attribute What’s the point of allowing the accept-charset attribute in the sanitization filter ? Sep 9, 2015
@gjtorikian
Copy link
Owner

accept-charset is used for more than just forms.

@ytrezq
Copy link
Author

ytrezq commented Feb 16, 2021

@gjtorikian what about usemap?

@gjtorikian
Copy link
Owner

Seems sane enough to include in v3.

@gjtorikian
Copy link
Owner

A new (beta) release of HTML-Proofer has been released, v3.0.0.pre1. I tried to go back and address all the issues in this repo. For this specific issue, I've opted to keep the sanitization process the same. However, downstream consumers can easily make any change they want to the sanitization process; see the updated README for more information.

Repository owner locked as resolved and limited conversation to collaborators Dec 30, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants