Material-components-ios: [Chips] Large number of Chips in MDCChipField is not scrollable.

[pokurivijay]

I am trying to implement Input Chips in iOS using MDCCipField. after inserting multiple chips the MDCCipField is not scrollable.

Reproduction steps

Steps to reproduce the behavior:

1. Implement Input Chips in iOS using MDCCipField.
2. After adding multiple chips the MDCCipField is increasing its height, but not scrollable.

Expected behavior

when we input more chips, MDCCipField should be scrollable to accept input like textview.

Actual behavior

when we input more chips, MDCCipField, the size of the MDCCipField is increasing to all the screen.

Platform (please complete the following information)

• Device: iPhoneXr Emulator
• OS: iOS 12.4

Additional context

I tried to implement this behaver by using scroll view, but I am unable to find the workaround for it.

---

Internal data

• Associated internal bug: b/140724190

[material-automation[bot]]

Your title label prefix has been renamed from [iOS] to [Ink].

[anuragfluke]

Gentle Reminder !! I am also waiting for solution... if you have any please respond

[romoore]

Hi @anuragfluke. Unfortunately this is currently ranked #117 in our internal backlog, so I don't think we'll be able to work on it in the near future. At this point, I would recommend not using MDCChipField and consider using an MDCTextField (or UITextField) and a collection view with Chips in it instead.

[anuragfluke]

Thanks for information. Do you have sample or examples?

In android chipfield is using with wrap text in scroll view and it is working perfectly fine.

something similar also available would work.
Please add if there is any ETA.

Best Regards
Anurag

Sent from my iPhone

On 04-Dec-2019, at 6:40 PM, Robert Moore [e-mail]> wrote:

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Hi @anuragflukehttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_anuragfluke&d=DwMCaQ&c=YEQWdgm3lcu5w_Y3fWOQZUGtAhl_lImuPlnxuD4zIqo&r=KOUdyUURgmdxf2WWvxPoqZOSMMY5IMBW7RmuJr9ro5E&m=7pPF-A3nzead6VU24EvhH8NXVnxCIwT2SQXH9Rvq2FI&s=KGVby8BSCol94aPdQQCJFVX9LEkaqhFCjMsK3njQlAg&e=. Unfortunately this is currently ranked #117https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_material-2Dcomponents_material-2Dcomponents-2Dios_issues_117&d=DwMCaQ&c=YEQWdgm3lcu5w_Y3fWOQZUGtAhl_lImuPlnxuD4zIqo&r=KOUdyUURgmdxf2WWvxPoqZOSMMY5IMBW7RmuJr9ro5E&m=7pPF-A3nzead6VU24EvhH8NXVnxCIwT2SQXH9Rvq2FI&s=_njsIgLz19lt6LGvH48E1rsPINAGxnyG7oE7-VzTqlE&e= in our internal backlog, so I don't think we'll be able to work on it in the near future. At this point, I would recommend not using MDCChipField and consider using an MDCTextField (or UITextField) and a collection view with Chips in it instead.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_material-2Dcomponents_material-2Dcomponents-2Dios_issues_8417-3Femail-5Fsource-3Dnotifications-26email-5Ftoken-3DAEEZPHC7X6L76X6EJM2KWMTQW6T5ZA5CNFSM4IUXPN32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEF46GOQ-23issuecomment-2D561636154&d=DwMCaQ&c=YEQWdgm3lcu5w_Y3fWOQZUGtAhl_lImuPlnxuD4zIqo&r=KOUdyUURgmdxf2WWvxPoqZOSMMY5IMBW7RmuJr9ro5E&m=7pPF-A3nzead6VU24EvhH8NXVnxCIwT2SQXH9Rvq2FI&s=XLMRvYiJ6A_m1vbPivDs125E6efbI2cCfYkNMVMJ3Uo&e=, or unsubscribehttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AEEZPHHUJVAR2H3DJPUEWBLQW6T5ZANCNFSM4IUXPN3Q&d=DwMCaQ&c=YEQWdgm3lcu5w_Y3fWOQZUGtAhl_lImuPlnxuD4zIqo&r=KOUdyUURgmdxf2WWvxPoqZOSMMY5IMBW7RmuJr9ro5E&m=7pPF-A3nzead6VU24EvhH8NXVnxCIwT2SQXH9Rvq2FI&s=YR0_hVcJYsDwH_5S4csQkEmY8yAGytMiLJz-jzF7FBY&e=.

---

Please be advised that this email may contain confidential information. If you are not the intended recipient, please notify us by email by replying to the sender and delete this message. The sender disclaims that the content of this email constitutes an offer to enter into, or the acceptance of, any agreement; provided that the foregoing does not invalidate the binding effect of any digital or other electronic reproduction of a manual signature that is included in any attachment.

[romoore]

Hi @anuragfluke. I can't provide any ETA, but given the relatively low position in our backlog I don't expect it to be worked on within the next 6 months, though that may change if our product management decides otherwise.

I don't have an example handy, and unless we began work on this issue, I don't think the team has enough capacity to try out a work-around for you. My suggestion would be to use a simple UICollectionView with MDCChipCollectionViewCell as the cell type and put that next to an MDCTextField or UITextField.