You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Binding the placeholder input to falsy values yield undesired rendering of the stringified value on the underlying HTML Input element's placeholder attribute - e.g. placeholder="undefined/null...".
This causes accessibility issues:
Screen readers (e.g., NVDA) announce "undefined" as the field’s name or placeholder, confusing users.
Accessibility tools (e.g., WAVE) flag this as a failure.
The problem also propagates to all other components that internally use the DateInput - date/datetime pickers, date filter menus in Grid and TreeList, etc.
Expected Behavior
The placeholder should never be set to "undefined/null". If no placeholder is provided, it should be omitted or use a localized example format (e.g., "dd.mm.yyyy").