## Background
In {T346168} we've implemented the error-hover state using `border-color-error--hover` in TextInput. We need to include the same logic in the rest of components used in forms where the error could be possible:
- TextArea
- Select
- ChipInput
### User stories
- As a user, I need to know when a TextArea and Select are interactive when error.
### Design spec
//Link the spec sheets here once they are completed.//
| TextArea component's spec | Select component's spec |
### Open questions
[] Should we include the `error` state within all the components that can be contained within Field?
[] Radio: there is an option where the [[ https://doc.wikimedia.org/codex/latest/components/demos/radio.html#with-no-initial-selection | Radio group with no initial selection ]]. In this case, the radios could contain errors in case the form Field is mandatory and the user doesn't select one of the radios.
[] Combobox: If the form Field is mandatory and the user leaves the Combobox empty with no selection, would the Combobox contain an error?
[] Lookup: same, in case the form Field is mandatory and the user leaves the Lookup empty with no selection from the menu, would the Lookup contain an error?
### Acceptance criteria (or Done)
**Design**
[] Design the Figma spec sheets for those components and link them in this task:
[] TextArea
[] Select
[] ChipInput
[] Update the components in the [[ https://www.figma.com/file/KoDuJMadWBXtsOtzGS4134/❖-Codex-components?node-id=1891%3A4420&viewport=287%2C338%2C0.28 | Codex Figma library ]]. //This step will be done by a DST member.//
[] Update the image and list of states in the Guidelines > Interaction states in both:
[] TextArea
[] Select
[] ChipInput
**Code**
[] Update components in Codex using the `border-color-error--hover` token in the`error-hover` state:
[] TextArea
[] Select
[] ChipInput