Large do input (Variante)

[pihcardozo]

Goal

Entender a possibilidade de termos uma versão large do input e qual impacto isso teria no DS global.

Context

Precisamos de uma versão large do input para ser aplicado com destaque no layout ao ser utilizado sozinho.

Impact

Teríamos uma versão maior do input, o que contribuiria para uma variedade de possibilidades de aplicação.

Discussion Questions

A versão large se aplica para todas as variantes existentes do input atual?

Como ficaria a variante “Read only” já que o input não tem bordas?

Additional considerations

No response

Do you have a visual proposal?

https://www.figma.com/file/o4buhch2d9GQhU5txrTNmO/Large-do-input-(Variante)?type=design&node-id=110%3A14245&mode=design&t=4njhXSAd11ESnV59-1

[AnaMontes11]

Hey @pihcardozo! Thanks for reaching out.

Reviewing the information you've provided, we understand that this need for input large goes beyond functionality and is solely related to an aesthetic aspect. In that case, we believe that the current Mistica input works.

We have a few questions though. For instance, what happens when we have more inputs? Will some be in large size while others remain as they are now? What about longer texts?

Could you show us more use cases? Examples from different contexts and with other typologies (not just numeric). This would help us have a broader understanding to address it.

Thanks!

[vinrosa]

Hello @AnaMontes11

We wouldn't have more than one input on the screen, this component variation was created precisely for flows where the user's focus is on filling out a single input. In situations where the screen has more than one element, be it another input or any other element, a regular input must be used.

The intention is that the user, when entering this screen, has the focus on the input with the keyboard already active for filling.

Use cases where input large would be used

Examples where normal input should be used

[AnaMontes11]

Hi @vinrosa, for the purpose you mentioned, the <autofocus> property already exists, which opens the keyboard. So, using the input we already have shouldn't be an impediment.

[yceballost]

This component won't be part of Mística by the moment, will be developed in a Vivo extended library