Add inline validation for preset fields with regex pattern

[Shyam-123pandey]

Add inline validation for fields that define a regex pattern

Summary

This PR adds inline validation support for preset fields that define a pattern (regex).

If a field includes a regex pattern and the entered value does not match it, an informational message is displayed directly below the input field.

Behavior

• Validation runs on blur / change, not while typing.
• The message appears only after the user finishes editing the field.
• If the value becomes valid, the message disappears.
• This does not block saving.
• This does not create or modify issues in the issues panel.
• It only applies to fields that define a pattern.

Why

Some fields may define a regex pattern but currently provide no direct feedback when the value does not match the expected format.

This change improves UX by giving contextual, field-level feedback after editing is complete, while staying consistent with iD’s existing interaction model (no validation on every keystroke).

Scope

• Changes limited to uiFieldText.
• No changes to the validation engine.
• No preset/schema changes.

Closes #10769

[Copilot]

Pull request overview

Adds inline, non-blocking validation feedback for text inputs whose preset field definition includes a regex pattern, improving UX by showing/hiding a message as the user types.

Changes:

• Add a validation message element to uiFieldText’s DOM structure.
• Validate input values against field.pattern during change() and toggle the message visibility/text accordingly.

[Shyam-123pandey]

Good After noon Sir, Almost things have been resolved just check , I have doubt on one issue as copilot suggested please check above, so suggest for that.

[tyrasd]

While in general, it is probably worth exploring the options to show such validation warnings inline with the fields, the particular implementation does not seem to be very well thought through / matching the rest of our UI/UX patterns.

Closing until we have a better idea how we want to approach this in general

[Shyam-123pandey]

Okay thanks, if any you'll find please suggest, I am working on it if found any strong idea which meets required criterias, inform to you. Thanks & Regards Shyam pandey

…

On Thu, 19 Mar 2026, 4:34 pm Martin Raifer, ***@***.***> wrote: *tyrasd* left a comment (openstreetmap/iD#11925) <#11925 (comment)> While in general, it is probably worth exploring the options to show such validation warnings inline with the fields, the particular implementation does not seem to be very well thought through / matching the rest of our UI/UX patterns. Closing until we have a better idea how we want to approach this in general — Reply to this email directly, view it on GitHub <#11925 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BFALIIVU6YLECOVN2YS4U4T4RPH47AVCNFSM6AAAAACV7FSNKGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DAOBZGM2TCNRSGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>