Skip to content
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.

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

InputNumber: float label initially broken if allowEmpty = false #4516

Closed
kaeldric opened this issue Sep 28, 2023 · 0 comments · Fixed by #4789
Closed

InputNumber: float label initially broken if allowEmpty = false #4516

kaeldric opened this issue Sep 28, 2023 · 0 comments · Fixed by #4789
Labels
Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Milestone

Comments

@kaeldric
Copy link
Contributor

Describe the bug

If there is an empty starting value, the allowEmpty flag works as expected and sets a valid value, but the float label and the new number initially overlap.

Reproducer

https://codesandbox.io/s/nervous-brattain-6m38v7?file=/src/App.vue

PrimeVue version

3.35.0

Vue version

3.x

Language

TypeScript

Build / Runtime

Vue CLI App

Browser(s)

No response

Steps to reproduce the behavior

No response

Expected behavior

No response

@kaeldric kaeldric added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Sep 28, 2023
@tugcekucukoglu tugcekucukoglu added Type: Bug Issue contains a bug related to a specific component. Something about the component is not working and removed Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible labels Nov 15, 2023
@tugcekucukoglu tugcekucukoglu added this to the 3.41.0 milestone Nov 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants