interface / @typed/ui

Popover.ContentOptions

Options for manually controlled native popover content.

Learn this UI primitive →

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

Import

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

Access Popover.ContentOptions through the imported Popover 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<HTMLDivElement> {
    readonly state: RefSubject.HydratedRefSubject<State, Schema.SchemaError>;
    readonly content: Renderable.Any;
}

Why

Content and state remain explicit while the browser owns top-layer behavior.

Ownership and lifetime

Options are inert; rendering owns the native ref and subscriptions by Scope.

Property: content

Content rendered in the top layer.

Property: content: Why

Renderable output retains Typed error and service channels.

Property: content: Ownership and lifetime

Dynamic content follows the content Scope.

Property: state

Hydrated state synchronized with native popover visibility.

Property: state: Why

Native toggle events and application updates converge on one source.

Property: state: Ownership and lifetime

The content borrows the state; its original Scope owns it.

Other public imports

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

Source