@financial-times/o-forms
Advanced tools
This component provides responsive styling for form fields and inputs. It provides validation and error handling for forms, as well.
FT-branded styles for form elements.
Check out how to include Origami components in your project to get started with o-forms.
o-forms has "field" elements which hold an input and information about that input, e.g. its label text. Use unique ids to associate form inputs and their labels. This is required as some assistive technologies do not support implicit labels, such as Dragon Naturally Speaking.
All form fields follow the same structure:
┌— field container (.o-forms-field) —————┐
| (one of div or label) |
| |
| ┌ title container (.o-forms-title) ┐ |
| | (group titles or | |
| | individual input labels) | |
| └——————————————————————————————————┘ |
| |
| ┌ input container (.o-forms-input) ┐ |
| | (group inputs or | |
| | individual inputs) | |
| └——————————————————————————————————┘ |
└————————————————————————————————————————┘
Form fields may support single input fields, such as text or select boxes. Or multiple input fields, such as check boxes or toggles. There are also a number of modifying classes to change the layout or fields, e.g. to show inputs inline with their label, or to visually display an inputs validity.
Single input fields are created with a label element and class o-forms-field. All label copy is wrapped within a child o-forms-title element, and the input itself is wrapped within a child o-forms-input element.
The input and its label copy are associated since they are both within a label element. Association enables a screenreader to read out the label when the user is focused on the input. Association also means clicking the label will focus the input.
The following example shows a text input:
<label for="text" class="o-forms-field">
<span class="o-forms-title">
<span class="o-forms-title__main">Label for input here</span>
</span>
<span class="o-forms-input o-forms-input--text">
<input id="text" type="text" name="text-example">
</span>
</label>
For a different single input, update the input element within o-forms-input and add a matching modifier to the o-forms-input element. E.g. for a textarea input:
<label for="text-example" class="o-forms-field">
<span class="o-forms-title">
<span class="o-forms-title__main">Label for input here</span>
</span>
- <span class="o-forms-input o-forms-input--text">
+ <span class="o-forms-input o-forms-input--textarea">
- <input id="text-example" type="text" name="text-example">
+ <textarea id="text-example" name="text-example"></textarea>
</span>
</label>
To create a text input use a single input field structure, with an o-forms-input--text modifier class on the o-forms-input element and an input type of type="text".
<label for="text-example" class="o-forms-field">
<span class="o-forms-title">
<span class="o-forms-title__main">Label for input here</span>
</span>
<span class="o-forms-input o-forms-input--text">
<input id="text-example" type="text" name="text-example" value>
</span>
</label>
To create a file input use a single input field structure, with an o-forms-input--file modifier class on the o-forms-input element and an input type of type="file".
<label for="text-example" class="o-forms-field">
<span class="o-forms-title">
<span class="o-forms-title__main">Label for input here</span>
</span>
<span class="o-forms-input o-forms-input--file">
<input id="text-example" type="file" name="file-example" value>
</span>
</label>
To create a password input use a single input field structure, with an o-forms-input--password modifier class on the o-forms-input element and an input type of type="password".
<label for="password-example" class="o-forms-field">
<span class="o-forms-title">
<span class="o-forms-title__main">Label for input here</span>
</span>
<span class="o-forms-input o-forms-input--password">
<input id="password-example" type="password" name="password-example" value>
</span>
</label>
To create a textarea input use a single input field structure, with an o-forms-input--textarea modifier class on the o-forms-input element and a textarea input element.
<label for="textarea-example" class="o-forms-field">
<span class="o-forms-title">
<span class="o-forms-title__main">Label for input here</span>
</span>
<span class="o-forms-input o-forms-input--textarea">
<textarea id="textarea-example"></textarea>
</span>
</label>
To create a select input use a single input field structure, with an o-forms-input--select modifier class on the o-forms-input element and a select input element.
<label for="select-example" class="o-forms-field">
<span class="o-forms-title">
<span class="o-forms-title__main">Label for input here</span>
</span>
<span class="o-forms-input o-forms-input--select">
<select id="select-example">
<option>Option 1</option>
<!-- further options -->
</select>
</span>
</label>
For text-like input types where o-forms does not provide a specific modifier class the o-forms-input--text modifier may be used. See more example in the Origami Registry.
E.g. to create an email input use a single input field structure, with an o-forms-input--text modifier class on the o-forms-input element and an input type of type="email".
<label for="email-example" class="o-forms-field">
<span class="o-forms-title">
<span class="o-forms-title__main">Label for input here</span>
</span>
<span class="o-forms-input o-forms-input--text">
<input id="email-example" type="email" name="email-example" value>
</span>
</label>
For fields which have more than one input element we must build on the single input field structure. Since each field has multiple inputs the o-forms-field element becomes a div and each input is associate with its own label element. Each form element must have a unique id attribute, and the for attribute of the label element must match the id of the form element it is associated with to meet accessibility requirements.
For example to for a group of radio buttons:
<div class="o-forms-field" aria-labelledby="example-group-title" role="group">
<span class="o-forms-title">
<span class="o-forms-title__main" id="example-group-title">Group Title</span>
</span>
<span class="o-forms-input o-forms-input--radio-round">
<label for="radio-1">
<input id="radio-1" type="radio" name="radio-1" value="Radio 1" checked>
<span class="o-forms-input__label">Radio 1</span>
</label>
<label for="radio-2">
<input id="radio-2" type="radio" name="radio-2" value="Radio 2" checked>
<span class="o-forms-input__label">Radio 2</span>
</label>
</span>
</div>
Note that to associate the field title to the group of inputs we should use a fieldset and legend element. However o-forms instead relies on a role="group" attribute along with an aria-labelledby attribute and associated id, example-group-title in the label above.
_We chose not to work with a fieldset because they are especially difficult to style consistentlyand_we wanted to provide visual flexibility for our users.
Other fields which use multiple input elements follow the same structure. E.g. for a group of checkbox inputs:
<div class="o-forms-field" aria-labelledby="example-group-title">
<span class="o-forms-title">
<span class="o-forms-title__main" id="example-group-title">Group Title</span>
</span>
- <span class="o-forms-input o-forms-input--radio-round">
+ <span class="o-forms-input o-forms-input--checkbox">
<label for="checkbox-1">
- <input id="checkbox-1" type="radio" name="example-radio"/>
- <span class="o-forms-input__label">Radio 1</span>
+ <input id="checkbox-1" type="checkbox" name="checkbox-1" value="1">
+ <span class="o-forms-input__label">Checkbox 1</span>
</label>
<label for="checkbox-2">
- <input id="checkbox-2" type="radio" name="example-radio"/>
- <span class="o-forms-input__label">Radio 2</span>
+ <input id="checkbox-2" type="checkbox" name="checkbox-2" value="2">
+ <span class="o-forms-input__label">Checkbox 2</span>
</label>
</span>
</div>
To create a radio input use a multiple input field structure, with an o-forms-input--radio-round modifier class on the o-forms-input element and child radio input elements within labels. The id attribute of the input element must match the for attribute of the label element and they must be unique within the form.
<div class="o-forms-field" aria-labelledby="example-group-title" role="group">
<span class="o-forms-title">
<span class="o-forms-title__main" id="example-group-title">Group Title</span>
</span>
<span class="o-forms-input o-forms-input--radio-round">
<label for="radio-1">
<input id="radio-1" type="radio" name="radio-1" value="Radio 1" checked>
<span class="o-forms-input__label">Radio 1</span>
</label>
<label for="radio-2">
<input id="radio-2" type="radio" name="radio-2" value="Radio 2">
<span class="o-forms-input__label">Radio 2</span>
</label>
</span>
</div>
Round radio inputs support 2 themes.
o-forms-field--professional on the field element.o-forms-field--professional-inverse on the field element.See radio buttons in the registry
For a box-like, rectangular radio button replace the o-forms-input--radio-round modifier class with o-forms-input--radio-box.
Box radio buttons may also, optionally represent a negative choose by applying the o-forms-input__label--negative modifier class to its label. This is useful for a yes/no input.
Loading states are also supported by box radio buttons. We recommend using o-forms JavaScript to add states to an existing form. However to add a state manually add an additional o-forms-input__state element with role=status and aria-label="[STATE]" attributes. In addition, add a state modifier class to the o-forms-input element, o-forms-input--saving or o-forms-input--saved.
The below example shows a box style radio button with a positive "yes" and negative "no" option. The "no" option is checked and a saved state is shown.
<div class="o-forms-field" aria-labelledby="example-group-title" role="group">
<span class="o-forms-title">
<span class="o-forms-title__main" id="example-group-title">Group Title</span>
</span>
<span class="o-forms-input o-forms-input--radio-round o-forms-input--saved">
<label for="radio-yes">
<input id="radio-yes" type="radio" name="positive" value="Yes">
<span class="o-forms-input__label">Yes</span>
</label>
<label for="radio-no">
<input id="radio-no" type="radio" name="negative" value="No" checked>
<span class="o-forms-input__label o-forms-input__label--negative">No</span>
</label>
<span role="status" class="o-forms-input__state"></span>
</span>
</div>
To show a state label with no text set the modifier class o-forms-input__state--icon-only on the o-forms-input__state state element. Or to use custom copy for the saving and saved states add the modifier class o-forms-input__state--custom and put your copy within the state element. However, as mentioned previously, we recommend setting a custom label using the setState JavaScript method instead of adding this markup manually.
Box radio inputs support 2 themes.
o-forms-field--professional on the field element.o-forms-field--professional-inverse on the field element.Deprecated, we no longer recommend pseudo box radio inputs. These will be removed in a future major version:
Its possible to achieve the look of box style radio inputs with anchor elements instead of actual radio inputs, we call these pseudo box radio inputs. This is no longer recommended and should not be used in new projects.
<div class="o-forms-input o-forms-input--pseudo-radio-link">
<a class="o-forms-input__link o-forms-input__link--current" href="/category">Category View</a>
<a class="o-forms-input__link" href="/timeline">Timeline View</a>
</div>
Links which look like form inputs may be confusing for some users of assistive technologies, as they may be accessed or behave differently than expected. Further, unlike true o-forms radio inputs, there is no fieldset with legend to group the links. For most cases, use standard box radio inputs instead.
To create a checkbox input use a multiple input field structure, with an o-forms-input--checkbox modifier class on the o-forms-input element and child checkbox input elements within labels.
<div class="o-forms-field" aria-labelledby="example-group-title">
<span class="o-forms-title">
<span class="o-forms-title__main" id="example-group-title">Group Title</span>
</span>
<span class="o-forms-input o-forms-input--checkbox">
<label for="checkbox-1">
<input id="checkbox-1" type="checkbox" name="checkbox-1" value="1">
<span class="o-forms-input__label">Checkbox 1</span>
</label>
<label for="checkbox-2">
<input id="checkbox-2" type="checkbox" name="checkbox-2" value="2">
<span class="o-forms-input__label">Checkbox 2</span>
</label>
</span>
</div>
To align the checkbox to the right of its label, add the o-forms-input__right class to the label element:
...
<span class="o-forms-input o-forms-input--checkbox">
- <label for="my-checkbox">
+ <label for="my-checkbox"class="o-forms-input__right">
<input id="my-checkbox" type="checkbox" name="my-checkbox"/>
<span class="o-forms-input__label">Checkbox 1</span>
</label>
</span>
...
Square checkboxes also support an additional theme:
professional: To add the professional theme to a square checkbox, add the o-forms-field--professional modifier class to the field element.
professional-inverse: To add the professional inverse theme to a square checkbox, add the o-forms-field--professional-inverse modifier class to the field element.
For a toggle checkbox, replace the o-forms-input--checkbox modifier class with o-forms-input--toggle.
<div class="o-forms-field" aria-labelledby="example-group-title">
<span class="o-forms-title">
<span class="o-forms-title__main" id="example-group-title">Group Title</span>
</span>
<span class="o-forms-input o-forms-input--toggle">
<label for="checkbox-1">
<input id="checkbox-1" type="checkbox" name="checkbox-1" value="1">
<span class="o-forms-input__label">Checkbox 1</span>
</label>
<label for="checkbox-2">
<input id="checkbox-2" type="checkbox" name="checkbox-2" value="2">
<span class="o-forms-input__label">Checkbox 2</span>
</label>
</span>
</div>
Toggles support 2 themes.
o-forms-field--inverse on the field element.o-forms-field--white on the field element.Add descriptions to toggles / checkboxes by adding o-forms-input__label__main and o-forms-input__label__prompt span elements. These must be associated with the checkbox input using aria-labelledby and aria-describedby attributes:
<div class="o-forms-field" role="group" aria-labelledby="[your-title-id]" aria-describedby="[your-description-id]">
<span class="o-forms-title">
<span class="o-forms-title__main" id="[your-title-id]">Toggle inputs with description</span>
<span class="o-forms-title__prompt" id="[your-description-id]">Optional prompt text</span>
</span>
<span class="o-forms-input o-forms-input--toggle">
<label for="checkbox-example">
<input id="checkbox-example" type="checkbox" name="default" value="Lorem ipsum dolor sit amet" checked="" aria-labelledby="[your-checkbox-label-id]" aria-describedby="[your-checkbox-description-id]" required="">
<span class="o-forms-input__label">
<span id="[your-checkbox-label-id]" class="o-forms-input__label__main">
Lorem ipsum dolor sit amet
</span>
<span id="[your-checkbox-description-id]" class="o-forms-input__label__prompt">
Lorem ipsum dolor sit amet consectetur adipisicing elit. Ad earum magnam vel possimus harum suscipit.
</span>
</span>
</label>
</span>
</div>
We do not use input[type=date], but instead combine three input[type=text] inputs. We use inputmode="numeric" to show a numeric keyboard in mobile browsers which support the attribute. And use a pattern attribute for basic client side date validation.
To create our date input use a multiple input field structure, with an o-forms-input--date modifier class on the o-forms-input element, containing inputs as shown:
<div class="o-forms-field" aria-labelledby="example-group-title">
<span class="o-forms-title">
<span class="o-forms-title__main" id="example-group-title">Group Title</span>
</span>
<span class="o-forms-input o-forms-input--date">
<label for="date">
<input id="date" class="o-forms-input__day-part" type="text" inputmode="numeric" pattern="(0[1-9]|1[0-9]|2[0-9]|3[01])" name="my-date" aria-label="Day (DD)"/>
<span class="o-forms-input__label">DD</span>
</label>
<label for="month">
<input id="month" class="o-forms-input__month-part" type="text" inputmode="numeric" pattern="(0[1-9]|1[012])" name="my-date" aria-label="Month (MM)"/>
<span class="o-forms-input__label">MM</span>
</label>
<label for="year">
<input id="year" class="o-forms-input__year-part" type="text" inputmode="numeric" pattern="[0-9]{4}" name="my-date" aria-label="Year (YYYY)"/>
<span class="o-forms-input__label">YYYY</span>
</label>
</span>
</div>
We avoid type="number" here for a number of reasons related to accessibility and how browsers handle number inputs, which gov.uk explain thoroughly in a blogpost.
To add additional, contextual information to an input label add a title element with class o-forms-title__prompt. When adding a prompt to a multiple input field, such as a checkbox or radio button group, give the prompt element an id and associated aria-describedby label on the field.
For a single input field, such as a text input:
<span class="o-forms-field">
<span class="o-forms-title">
<label for="text-example" class="o-forms-title__main">Label for input here</label>
+ <span class="o-forms-title__prompt">Extra context for the input</span>
</span>
<span class="o-forms-input o-forms-input--text">
<input id="text-example" type="text" name="text-example" value>
</span>
</span>
For a multiple input field, such as a checkbox group:
-<div class="o-forms-field" aria-labelledby="example-group-title">
+<div class="o-forms-field" aria-labelledby="example-group-title" aria-describedby="example-group-prompt">
<span class="o-forms-title">
<span id="example-group-title" class="o-forms-title__main">Group Title</span>
+ <span id="example-group-prompt" class="o-forms-title__prompt">Extra context for the input</span>
</span>
<span class="o-forms-input o-forms-input--checkbox">
<label for="checkbox-1">
<input id="checkbox-1" type="checkbox" name="checkbox-1" value="1">
<span class="o-forms-input__label">Checkbox 1</span>
</label>
<label for="checkbox-2">
<input id="checkbox-2" type="checkbox" name="checkbox-2" value="2">
<span class="o-forms-input__label">Checkbox 2</span>
</label>
</span>
</div>
Add the o-forms-field--optional class to indicate that a field is optional. For example to mark a text field as optional:
-<label for="text-example" class="o-forms-field">
+<label for="text-example" class="o-forms-field o-forms-field--optional">
<span class="o-forms-title">
<span class="o-forms-title__main">Label for input here</span>
</span>
<span class="o-forms-input o-forms-input--text">
<input id="text-example" type="text" name="text-example" value>
</span>
</label>
To inline an element, such as a button, after an input add the class o-forms-input--suffix on the o-forms-input element. For example to inline a button with a text input using o-buttons:
<label for="text-example" class="o-forms-field">
<span class="o-forms-title">
<span class="o-forms-title__main">Search for an example thing</span>
</span>
- <span class="o-forms-input o-forms-input--text">
+ <span class="o-forms-input o-forms-input--text o-forms-input--suffix">
<input id="text-example type="text" name="text-example" value>
+ <button class="o-buttons o-buttons--secondary o-buttons--big">Search</button>
</span>
</label>
Add the class o-forms-input--small on the o-forms-input element to reduce the size of an input. For example to output a small text input:
<label for="text-example" class="o-forms-field">
<span class="o-forms-title">
<span class="o-forms-title__main">Label for input here</span>
</span>
- <span class="o-forms-input o-forms-input--text">
+ <span class="o-forms-input o-forms-input--text o-forms-input--small">
<input id="text-example" type="text" name="text-example" value>
</span>
</label>
To display an input next to its label, rather than below, set o-forms-field--inline.
-<label for="text-example" class="o-forms-field">
+<label for="text-example" class="o-forms-field o-forms-field--inline">
<span class="o-forms-title">
<span class="o-forms-title__main">Label for input here</span>
</span>
<span class="o-forms-input o-forms-input--text">
<input id="text-example" type="text" name="text-example" value>
</span>
</label>
If the label of an inlined field is short the class o-forms-title--vertical-center may be added to align the title element vertically with the input.
-<label for="text-example" class="o-forms-field">
+<label for="text-example" class="o-forms-field o-forms-field--inline">
- <span class="o-forms-title">
+ <span class="o-forms-title o-forms-title--vertical-center">
<span class="o-forms-title__main">Label for input here</span>
</span>
<span class="o-forms-input o-forms-input--text">
<input id="text-example" type="text" name="text-example" value>
</span>
</label>
By default the inline label and input will be a set width to ensure multiple inline fields are aligned with one another. Set o-forms-title--shrink to allow the input to take all available space.
-<label for="text-example" class="o-forms-field">
+<label for="text-example" class="o-forms-field o-forms-field--inline">
- <span class="o-forms-title o-forms-title--shrink">
+ <span class="o-forms-title o-forms-title--shrink">
<span class="o-forms-title__main">short label</span>
</span>
<span class="o-forms-input o-forms-input--text">
<input id="text-example" type="text" name="text-example" value>
</span>
</label>
Add the class o-forms-input--inline to the o-forms-input element to display multiple inputs inline. For example, by default multiple checkboxes are stacked on top of each other but may be shown in a row:
<div class="o-forms-field" aria-labelledby="example-group-title">
<span class="o-forms-title">
<span class="o-forms-title__main" id="example-group-title">Group Title</span>
</span>
- <span class="o-forms-input o-forms-input--checkbox">
+ <span class="o-forms-input o-forms-input--checkbox o-forms-input--inline">
<label for="checkbox-1">
<input id="checkbox-1" type="checkbox" name="checkbox-1" value="1">
<span class="o-forms-input__label">Checkbox 1</span>
</label>
<label for="checkbox-2">
<input id="checkbox-2" type="checkbox" name="checkbox-2" value="2">
<span class="o-forms-input__label">Checkbox 2</span>
</label>
</span>
</div>
o-forms JavaScript builds on form validation built into the browser to visually display an input as valid or invalid; display a custom error message below the input; and generate an error summary.
To show a custom error message below an input add an element with class o-forms-input__error as a child of the o-forms-input element. Add your message to o-forms-input__error and to meet accessibility standards we add role="alert".
For example to create a required text field with a custom error message, whilst including o-forms JavaScript.
<label for="required-text" class="o-forms-field">
<span class="o-forms-title">
<span class="o-forms-title__main">Label for input here</span>
</span>
<span class="o-forms-input o-forms-input--text">
- <input id="required-text" type="text" name="required-text-example">
+ <input id="required-text" type="text" name="required-text-example" required>
+ <span role="alert" class="o-forms-input__error>Error message here for a required input</span>
</span>
</label>
For example to render an invalid field without o-forms JavaScript:
<label for="required-text" class="o-forms-field">
<span class="o-forms-title">
<span class="o-forms-title__main">Label for input here</span>
</span>
- <span class="o-forms-input o-forms-input--text">
+ <span class="o-forms-input o-forms-input--text o-forms-input--invalid">
- <input id="required-text" type="text" name="required-text-example">
+ <input id="required-text" type="text" name="required-text-example" required>
+ <span role="alert" class="o-forms-input__error>Error message here for a required input</span>
</span>
</label>
o-forms also generates an error message element when a form is submitted and invalid inputs are recognised. Inputs must have a unique id and a field title element to show in the error summary.
This feature will collect the custom messages of the invalid fields if they are present in the markup, or will default to the browsers native error message if they aren't. It will associate the message to the title of the input that is invalid, generate a list of links at the top of the form, and focus on the first link.
This markup will always be generated dynamically if the errorSummary option is not set to false.
If you are not using o-forms JavaScript you may manually create the error summary within an o-forms element using the following markup:
<!-- error summary, `labelledby` the error heading -->
<div class="o-forms__error-summary" aria-labelledby="my-error-summary" role="alert">
<h4 id="my-error-summary" class="o-forms__error-summary__heading">There is a problem</h4>
<ul class="o-forms__error-summary__list">
<li class="o-forms__error-summary__item">
<!-- link to the invalid input -->
<a href="#my-date-input">
<!-- the name of the invalid input -->
<span class="o-forms__error-summary__item-overview">My date input</span>:
<!-- a description of what is wrong and how to fix it -->
<span class="o-forms__error-summary__item-detail">
Please use the format (DD/MM/YYYY)
</span>
</a>
</li>
</ul>
</div>
o-forms has a primary mixin; oForms().
You can include styles for every input type and feature by calling that mixin:
@import '@financial-times/o-forms/main';
@include oForms();
If you would like to be more specific about what aspects of the styles get output, then you'll need to provide the primary mixin with an $opts map. For example, in order to output styles for text inputs and checkboxes, and add the ability to inlne them, you would use the following:
@import '@financial-times/o-forms/main';
@include oForms($opts: (
'elements': ('text', 'checkbox'),
'features': ('inline')
));
o-forms has many options due to its comprehensive nature.
The $opts map accepts two lists with the following options:
'elements':
'checkbox''date''file''password''pseudo-radio-link''radio-round''radio-box''select''textarea''text''toggle''features':
'disabled''inline''right''inverse' (deprecated, see the 'themes' option)'small''state''suffix'error-summary'themes'
'inverse''professional''professional-inverse''white'Note 1: valid and invalid styles are output with the base of o-forms so there is no need to include them in the list above.
Note 2: It's important to remember that not all features will apply to all input types. If there are any features you would like to see added to an input, please get in touch with the team.
There is one public mixin to customise two types of input: pseudo radio links and box-styled input[type=radio].
It accepts four arguments:
$input: (required) either 'pseudo-radio-link' or 'radio'$modifier: (required) this will name the modifier to add to the input container class list$icons: (optional) accepts an icon or a list of icons to output according to the custom theme$theme: (required) a map of the colors that define the custom theme:
'controls-base': the base color of the theme'controls-checked-base': the background color of a checked input'controls-negative-checked-background': the background color for a 'negative' checked input'controls-border': the colour of the border around the controls@include oFormsAddCustom((
$input: 'radio',
$modifier: 'my-theme', // outputs the class 'o-forms-input--my-theme',
$icons: 'burger'
$theme: (
controls-base: 'claret',
controls-checked-base: 'white',
controls-negative-checked-background: 'claret-30'
)
));
No code will run automatically unless you are using the Build Service. You must either construct an o-forms object or fire an o.DOMContentLoaded event, which o-forms listens for.
The JavaScript for this component is primarily responsible for individual input validation and overall form validation.
If you would like to use an input without a form element, you can still apply validation to it with the o-forms individual Input API.
The main o-forms JavaScript has been written to identify and run on a <form> element. You'll need to set up your form and include the data attribute data-o-component="o-forms":
<form data-o-component="o-forms">
<!-- form elements as demonstrated in the markup section above -->
</form>
By default, o-forms is initialised with validation logic. It will generate an error summary for invalid elements when the form is submitted:
import oForms from '@financial-times/o-forms';
oForms.init()
The default behaviour of o-forms can be changed by configuring the options object. For example, set preventSubmit: true to prevent the user from submitting the form. You may then run your own logic before submitting the form by listening for the oForms.submit event.
oForms.init(null, {
preventSubmit: true
})
window.addEventListener('oForms.submit', (e) => {
console.log(`A user would like to submit a form, it is ${e.detail.valid ? 'valid' : 'invalid'}.`);
if(e.detail.valid) {
e.detail.instance.form.submit();
}
});
The error summary may also be prevented by setting errorSummary: false. Though we do not recommend this as an error summary can be helpful for users to discover and navigate a form with errors – this is particularly true for users of some assistive technologies.
oForms.init(null, {
errorSummary: false
})
In order to use default browser validation set useBrowserValidation: true:
oForms.init(null, {
useBrowserValidation: true,
errorSummary: false
})
You can also set these values to the data attributes e.g. data-o-forms-prevent-submit, data-o-forms-use-browser-validation, and data-o-forms-error-summary on the <form> element.
In the case where a single input is enough for a product but requires validation, you can initialise an Input instance:
import Input from '@financial-times/o-forms/src/js/input';
new Input(myInputEl);
o-forms offers the ability to display a 'saving' or 'saved' state. However, currently the only input that accepts state is the box-styled input[type=radio]. If you would like to apply state to any other input, please get in touch with the team.
o-forms has no opinion about the timing of the states—it doesn't know when to change from 'saving' to 'saved', but it has a public method setState that allows the project to control this.
The setState method accepts three arguments: the state, name, and label. State can be one of 'saving', 'saved' or 'none'. 'none' removes any state from the input. The name argument must be the name of the inputs that will be recieving the state. Label is used in the user interface to describe the state. Label is optional and defaults to 'Saving' for the saving state and 'Saved' for the saved state.
<form data-o-component="o-forms">
...
<label for="daily">
<span class="o-forms-input__label">Daily</span>
<input id="daily" type="radio" name="my-radio-box"/>
</label>
<label for="weekly">
<span class="o-forms-input__label">Weekly</span>
<input id="weekly" type="radio" name="my-radio-box"/>
</label>
...
</form>
import oForms from '@financial-times/o-forms';
let myForm = oForms.init();
// on event, e.g. click
myForm.setState('saving', 'my-radio-box');
To change the saving label pass a third argument, e.g. to update the label from "Saving" to "Sending":
-myForm.setState('saving', 'my-radio-box');
+myForm.setState('saving', 'my-radio-box', {
+ iconLabel: 'Sending'
+});
You also have the option of displaying state as an icon without text. In order to do this, you can call the method above with an extra options argument:
myForm.setState('saving', 'my-radio-box', {
iconOnly: true
});
| State | Major Version | Last Minor Release | Migration guide |
|---|---|---|---|
| ✨ active | 9 | N/A | migrate to v9 |
| ⚠ maintained | 8 | 8.5 | migrate to v8 |
| ╳ deprecated | 7 | 7.1 | migrate to v7 |
| ╳ deprecated | 6 | 6.0 | migrate to v6 |
| ╳ deprecated | 5 | 5.11 | migrate to v5 |
| ╳ deprecated | 4 | 4.1 | migrate to v4 |
| ╳ deprecated | 3 | 3.5 | migrate to v3 |
| ╳ deprecated | 2 | 2.0 | migrate to v2 |
| ╳ deprecated | 1 | 1.0 | migrate to v1 |
| ╳ deprecated | 0 | 0.13 | N/A |
If you have any questions or comments about this component, or need help using it, please either raise an issue, visit #origami-support or email Origami Support.
This software is published by the Financial Times under the MIT licence.
FAQs
This component provides responsive styling for form fields and inputs. It provides validation and error handling for forms, as well.
We found that @financial-times/o-forms demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 10 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.
Security News
RubyGems.org has added a new "maintainer" role that allows for publishing new versions of gems. This new permission type is aimed at improving security for gem owners and the service overall.
Security News
Node.js will be enforcing stricter semver-major PR policies a month before major releases to enhance stability and ensure reliable release candidates.