The registration form features a critical validation flaw where standard email domains (such as .com) are not properly validated or accepted. Additionally, the Terms of Service section is cumbersome and counterintuitive for users to read and accept
Issue Description
During the account creation and credential setup process:
Email Domain Validation Failure: The system throws errors or rejects legitimate email addresses utilizing standard top-level domains like .com, blocking the user from proceeding.
Cumbersome Terms of Service UX: The layout, reading mechanism, and acceptance flow for the Terms of Service are awkward and difficult to navigate, causing unnecessary friction in the registration workflow.
Preconditions
The user is on the account credentials and terms acceptance screen[span_4].
The email input field and Terms of Service checkbox elements are active.
Steps to Reproduce
Navigate to the registration step requiring email input and terms agreement.
Enter a valid email address ending in .com (e.g., user@domain.com).
Observe that the system triggers a validation error or rejects the correct format.
Attempt to review and interact with the Terms of Service block for acceptance, experiencing an unresponsive or cumbersome interface.
Expected Result
The system must correctly validate standard email domain extensions (including .com, .net, etc.) smoothly without generating false-positive validation errors.
The Terms of Service review and acceptance mechanism should be redesigned (e.g., via a clean modal popup, a scrollable document link, or a concise summary) to prevent a clunky user experience.
Actual Result
The email validator fails to process standard domains like .com properly.
Reviewing and accepting the Terms of Service is inconvenient, confusing, and impractical.
Evidence
Email/Credentials Field: Generates errors when attempting to process standard emails with .com.
Terms Section: "Términos de servicio" block layout features checkboxes and buttons that impede a smooth reading flow for the user.
Impact
Registration Block: Users cannot sign up using legitimate and widespread email addresses.
UX Friction: Cumbersome terms-reading flows increase form abandonment rates.
Frequency
Always
Reproducibility
100%
Notes & Recommendations
Update the Regular Expression (Regex) for the email field on both client and server sides to ensure proper support for global TLDs (.com, .org, .net, etc.).
Implement a user-friendly modal window or a clean accordion view for the Terms of Service, allowing quick review and a direct, frictionless acceptance checkbox.
## Summary
The registration form features a critical validation flaw where standard email domains (such as .com) are not properly validated or accepted. Additionally, the Terms of Service section is cumbersome and counterintuitive for users to read and accept
## Issue Description
During the account creation and credential setup process:
1. *Email Domain Validation Failure:* The system throws errors or rejects legitimate email addresses utilizing standard top-level domains like .com, blocking the user from proceeding.
2. *Cumbersome Terms of Service UX:* The layout, reading mechanism, and acceptance flow for the Terms of Service are awkward and difficult to navigate, causing unnecessary friction in the registration workflow.
## Preconditions
- The user is on the account credentials and terms acceptance screen[span_4].
- The email input field and Terms of Service checkbox elements are active.
## Steps to Reproduce
1. Navigate to the registration step requiring email input and terms agreement.
2. Enter a valid email address ending in .com (e.g., user@domain.com).
3. Observe that the system triggers a validation error or rejects the correct format.
4. Attempt to review and interact with the Terms of Service block for acceptance, experiencing an unresponsive or cumbersome interface.
## Expected Result
- The system must correctly validate standard email domain extensions (including .com, .net, etc.) smoothly without generating false-positive validation errors.
- The Terms of Service review and acceptance mechanism should be redesigned (e.g., via a clean modal popup, a scrollable document link, or a concise summary) to prevent a clunky user experience.
## Actual Result
- The email validator fails to process standard domains like .com properly.
- Reviewing and accepting the Terms of Service is inconvenient, confusing, and impractical.
## Evidence
- *Email/Credentials Field:* Generates errors when attempting to process standard emails with .com.
- *Terms Section:* "Términos de servicio" block layout features checkboxes and buttons that impede a smooth reading flow for the user.
## Impact
- *Registration Block:* Users cannot sign up using legitimate and widespread email addresses.
- *UX Friction:* Cumbersome terms-reading flows increase form abandonment rates.
## Frequency
Always
## Reproducibility
100%
## Notes & Recommendations
- Update the Regular Expression (Regex) for the email field on both client and server sides to ensure proper support for global TLDs (.com, .org, .net, etc.).
- Implement a user-friendly modal window or a clean accordion view for the Terms of Service, allowing quick review and a direct, frictionless acceptance checkbox.
enjin2310
changed title from # [Bug] Email Domain Validation Failure (Excludes Common TLDs like .com) and Poor Terms of Service UX to # [Bug] [Medium] Email Domain Validation Failure (Excludes Common TLDs like .com) and Poor Terms of Service UX2026-11-01 05:05:59 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
The registration form features a critical validation flaw where standard email domains (such as .com) are not properly validated or accepted. Additionally, the Terms of Service section is cumbersome and counterintuitive for users to read and accept
Issue Description
During the account creation and credential setup process:
Preconditions
Steps to Reproduce
Expected Result
Actual Result
Evidence
Impact
Frequency
Always
Reproducibility
100%
Notes & Recommendations
# [Bug] Email Domain Validation Failure (Excludes Common TLDs like .com) and Poor Terms of Service UXto # [Bug] [Medium] Email Domain Validation Failure (Excludes Common TLDs like .com) and Poor Terms of Service UX