As a user of the NoScript addon for Firefox, I selectively allow scripts to run. You do a great job at notifying the user that JavaScript is required to use the contact form. However, if I choose to allow https://act.eff.org/ within NoScript and then try to submit the form, this notification about JavaScript being needed disappears. However, https://congressforms.eff.org/ is loaded after customizing my message and clicking the button.
This script is not shown at the outset for the user to know that they need to allow it to proceed. Also, the text box disappears so there is no way to recover any message customizations. The page needs to be reloaded for the new NoScript settings to take effect.
I am not sure if this is something you want to spend time on on (I'm not sure how many people use NoScript), but I would recommend checking that the necessary scripts are all loaded before allowing the user to move on. The same issue could probably happen if there was a network error in loading the second script too. Otherwise, you could include the https://congressforms.eff.org/ script at page load time so there is a NoScript menu option to allow it.
As a user of the NoScript addon for Firefox, I selectively allow scripts to run. You do a great job at notifying the user that JavaScript is required to use the contact form. However, if I choose to allow https://act.eff.org/ within NoScript and then try to submit the form, this notification about JavaScript being needed disappears. However, https://congressforms.eff.org/ is loaded after customizing my message and clicking the button.
This script is not shown at the outset for the user to know that they need to allow it to proceed. Also, the text box disappears so there is no way to recover any message customizations. The page needs to be reloaded for the new NoScript settings to take effect.
I am not sure if this is something you want to spend time on on (I'm not sure how many people use NoScript), but I would recommend checking that the necessary scripts are all loaded before allowing the user to move on. The same issue could probably happen if there was a network error in loading the second script too. Otherwise, you could include the https://congressforms.eff.org/ script at page load time so there is a NoScript menu option to allow it.