-
Notifications
You must be signed in to change notification settings - Fork 1k
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
InputGroup: Input field do not show correctly #6962
Comments
digitalnovats
added
the
Status: Needs Triage
Issue will be reviewed by Core Team and a relevant label will be added as soon as possible
label
Aug 1, 2024
melloware
added
Status: Needs Reproducer
Issue needs a runnable reproducer
and removed
Status: Needs Triage
Issue will be reviewed by Core Team and a relevant label will be added as soon as possible
labels
Aug 1, 2024
This comment was marked as outdated.
This comment was marked as outdated.
melloware
added
Type: Bug
Issue contains a defect related to a specific component.
and removed
Status: Needs Reproducer
Issue needs a runnable reproducer
labels
Aug 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When you use an InputGroup as described in the documentation, it is displayed incorrectly. The width of the input field becomes very small. This can also be noticed from the documentation.
Reproducer
Hello, in the newly released v10.8.0 I found an issue with InputGroup InputNumber width. Please see the image below from demo page:
System Information
System:
OS: Windows 11 10.0.22631
CPU: (8) x64 Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz
Memory: 9.42 GB / 31.87 GB
Binaries:
Node: 20.8.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.4 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 10.2.0 - C:\Program Files\nodejs\npm.CMD
pnpm: 9.0.5 - C:\Program Files\nodejs\pnpm.CMD
Browsers:
Chrome: 126.0.6478.128
Edge: Chromium (127.0.2651.74)
Internet Explorer: 11.0.22621.3527
npmPackages:
primereact: ^10.8.0 => 10.8.0
react: ^18.3.1 => 18.3.1
Steps to reproduce the behavior
No response
Expected behavior
No response
The text was updated successfully, but these errors were encountered: