Answers.Body: <p>We've recently discovered that this feature is not always reliable unfortunately. However, we're working on addressing this and coming up with a better solution in the coming weeks. Sorry for any inconvenience.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-11-16T16:56:52.267Z
Answers.LastActivityDate: 2017-11-16T16:56:52.267Z
Answers.UserDisplayName: Solspace
Body: <p>I'm using Freeform 1.7.2 and since version 1.6.2 a form anchor is automatically added:</p>
  
  <blockquote>
    <p>Added form anchor to be automatically generated so inline error returns can focus down to form, if it's lower down on page.</p>
  </blockquote>
  
  <p>Yet, the submission still jumps to the top of the page if there is an error. I asked a similar question before, but this was before the name anchor was added. Shouldn't this now work by itself?</p>
  
  <p>Here's my super simple code:</p>
  
  <pre><code>{{ craft.freeform.form("formName", {
     instructionsBelowField: true,
     useRequiredAttribute: true,
  }).render() }}
  </code></pre>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-11-16T14:04:58.297Z
Comments.Text: Unless you provide a little bit more information for us (what works, what does not work, how it is supposed to work eg via URL param or route param/Javascript or whatever, are there any console errors) it would be more useful to contact the creator of the plugin.
Comments.UserDisplayName: Robin Schambach
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-11-16T16:01:34.303Z
Comments.Text: I know Robin, but this is the way Solspace advices me to ask for support. But I'll ask them directly and post the answer here then.
Comments.UserDisplayName: noregt
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-11-16T17:00:20.150Z
Comments.Text: Just to clarify, we encourage the Craft Stack Exchange for how-to type questions. If you believe you are encountering a bug, you can of course use our Support Request ticket system. :)
Comments.UserDisplayName: Solspace
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-11-16T17:01:34.530Z
Comments.Text: Okay, I wasn't sure if this was a bug, but apparently it is.
Comments.UserDisplayName: noregt
Tags: <plugin-freeform><solspace>
Title: Error reporting Freeform submission jumps to top of page despite auto form anchor
ThreadText: # Error reporting Freeform submission jumps to top of page despite auto form anchor
  
  (Asked by: username_0 on 2017-11-15)
  
  I'm using Freeform 1.7.2 and since version 1.6.2 a form anchor is automatically added:
  
  > Added form anchor to be automatically generated so inline error returns can focus down to form, if it's lower down on page.
  
  Yet, the submission still jumps to the top of the page if there is an error. I asked a similar question before, but this was before the name anchor was added. Shouldn't this now work by itself?
  
  Here's my super simple code:
  
  ```
  {{ craft.freeform.form("formName", {
     instructionsBelowField: true,
     useRequiredAttribute: true,
  }).render() }}
  
  ```
  
  **Tags:** plugin-freeform, solspace
  
  > **Comments:**
  > **username_1**: Unless you provide a little bit more information for us (what works, what does not work, how it is supposed to work eg via URL param or route param/Javascript or whatever, are there any console errors) it would be more useful to contact the creator of the plugin.  
  > **username_0**: I know username_1, but this is the way username_2 advices me to ask for support. But I'll ask them directly and post the answer here then.  
  > **username_2**: Just to clarify, we encourage the Craft Stack Exchange for how-to type questions. If you believe you are encountering a bug, you can of course use our Support Request ticket system. :)  
  > **username_0**: Okay, I wasn't sure if this was a bug, but apparently it is.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2017-11-16. Score: 2 | Accepted answer
  
  We've recently discovered that this feature is not always reliable unfortunately. However, we're working on addressing this and coming up with a better solution in the coming weeks. Sorry for any inconvenience.
  
  
  ---
  
  