-
Notifications
You must be signed in to change notification settings - Fork 563
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[iOS][Input validation] [Card UX issue : when error message is displayed on the card on button click] #4835
Comments
please review this issue for target Milestone, Inconsistencies & Priority upon triage. |
Hi @jyoti-ms. We have acknowledged this issue report. Please continue to follow this issue for updates/progress/questions. |
@shalinijoshi19 @dclaux @jwoo-msft We are facing this issue as we are upgrading to the latest SDK in Teams. Can you please triage and let us know how we can work around this. |
@jyoti-ms As we have discussed, SDK will send layout change notification. |
Thanks @jwoo-msft. yes, sending layout change notification on button click should work. |
🎉 Handy links: |
@sowrabh-msft FYI this issue has been addressed with our last patch. thanks |
Platform
What platform is your issue or question related to?
Author or host
Host - Teams iOS Client
Version of SDK
SDK 2.1.0 (Adaptive card v1.3)
Details
An error message is shown on the card when input validation check is not passed on submit button click.
SDK
send
method is not triggering anyonClick
event to the client whenever input validation failed and error messages are shown directly.In teams, we need to refresh the superview's layout (table view cell layout) that contains the adaptive card whenever error message is shown on the card as height of the adaptive card view has increased (changed by the SDK).
This is causing the UX to squeeze when user clicks on action.submit button. SDK is handling this right now and updating the layout for adaptive card only.
PFA screenshot:

The text was updated successfully, but these errors were encountered: