Skip to content
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][Smoke Test] [Multiline Input's boundary has disappeared] #5179

Closed
1 task
jwoo-msft opened this issue Dec 11, 2020 · 3 comments · Fixed by #5185
Closed
1 task

[iOS][Smoke Test] [Multiline Input's boundary has disappeared] #5179

jwoo-msft opened this issue Dec 11, 2020 · 3 comments · Fixed by #5185
Assignees
Labels
Area-Inconsistency Bugs around renderer inconsistencies across different platforms Bug High Priority Platform-iOS
Milestone

Comments

@jwoo-msft
Copy link
Member

Platform

What platform is your issue or question related to? (Delete other platforms).

  • iOS

Details

Upon submission of Input.Text multi-lines, its boundary disappears.
https://github.com/microsoft/AdaptiveCards/blob/main/samples/v1.0/Elements/AdaptiveCard.json
Simulator Screen Shot - iPhone 8 - 2020-12-11 at 15 10 02
Simulator Screen Shot - iPhone Xʀ - 2020-12-11 at 15 09 29

@jwoo-msft jwoo-msft added the Bug label Dec 11, 2020
@ghost ghost added this to the 21.01 milestone Dec 11, 2020
@ghost ghost added the Area-Inconsistency Bugs around renderer inconsistencies across different platforms label Dec 11, 2020
@ghost
Copy link

ghost commented Dec 11, 2020

please review this issue for target Milestone, Inconsistencies & Priority upon triage.

@ghost
Copy link

ghost commented Dec 12, 2020

Hi @jwoo-msft. We have acknowledged this issue report. Please continue to follow this issue for updates/progress/questions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Inconsistency Bugs around renderer inconsistencies across different platforms Bug High Priority Platform-iOS
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants