Include guidelines for textareas #301
Comments
|
There are visual examples of textareas here: http://govuk-elements.herokuapp.com/form-elements/example-form-elements/ Our recommendation would be to ensure that the textarea is sized according to the response required - so rather than make these a default recommended height - they can vary in height to best fit the response. I'll ensure this guidance is added to the main form elements page, thanks for suggesting it. |
|
Fab, thanks for getting back to me so quickly! I must have missed that page |
gemmaleigh
added a commit
that referenced
this issue
Oct 11, 2016
# 4.14.1 - Fix tabular number sizing in Firefox ([PR #301](alphagov/govuk_frontend_toolkit#301)) # 4.14.0 - Allow use of multiple GA customDimensionIndex. See [this section](https://github.com/alphagov/govuk_frontend_toolkit/blob/master/ docs/javascript.md#using-google-custom-dimensions-with-your-own-statisti cal-model) of the documentation for more information. - Configurable duration (in days) for AB Test cookie. See [this section](https://github.com/alphagov/govuk_frontend_toolkit/blob/master/ docs/javascript.md#multivariate-test-framework) of the documentation for more information. - Allow base scripts to run within a module loader. See [this PR](alphagov/govuk_frontend_toolkit#290) for more information.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There are no visual examples of textareas on http://govuk-elements.herokuapp.com/form-elements/. As a result different services have included their own custom textarea styles for width and height resulting in inconsistencies across applications.
A standard textarea with class
form-controlinherits the 50% width desktop, 100% width mobile as per text inputs, but they seem to only be high enough to show 2 linesThe text was updated successfully, but these errors were encountered: