Clay: Small visual updates for LocalizedInput

[oliv-yu]

What is your proposal?

It looks like both segments and web content have their own localized input, but was wondering if Clay's could have some APIs to make it resemble theirs? We're creating another admin page using the same localized input header and Clay's current localized input doesn't seem to cover this use case. Also would be nice in case other teams were considering to adopt it.

Options:

• position icon to the left of the input
• hide selected locale subtext
• border and locale on the icon

Also, I think there's a typo in 'untranslated' in the dropdown 😅

Thanks!

@thektan

[bryceosterhaus]

Hey @oliv-yu thanks for the proposal!

@drakonux does this fall under the lexicon specification? Wasn't sure what the configurability we wanted to provide with this design.

[drakonux]

Hey, @oliv-yu I agree DXP must have these two cases unified using the same component.

However, @bryceosterhaus this variation of the localized-input has enough differences to be a unique component just for DXP (cc\ @jbalsas ).

Besides, as far as I know, this component needs a deeper review (interaction and visual).

My recommendation would be to not add it to Clay and if a DXP team wants, they can open us a request, and Lexicon will work on a definition to allow DXP to standardize the component (portal designers can also have a meeting and get an agreement about it).

[thektan]

Thanks @drakonux! I've created a lexicon request here: https://issues.liferay.com/browse/LEXI-988

[kresimir-coko]

As @drakonux said:

My recommendation would be to not add it to Clay and if a DXP team wants, they can open us a request, and Lexicon will work on a definition to allow DXP to standardize the component (portal designers can also have a meeting and get an agreement about it).

@jbalsas Do we not add this to Clay and thus, close this issue?

[jbalsas]

Yeah, I think the goal would be to add this component to frontend-components in DXP directly rather than having it inside Clay

[kresimir-coko]

Alright, closing this then 👍

Yeah, I think the goal would be to add this component to frontend-components in DXP directly rather than having it inside Clay