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
The validator throws the following error when a share link for Threema, an alternativ to WhatsApp, is used on a page:
Invalid URL protocol 'threema:' for attribute 'href' in tag 'a'.
Since "whatsapp:" is allowed, "threema:" should be considered valid as well. After all, it is basically the same thing.
The issue can be reproduced by simply testing the following two links in the validator:
<a href="whatsapp://send?text=https%3A%2F%2Fvalidator.ampproject.org">AMP Validator</a>
<a href="threema://compose?text=https%3A%2F%2Fvalidator.ampproject.org">AMP Validator</a>
The whatsapp: link is fine, the threema: link is throwing the mentioned protocol error.
Cheers, JP
The text was updated successfully, but these errors were encountered:
@honeybadgerdontcare, can you add this protocol to our url lists where appropriate?
Sorry, something went wrong.
Resolved. This will be deployed to cdn.ampproject.org next week.
This change is now live on cdn.ampproject.org
Confirmed. Thank you very much!
honeybadgerdontcare
No branches or pull requests
The validator throws the following error when a share link for Threema, an alternativ to WhatsApp, is used on a page:
Since "whatsapp:" is allowed, "threema:" should be considered valid as well. After all, it is basically the same thing.
The issue can be reproduced by simply testing the following two links in the validator:
<a href="whatsapp://send?text=https%3A%2F%2Fvalidator.ampproject.org">AMP Validator</a>
<a href="threema://compose?text=https%3A%2F%2Fvalidator.ampproject.org">AMP Validator</a>
The whatsapp: link is fine, the threema: link is throwing the mentioned protocol error.
Cheers,
JP
The text was updated successfully, but these errors were encountered: