# Disclosure.ContentOptions

Options for native `<details>` content.

## Signatures

```ts
export interface ContentOptions extends Dom.HostOptions<HTMLDetailsElement> {
    readonly state: RefSubject.HydratedRefSubject<State, Schema.SchemaError>;
    readonly content: Renderable.Any;
}
```

## Why

A shared state lets application code observe and control the browser-owned
disclosure lifecycle.

## Ownership and lifetime

Options are inert; rendering owns listeners and the NativeDetails observer.

## Property: content

Summary and disclosed body content.

## Property: content: Why

Keeping the subtree renderable preserves Typed error/service composition.

## Property: content: Ownership and lifetime

Dynamic content follows the details Scope.

## Property: state

Hydrated state synchronized with the details element.

## Property: state: Why

Native toggle events and application updates converge on one source.

## Property: state: Ownership and lifetime

The content borrows state; its originating Scope owns it.