Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
vnbaaij merged 1 commit into from
Feb 27, 2024
Merged

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

vnbaaij merged 1 commit into from
Feb 27, 2024

Conversation

@vnbaaij
Copy link
Collaborator

@vnbaaij vnbaaij commented Feb 26, 2024

@vnbaaij vnbaaij added the v3 label Feb 26, 2024
@vnbaaij vnbaaij added this to the V4.5.0 milestone Feb 26, 2024
@vnbaaij vnbaaij requested a review from dvoituron February 26, 2024 20:46
@vnbaaij vnbaaij self-assigned this Feb 26, 2024
@vnbaaij vnbaaij merged commit b07267d into dev Feb 27, 2024
@vnbaaij vnbaaij deleted the vnbaaij/fix-issue-#1531 branch February 27, 2024 08:44
vnbaaij added a commit that referenced this pull request Mar 6, 2024
@vnbaaij
Fix #1531 by using web components current-value instead of value. (#1576
64f464f 
)
@LuohuaRain LuohuaRain mentioned this pull request Jul 23, 2024
Merged
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@dvoituron dvoituron dvoituron approved these changes

Assignees

@vnbaaij vnbaaij

Labels

v3

Projects

None yet

Milestone

V4.5.0

Development

Successfully merging this pull request may close these issues.

fix: FluentNumberField's two-way data binding on Value Property does not update appropriately

3 participants

@vnbaaij @dvoituron