Make the appending of the URL fragment (the one that identifies & anchors to the contact form element: e.g. #zcr1234567abcdefg) to the form action attribute optional, as it may affect the functionality of the redirect option.
How does the appending of the URL fragment to the action attribute affect the redirect functionality?
After submitting the form, when the destination URL also has the contact form rendered (for example, in a site-wide contact form present in the site footer), the user gets scrolled down to the form again, instead of being presented with whatever is in the redirect URL (usually, a “thank you” message and maybe some call to actions).
I’d say that it might be safe to make them mutually exclusive: if the redirect option is used, it seems undesirable/unnecessary to have the URL fragment appended to the action attribute.
Make the appending of the URL fragment (the one that identifies & anchors to the contact form element: e.g.
#zcr1234567abcdefg) to the formactionattribute optional, as it may affect the functionality of theredirectoption.How does the appending of the URL fragment to the action attribute affect the redirect functionality?
After submitting the form, when the destination URL also has the contact form rendered (for example, in a site-wide contact form present in the site footer), the user gets scrolled down to the form again, instead of being presented with whatever is in the
redirectURL (usually, a “thank you” message and maybe some call to actions).I’d say that it might be safe to make them mutually exclusive: if the
redirectoption is used, it seems undesirable/unnecessary to have the URL fragment appended to theactionattribute.