Fix #1531 by using web components current-value instead of value. #1576

vnbaaij · 2024-02-26T20:46:08Z

Fix fix: FluentNumberField's two-way data binding on Value Property does not update appropriately #1531 by using web components current-value instead of value. Confirmed this is correct by looking at Fluent UI web component and FAST Explorer markup (both show no value attribute being used.
Also updated verified files for tests

)

vnbaaij added the v3 label Feb 26, 2024

vnbaaij added this to the V4.5.0 milestone Feb 26, 2024

vnbaaij requested a review from dvoituron February 26, 2024 20:46

vnbaaij self-assigned this Feb 26, 2024

dvoituron approved these changes Feb 27, 2024

View reviewed changes

vnbaaij merged commit b07267d into dev Feb 27, 2024
4 checks passed

vnbaaij deleted the vnbaaij/fix-issue-#1531 branch February 27, 2024 08:44

LuohuaRain mentioned this pull request Jul 23, 2024

[FluentSlider] Use current-value instead of value attribute in web component #2438

Merged

8 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Fix #1531 by using web components current-value instead of value. #1576

Fix #1531 by using web components current-value instead of value. #1576

vnbaaij commented Feb 26, 2024

Fix #1531 by using web components current-value instead of value. #1576

Fix #1531 by using web components current-value instead of value. #1576

Conversation

vnbaaij commented Feb 26, 2024