Native Rml::TextInputHandler with batched lifecycle notifications.
Remarks
With no callbacks, lifecycle events remain in Native until drainEvents:
no per-widget JS callback occurs. Explicit activate/deactivate callbacks run
synchronously and may use only TextInputContext editing/read operations.
Destroy callbacks run at the next safe native boundary after invalidation,
never from native destructors or V8 finalizers. Global handlers are retained
until shutdown; context/widget owners retain their selected handlers.
Construction and global selection also work before initialization. Pending
handlers belong to the next successful initialization; shutdown invalidates
them even if initialization never ran. A rejected initialization preserves
the pending selection. Creating a handler claims this Node environment as
the setup owner until shutdown or its environment cleanup.
Drain queued events regularly to release historical notification storage.
Native Rml::TextInputHandler with batched lifecycle notifications.
Remarks
With no callbacks, lifecycle events remain in Native until drainEvents: no per-widget JS callback occurs. Explicit activate/deactivate callbacks run synchronously and may use only TextInputContext editing/read operations. Destroy callbacks run at the next safe native boundary after invalidation, never from native destructors or V8 finalizers. Global handlers are retained until shutdown; context/widget owners retain their selected handlers. Construction and global selection also work before initialization. Pending handlers belong to the next successful initialization; shutdown invalidates them even if initialization never ran. A rejected initialization preserves the pending selection. Creating a handler claims this Node environment as the setup owner until shutdown or its environment cleanup. Drain queued events regularly to release historical notification storage.