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

mailto URIs with multiple recipients not accepted #233

Open
Qup42 opened this issue Apr 8, 2024 · 0 comments · May be fixed by #234
Open

mailto URIs with multiple recipients not accepted #233

Qup42 opened this issue Apr 8, 2024 · 0 comments · May be fixed by #234
Labels

Comments

@Qup42
Copy link

Qup42 commented Apr 8, 2024

Describe the bug

The standard for the mailto schema (RFC6068) allows multiple recipients that are separated by ,. One example ismailto:foo@example.com,bar@example.com. Such links that contain multiple recipients are incorrectly flagged as invalid by htmltest.

To Reproduce

Steps to reproduce the behaviour:

  1. Run with empty config on index.html: htmltest index.html
  2. See error

.htmltest.yml (empty)

index.html

<!DOCTYPE html>
<html>
   <head></head>
   <body>
      <a href="mailto:foo@example.com,bar@example.com"></a>
   </body>
</html>

Expected behaviour

mailto:foo@example.com,bar@exmple.com is a valid mailto URI as per RFC6068. No error or warning should be raised by htmltest.

Actual behaviour

The link is flagged as invalid:

invalid email address (invalid format): 'foo@example.com,bar@example.com' --- index.html --> mailto:foo@example.com,bar@example.com

Versions

  • OS: Arch Linux
  • htmltest: 0.17.0

Additional context

The link is declared as invalid by htmltest because the individual recipients are not split up.
I will try to provide a PR for this Issue. I expect the PR to be of medium size.

@Qup42 Qup42 added the bug label Apr 8, 2024
@Qup42 Qup42 linked a pull request Apr 8, 2024 that will close this issue
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 a pull request may close this issue.

1 participant