- Location
- Los Santos
For sure not a big issue, but I will follow up with a suggestion that may work.
The type if the input on the "Report a Player Form" for the Time of the incident (GMT) 24hr Format is a bit buggy. Since the input type is number, 0 on the left side of a number will always be cut as 0 on the left doesnt matter, that is why, when players add the time 0110 it will get transformed into 110, this may get worst with times like 0005 or 0010, which would transform to 5 and 10, respectively.
This is how it looks now:
My suggestion would be to change the type from number to time
Chrome, and I would assume, most of the browsers would recognize it as a known type and will add even extra "icons/functions". For the type number it is a small arrow up and down, for type time it adds a small clock.
Which automatically provides the neat feature:
Not sure how if your backend is expecting a number and changing the type will make it crash, but imo is worth a shot making a report a player with the changed type ( even with dev tools) to give it a go
The type if the input on the "Report a Player Form" for the Time of the incident (GMT) 24hr Format is a bit buggy. Since the input type is number, 0 on the left side of a number will always be cut as 0 on the left doesnt matter, that is why, when players add the time 0110 it will get transformed into 110, this may get worst with times like 0005 or 0010, which would transform to 5 and 10, respectively.
This is how it looks now:
My suggestion would be to change the type from number to time
Chrome, and I would assume, most of the browsers would recognize it as a known type and will add even extra "icons/functions". For the type number it is a small arrow up and down, for type time it adds a small clock.
Which automatically provides the neat feature:
Not sure how if your backend is expecting a number and changing the type will make it crash, but imo is worth a shot making a report a player with the changed type ( even with dev tools) to give it a go