> For the complete documentation index, see [llms.txt](https://atomico.gitbook.io/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atomico.gitbook.io/doc/guides/archives/forms-and-shadowdom.md).

# Forms and shadowDOM

Improve the interaction with the forms and accessibility of your components.

It is normal that we use the technique of dispatching events from the component to communicate states and more, but when using forms this changes since the events inside the shadowDOM do not interact with the form outside of it, example:

```markup
<form>
    <my-input>
        #shador-root
            <input/>
    </my-input>
</form>
```

To solve this we will have to nest an input tag in the lightDOM of our component, in order to reflect the logic of this to the form. Atomico facilitates this hybrid interaction between lightDOM and shadowDOM with the [**@atomico/hooks/use-render**](/doc/packages/atomico-hooks/use-render.md) hook that allows executing a second render that works from the lightDOM, example:

```jsx
import { useRender } from "@atomico/hooks/use-render";

function myInput(){
    // render LightDOM
    useRender(()=><input/>);
    
    // render ShadowDOM
    return <host shadowDom>
        <slot/>
    </host>
}
```

With this you have gained full control over the existing input tag in the lightDOM, allowing you to apply styles using the `::slotted` selector, example:

```javascript
myInput.styles = css`
    :slotted(input){
        border: 1px solid black;
        height: 40px;
    }
`;
```

We have created an input tag that allows you to interact directly with the form, this technique is applicable with all the tags that interact with the form, such as button, input, textarea and others.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://atomico.gitbook.io/doc/guides/archives/forms-and-shadowdom.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.