Details
-
Bug
-
Resolution: Done
-
Blocker
-
None
-
None
-
None
-
Release 5 - 12/13 Beg Del Adm:, Rel 5 - 1/10 - 1/24 - DA Cont.
Description
Tested in version 1.5.0-SNAPSHOT-5b9a841
FYI on priority, there is a workaround, so the user is not blocked. The user can use the increment arrows to increase/decrease the value.
NOTE: This occurs in Firefox, Edge, IE11, and Safari (it works fine in Chrome)
Description
The increments in the number selector do not match the requirements of the field. The user can use the selector to select 1 or 0. The filed requires: Numeric - must be between 0.0 and 1.0. Perhaps the selector can just be deleted.
When a user attempts to enter '.2' they are prevented and must enter '0' before the '.' Should there be a red error message that displays in this case?
Steps
- Log into UI
- Click 'Add New' button and select 'Metadata Provider’
- Enter 'test' in Metadata Provider Name (Dashboard Display Only), Select FileBackedHttpMetadataProvider,
- Move through the application to the Reloading page
- Attempt to enter '0.2' or '.2' in the Refresh Delay Factor field
What is occurring:
The dot (.) cannot be entered.
What is expected
User can manually enter the numbers including the dot (.)
Attachments
Issue Links
- is related to
-
SHIBUI-1080 Refresh Delay Factor
- Done
-
SHIBUI-841 Win10_Edge: Refresh Delay Factor Cannot Manually Populate Field
- Done
-
SHIBUI-937 Allow for `Refresh Delay Factor` without initial `0.` in `Reloading Attributes`
- Done