9ba46d9f88
Previously, when an input property was initially set to `undefined` it would not be correctly recognized as a change (and trigger `ngOnChanges()`). This commit ensures that explicitly setting an input to `undefined` is correctly handled the same as setting the property to any other value. This aligns the behavior of Angular custom elements with that of the corresponding components when used directly (not as custom elements). PR Close #36140 |
||
---|---|---|
.. | ||
BUILD.bazel | ||
component-factory-strategy_spec.ts | ||
create-custom-element_spec.ts | ||
extract-projectable-nodes_spec.ts | ||
slots_spec.ts | ||
utils_spec.ts |