[ ] support request => Please do not submit support requests here, instead ask your query in our Gitter channel
Current behavior:
The code does restrict the user if they enter any malicious script code inside the email field of signup.html page
Expected behavior:
The behavior remains same, but provide a stability that it checks the edit field inside the same script(signup.js) rather than going into another script file and checking whether the written email in input field of signup.html is in right regular-language structure of an email.
Steps to reproduce:
Say if we enter some email like soora<html>.com inside the email field of signup.html then the script signup.js doesn't check this explicit behavior rather checked in some other(future) script. This isn't the right behavior one should expect and should be resolved in the script file of the given page itself.
This is implemented inside the script file for login.html page but not for signup.html
Related code:
var email=document.getElementById("email").value;
if(!email){
alert("Email field cannot be empty");
return;
}
I'm submitting a ...
Current behavior:
The code does restrict the user if they enter any malicious script code inside the email field of
signup.htmlpageExpected behavior:
The behavior remains same, but provide a stability that it checks the edit field inside the same script(
signup.js) rather than going into another script file and checking whether the written email in input field ofsignup.htmlis in right regular-language structure of an email.Steps to reproduce:
Say if we enter some email like
soora<html>.cominside the email field ofsignup.htmlthen the scriptsignup.jsdoesn't check this explicit behavior rather checked in some other(future) script. This isn't the right behavior one should expect and should be resolved in the script file of the given page itself.This is implemented inside the script file for
login.htmlpage but not forsignup.htmlRelated code:
Would you like to work on the issue?