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

Optimize/fix form-based email validation #43

Closed
rjgamer opened this Issue Apr 29, 2018 · 1 comment

Comments

Projects
1 participant
@rjgamer
Contributor

rjgamer commented Apr 29, 2018

test@test seem to be valid for the form type email (based on HTML5 standards). But for the validator of the framework is the TLD a must.

@rjgamer rjgamer self-assigned this Apr 29, 2018

@rjgamer rjgamer added the bug label Apr 29, 2018

@rjgamer rjgamer changed the title from Optimize form-based email validation to Optimize/fix form-based email validation Apr 29, 2018

@rjgamer rjgamer added this to To do in 1.0.0-a2 via automation Apr 29, 2018

@rjgamer

This comment has been minimized.

Contributor

rjgamer commented Apr 29, 2018

Not fixable without JS-based validations.

To prevent an overhead for code maintenance, nothing will be fixed or implemented (like JS-based validations).

More details about type email and TLDs: https://stackoverflow.com/questions/14373433/how-does-html5-input-type-email-works-without-top-level-domain-name

@rjgamer rjgamer closed this Apr 29, 2018

1.0.0-a2 automation moved this from To do to Done Apr 29, 2018

@rjgamer rjgamer added the wontfix label Apr 29, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment