Results 1 to 4 of 4

Thread: ExtJS 6.6 Email Validation error for business top-level domain

    Thank you for reporting this bug. We will make it our priority to review this report.
  1. #1
    Sencha Premium Member
    Join Date
    Dec 2010
    Posts
    7

    Default ExtJS 6.6 Email Validation error for business top-level domain

    Run the following fiddle:

    https://fiddle.sencha.com/#fiddle/2q5i&view/editor

    You'll see that the email is marked as invalid even though .business is a valid top-level domain. It seems the email validation is too strict. It expects at most 6 characters for the top-level domain even though there are multiple longer top-level domains now.

    I think if you need to check the maximum length of the TLD it should be 63 which is the maximum length supported by DNS.

  2. #2
    Sencha - Forum Administrator
    Join Date
    Sep 2017
    Posts
    1,006

    Default

    Thank you so much for your post. I apologize for the delay. I have shared this with the support staff to look into at their earliest convenience. Your patience is greatly appreciated! We do suggest using the support portal when you need assistance with a capability of a Sencha product, you have identified a situation where a products behavior is inconsistent with the product documentation and might indicate a software bug, or when the communication between you and Sencha needs to be private.

    Thanks again,

    Michele



  3. #3
    Ext Support Team
    Join Date
    Jan 2018
    Posts
    538

    Default

    Hello Thomas,

    This issue has been reviewed by our Engineering team under Jira EXTJS-22456 and the following inputs were shared:

    1. They didn't think that they could restrict the framework to RFC-validate emails. If you want you can override the validators and apply more strict rules.

    2. You
    can always create your own validation.

    Regards,
    Kumar.

  4. #4
    Sencha MVP Team Member
    Join Date
    Sep 2016
    Location
    Kennewick, WA
    Posts
    147

    Default

    Quote Originally Posted by rakumar View Post
    Hello Thomas,

    This issue has been reviewed by our Engineering team under Jira EXTJS-22456 and the following inputs were shared:

    1. They didn't think that they could restrict the framework to RFC-validate emails. If you want you can override the validators and apply more strict rules.

    2. You
    can always create your own validation.

    Regards,
    Kumar.
    This would still be considered a bug. Per information found the longest TDL is 24 characters while the original poster is correct in they do support up to 63 in DNS... If Ext JS has an email validator it should validate anything up to and including 63 characters. I as a developer using a framework shouldn't have to override validators that validate an email and are provided by the framework I'm using. Especially the case of one I pay for?
    Andy Allord
    Sencha MVP/Software Engineer

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •