FG UI 1.3 development

Theme Inheritance 1.3

Phase 2 component inheritance across local Light and Dark semantic surfaces.

PHASE 2
ACTIVE FG UI 1.3 DEVELOPMENT

FG UI 1.2.0 remains Stable. This page exercises additive 1.3 theme-composition work against the live /dev runtime.

FG UI 1.3 development

Overlay / Portal Theme Context

Phase 3 proves that floating UI keeps the semantic Light/Dark/Hybrid and Accent context of the control that opened it, even when the overlay lives at document root.

PHASE 3
ONE CONTEXT ENGINE

FGUI transfers the opener's resolved semantic recipe instead of creating component-specific Dark copies.

Root overlays opened from Dark

These targets live outside the forced Dark opener surface.

Forced Dark opener

Root overlays opened from Light

A forced Light source remains Light even when global theme is Dark.

Forced Light opener

Floating panels

Local panels also snapshot opener context so they remain correct if later portaled.

Generic portal contract

Future command/search palettes can use the same transfer contract.

FGUI.open(target, { source: opener })

Detached targets opt in with data-fgui-theme-context-target.

Next: Phase 3A adds zero-flash theme startup and the formal site-default → saved-preference → System hierarchy.