Bug #105368
Updated by Ayke Halder 11 days ago
Any @HTMLInputElement@ that has native browser-validation might block the form from beeing sent. But no validation error from the TYPO3 side is shown. It's about all those @input@-fileds which have browser-native syntax-validation either * implicit by @type="email,date,number,…"@ or * explicitly added via attributes like @min@, @max@, @minlength@, @maxlength@ … ---- Also see * See https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input#attributes * https://developer.mozilla.org/en-US/docs/Web/API/HTMLInputElement/invalid_event#result ---- h3. Without fix h4. Changed field: valid vs. invalid value !{width:45%}typo3-be-before-changed-field-without-any-error.png! !{width:45%}typo3-be-before-changed-field-with-invisible-validation-error.png! h3. With fix h4. Changed field: valid vs. invalid value !{width:45%}typo3-be-after-changed-field-without-any-error.png! !{width:45%}typo3-be-after-changed-field-with-validation-error.png!