-
Notifications
You must be signed in to change notification settings - Fork 5
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
Widget msgs bug: a negative bye confirmation would not disable past widgets of the same kind #71
Comments
This one has low priority for now. |
Another potential solution is to have a token that is generated by the server for each widget message. |
This is for widget chatbot messages that display options (e.g., screenshots) that the user should select.
When the user says no to a bye confirmation of the chatbot, right after a widget message is displayed, the chatbot will display the same widget message (i.e., the new message); however, the past widget would not be disabled, which means the user can still select options from it, and this can cause errors in the conversation flow.
We can reproduce this by saying bye after the list of apps are shown for selection, then, we can see that both widget messages (listing the apps) are enabled, so I can use any and the other one will remain enabled (it shouldn't, it should be disabled).
One possible solution is to disable the past widget message in the react front end. However, I am not sure how to do this in react.
The text was updated successfully, but these errors were encountered: