-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Grouped Product Quantity Validation Displays Errors for All Inputs When One Input Is Invalid #39347
Comments
Hi @allforcode. Thank you for your report.
Join Magento Community Engineering Slack and ask your questions in #github channel. |
Hi @engcom-Bravo. Thank you for working on this issue.
|
Hi @allforcode, Thanks for your reporting and collaboration. We have verified the issue in Latest 2.4-develop instance and the issue is reproducible.Kindly refer the screenshots. Steps to reproduce
All input fields displays error message, even if their values are valid. Hence Confirming the issue. Thanks. |
✅ Jira issue https://jira.corp.adobe.com/browse/AC-13325 is successfully created for this GitHub issue. |
✅ Confirmed by @engcom-Bravo. Thank you for verifying the issue. |
@magento I'm working on this |
Preconditions and environment
Magento Versions
I tested in Magento 2.4.7 and Magento 2.4.7-p2
Description
On the grouped product page, entering a single invalid quantity (e.g., a negative value) causes error messages to appear for all quantity input fields, even if the other inputs have valid values. This behavior creates confusion for users who have correctly entered quantities.
Steps to reproduce
Expected result
Only the input field with an invalid quantity should display an error message.
Actual result
All input fields display an error message, even if their values are valid.
Additional information
In Magento 2.4.5, the form validation is handled by
view/frontend/web/product/view/validation.js
, whereas in Magento 2.4.7, it is managed bylib/web/mage/validation.js
.Release note
No response
Triage and priority
The text was updated successfully, but these errors were encountered: