Welcome to the Xamarin.Forms feedback portal. We’re happy you’re here! If you have feedback on how to improve the Xamarin.Forms, we’d love to hear it!

  • Check out the features or bugs others have reported and vote on your favorites. Feedback will be prioritized based on popularity.
  • If you have feedback that’s not listed yet, submit your own.

Thanks for joining our community and helping improve Syncfusion products!

3
Votes

Hi,

I am using a SfComboBox control in Xamarin.Forms running on UWP. I am using it in token/tag mode with multi-select. The control is fixed width (it takes up X number of pixels) and the user can type their own tags into the control. I am encountering several issues with tag wrapping & tags being covered up by an invisible box at the right-hand of the control. See the below screenshot:

sfcomboboxrepro1.PNG

Tags are often not wrapping when they should be and if you click where the red arrow is, you do not get the I-beam enter text cursor. This means the user is unable to add their own custom tag whenever they encounter a situation like this. In the above screenshot, the user should be able to click to the right of the "kl" tag and be allowed to type in text. In this case, they cannot do that.

Another problem with the tags being covered is shown in these two screenshots:

sfcomboboxrepro3.PNG

sfcomboboxrepro2.PNG

The "X" on the tag/token is being covered by something invisible on the right hand side of the control. The user is not able to remove this tag. The control also has increased in height but in this case the tags do not start wrapping to the next line. This issue occurs in a sweet spot number of characters. If the tags in the above two screenshots were longer, the issue might not occur. However, our customer has encountered issues like the ones described above quite frequently in actual use.

I have attached a reproduction project. You may need to adjust the width, the tags you add, or adjust what tags are available to encounter the issue. It seems to occur on most monitors but the point at which it occurs will vary monitor to monitor.


Thanks,

Ronan