Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Disabled controls <em>shouldn't</em> actually be submitted with the form, so what you're seeing is in fact normal behaviour. According to the <a href="http://www.w3.org/TR/html4/interact/forms.html#h-17.12" rel="noreferrer">HTML form specification</a>:</p> <blockquote> <p>When set, the disabled attribute has the following effects on an element:</p> <ul> <li>Disabled controls do not receive focus.</li> <li>Disabled controls are skipped in tabbing navigation.</li> <li><em>Disabled controls cannot be successful.</em></li> </ul> </blockquote> <p>The definition of <code>successful</code> can be found <a href="http://www.w3.org/TR/html4/interact/forms.html#successful-controls" rel="noreferrer">in the same document</a>. It's a bit nonsensical to suggest that Play is broken because of this.</p> <p>If you want to have a form field that user cannot edit while it should still be sent along when the form is submitted, you can use the <a href="http://www.w3.org/TR/html4/interact/forms.html#h-17.12.2" rel="noreferrer">read-only</a> attribute, or use JavaScript to disallow user input.</p> <p><strong>Update:</strong> as pointed out in the comments, the following points may also offer a solution:</p> <ul> <li>It's possible that Play still keeps the disabled control's form values in the request object, and just doesn't bind them (so you could retrieve them from the request if needed)</li> <li>Use a hidden field to keep the form value in case you still want to submit the value, but do not want the user(s) to see the control</li> </ul>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload