danielmutis

WG: there should be guidelines on how to handle these situations. This should be documented with the component. Lyubo: a nav should include at least 3 items. Daniel: provide guidelines...

* Nina to explore visual solutions for this. Ideally within the toolbar that this component already has. * Copy buttons are something we don't do as a policy from the...

WG: This issue is validated. We have some solutions in the new side nav spec, which hasn't been fully approved yet. This includes more changes than just the logo. For...

WG: in order to have this in Vanilla there is a lot of work that is required. Exploring similar solutions in other products, detail the way in which we want...

WG: let's use the same background as the input so that theming can be applied. We need to consider what happens to this colour on paper background. @lyubomir-popov to provide...

WG: @juanruitina and @danielmutis to look at how the mobile experience of this component could be improved. Would also be good to identify if this component could be useful in...

WG: this component should go through the HOC process to gather requirements.

WG: @ninarojc1 to amend the ticket to include the correct visual for the expanded version. To consider as well the placement of the button when other buttons exist, and how...

The original issue was with the colour red. I see that @AnnSoMuller proposed to have them on the left for scannability. I wonder whether there is an actual need for...

Proposal: If the majority of the fields are required, mark only the optional field labels with (optional). If the majority of the fields are optional, mark only the required field...