Selection Limitation with LocalizedTextField - Requires Workaround with Hidden LocalizedTextInput

[ahmehri]

Description:

The current implementation appears to have a limitation where selecting or focusing the localized text input functionality is not directly available within the LocalizedTextField component. This contrasts with the LocalizedTextInput component, which seems to offer this capability (as indicated by functions like getId and getName in its documentation).

As a result of this limitation, consumers are forced to implement a workaround to achieve the desired selection behavior. This workaround involves rendering a LocalizedTextInput component and visually hiding it using AccessibleHidden (as demonstrated in this example). This adds unnecessary complexity to the component usage.

Expected Behavior:

Ideally, the LocalizedTextField component should provide a similar mechanism for selecting or focusing the localized text input fields as the LocalizedTextInput component, without requiring the use of a hidden component as a workaround.

Current Behavior:

The LocalizedTextField component lacks the necessary functionality (or has a different implementation) for programmatically selecting or focusing the input fields for different locales. This forces developers to use the aforementioned workaround.