interface / @typed/ui

Disclosure.ContentOptions

Options for native <details> content.

Learn this UI primitive →

Package version
1.0.0-beta.13
Category
Native content host
Since
1.0.0
Member of
Disclosure

Import

import { Disclosure } from "@typed/ui";

Access Disclosure.ContentOptions through the imported Disclosure export. Its declaration below describes the member.

This public exposure is a re-export. Its import path is supported; declaration documentation is shared with the other public exposures below.

Signatures

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.

Other public imports

These import paths expose the same declaration. Each page retains its own public name and signature.

Source