fix(runtime): use strict comparison when updating properties

[SaiGovardhana]

What is the current behavior?

Currently, when component properties are updated, the runtime may treat distinct falsy values (like 0 and '') as equivalent due to loose equality checks. This can result in the DOM not reflecting the latest state, causing inputs or other properties to remain out of sync.

GitHub Issue Number: #6572

What is the new behavior?

Closes #6572

This PR introduces a strict comparison (!==) when updating element properties in the setAccessor function. Now, all value changes, including transitions between distinct falsy values, are properly propagated to the DOM.

Documentation

Does this introduce a breaking change?

• Yes
• No (Most Likely)

Testing

Added a unit test for the numeric input wrapper to verify that the internal correctly updates when the component property changes between distinct falsy values (e.g., 0 -> "").

Verified that the DOM value always reflects the latest property, ensuring transitions between falsy states are handled correctly.

[johnjenkins]

hey @SaiGovardhana - thanks for raising!
This change will cause extra renders for '', null and undefined.

I'm not sure if that's ok(?)

[SaiGovardhana]

hey @SaiGovardhana - thanks for raising! This change will cause extra renders for '', null and undefined.

I'm not sure if that's ok(?)

Hi @johnjenkins , Are you talking about stencil web components being re-rendered?

• I believe this branch of code is only run for standard html elements.

• Also the value stored set to element would be an empty string for null and undefined