fragdenstaat.de - The error message is not displayed when reach the maximum limit when changing the date
Categories
(Web Compatibility :: Site Reports, defect, P3)
Tracking
(Not tracked)
People
(Reporter: railioaie, Unassigned)
References
(Depends on 1 open bug, )
Details
(Keywords: webcompat:platform-bug, webcompat:site-report, Whiteboard: [webcompat-source:web-bugs])
User Story
platform:windows,mac,linux,android impact:annoyance-minor configuration:general affects:all branch:release
Attachments
(1 file)
|
159.36 KB,
image/png
|
Details |
Screenshot_192.png
Environment:
Operating system: Android 14
Firefox version: Firefox Mobile 129.0
Preconditions:
Clean profile
Steps to reproduce:
- Navigate to: https://fragdenstaat.de/anfrage/informationen-dazu-warum-abgabe-der-stimme-per-eid-elektronischer-signatur-per-ausweis-nicht-mehr-angeboten-wird-in-deutschland-1/
- Login
- Write a FOI request
- Click the pencil near the expiration date and try to edit
- If the value is higher than 15 an error message should be displayed
Expected Behavior:
- The error message is displayed
Actual Behavior:
2. The error message is not displayed and the user can complete with any value
Notes:
- Reproduces regardless of the status of ETP
- Reproduces in Firefox Nightly, and Firefox Release
- Does not reproduce in Chrome
Created from https://github.com/webcompat/web-bugs/issues/140735
/me is the original reporter
Ah and I found/remembered https://fragdenstaat.de/behoerde/7681/testbehorde/ – it's a test agency which you can use as the target to not spam any real agencies…
|
||
Comment 3•2 months ago
|
||
This is a product decision, adding ni for Dennis to find the relevant bug
|
||
Comment 4•1 month ago
|
||
This is effectively bug 1398528. That bug is about allowing non-number inputs, but it's effectively the same: we validate the field after the user has typed stuff in, not while typing in. As such, we don't block users from entering something invalid - but the browser tells them afterwards.
Technically, we're right about this. But I can see how, in this case, this could cause confusion. As opposed to entering text into number inputs, a user might reasonably type 24 into the field here, and then realize it's invalid only later. Therefore, I'll keep this as an active site report, and make it blocking on bug 1398528. It's probably not high priority, but maybe we can figure out something.
|
|
||
Comment 5•1 month ago
|
||
(Accidentally set the wrong triage flags.)
Description
•