All issues

autocomplete on input (the only element affected?) renders when false is passed, but no other attribute does this?

Needs Submitter Response

#21344

· NullVoxPopuli opened

on Apr 28, 2026

get/set/get should be supported

Proposed Feature

#21225

· NullVoxPopuli opened

on Mar 19, 2026

Toss our own sanitizing for setHTML when it becomes baseline for our supported browser versions

#21119

· NullVoxPopuli opened

on Feb 26, 2026

renderComponent should automatically cleanup if the parentElement (the element passed to `into`) is removed from the DOM

#21097

· NullVoxPopuli opened

on Feb 17, 2026

Private properties are inaccessible from the <template> region

#21007

· NullVoxPopuli opened

on Nov 16, 2025

[Feature] stack based plain-function-helper access to the owner during rendering

Needs Submitter Response

#20997

· NullVoxPopuli opened

on Oct 31, 2025

refactor destroyables to use AbortSignal and get rid of custom infra

#20990

· NullVoxPopuli opened

on Oct 13, 2025

Runtime compiler does not correctly generate the scope bag, and is thus non-reactive (incorrectly reactive?)

#20913

· NullVoxPopuli opened

on May 30, 2025

[Feature] Use Error#cause to show the cause of an error when an exception occurs in framework code

Proposed Feature

#20890

· NullVoxPopuli opened

on Mar 28, 2025

Ergo + Compat Bugs

Needs Submitter Response

#21043

· NullVoxPopuli opened

on Nov 6, 2024

support `{ toString(): string }` and `{ toHTML(): string }` as reactive outputs

#21041

· NullVoxPopuli opened

on Mar 19, 2024

[Feature] Swappable renderer

#20648

· NullVoxPopuli opened

on Feb 13, 2024