You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When labor is set to "Optional" on the configuration page, the user should be able to either not enter any labor data or enter both labor data. Because the firefox HTML input form allows users to put non-numeric characters even though its type is set to number and simply returns an empty string for the value, there is no way to distinguish between when a user puts invalid input (thus firefox returning "") or user clearing the input after putting something in there (initially it is set to null, then user puts something in it, then deletes it, making it an empty string ""). Thus, whenever the user puts in an invalid input, the feature implemented at #541 stops working.
Steps to Reproduce
Set the configuration to "optional" on the configuration page
Go to the Seeding input and put all the values except labor-related fields to test the submit button.
Put a valid value in one of the fields
Put an invalid value on the other field
Clear the field with a valid value. Now the submit button is highlighted and the field with wrong input is not highlighted
Suggested Solution
Need research.
The text was updated successfully, but these errors were encountered:
@Panktivpatel Welcome. It would be great to see what you can do with this issue.
Note: If you are in a class that is using the "GitKit" and an assignment asked you to comment on an issue for your course be sure you are using the correct "upstream" for your course. This is the main upstream for FarmData2. We welcome your contributions. But I wanted to be sure this was what you intended.
Description of the Issue
When labor is set to "Optional" on the configuration page, the user should be able to either not enter any labor data or enter both labor data. Because the firefox HTML input form allows users to put non-numeric characters even though its type is set to number and simply returns an empty string for the value, there is no way to distinguish between when a user puts invalid input (thus firefox returning "") or user clearing the input after putting something in there (initially it is set to null, then user puts something in it, then deletes it, making it an empty string ""). Thus, whenever the user puts in an invalid input, the feature implemented at #541 stops working.
Steps to Reproduce
Suggested Solution
Need research.
The text was updated successfully, but these errors were encountered: