Fixed issue where adaptive card inputs were being reset. #1681
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #1680
===
The root cause is that when an activity is clicked on, it fires off both highlight activity & set inspector objects actions that then modify the chat document in the store.
This change in the store causes the
chat.tsx
component to re-render and the entire Web Chat control with it, which wipes the state of input fields within adaptive cards.Preventing that re-render from happening seems like a very hard problem, if not impossible, given our current DOM structure.
The fix here is to intercept clicks & keydown events within activities, check if they originated within an input field, and prevent the highlight and select activity actions from being fired.