Project

General

Profile

Actions

Bug #105875

closed

Entering an invalid number value prevents saving but does not display where the error can be found

Added by Lina Wolf 23 days ago. Updated 18 days ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2025-01-02
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
13
PHP Version:
8.3
Tags:
Formengine validation
Complexity:
Is Regression:
Sprint Focus:

Description

Browser: Chrome

If I enter the letter "e" into a number field and attemp to save a content element,
the browser validation prevents the form from being saved.

However if the field is on a palette that is not currently opened it is hard to find and there is no feedback what happened during your attemp to save. Saving is simply blocked.

I would have expected an allert and marking of the palette similar to how it happens when a required field is not filled in.


Files

InputError.png (9.9 KB) InputError.png Lina Wolf, 2025-01-02 14:16

Related issues 2 (1 open1 closed)

Related to TYPO3 Core - Bug #105869: Formengine validation status brokenResolved2024-12-29

Actions
Is duplicate of TYPO3 Core - Task #105524: FormEngine: input fields of type number are not working as expected when browser-native validation gets "bad input"Under Review2024-10-30

Actions
Actions #1

Updated by Garvin Hicking 23 days ago

  • Tags set to Formengine validation
Actions #2

Updated by Garvin Hicking 23 days ago

  • Related to Bug #105869: Formengine validation status broken added
Actions #3

Updated by Garvin Hicking 18 days ago

  • Is duplicate of Task #105524: FormEngine: input fields of type number are not working as expected when browser-native validation gets "bad input" added
Actions #4

Updated by Garvin Hicking 18 days ago

  • Status changed from New to Closed

Closing as duplicate of #105524

Actions

Also available in: Atom PDF