microsoft / microsoft/BotFramework-WebChat
New message is announced when a reorder of messages happens
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.8k
- Forks
- 1.6k
- Avg merge
- 22h 58m
- Merged PRs (30d)
- 2
Description
Is it an issue related to Adaptive Cards?
- Yes, this is an Adaptive Card issue but it is specific to Web Chat.
Do you have any screenshots?
What version of Web Chat are you using?
I am not using latest
Which distribution are you using Web Chat from?
Bundle (webchat.js)
Which hosting environment does this issue primarily affect?
Dynamics 365 Omnichannel
Which browsers and platforms do the issue happened?
Browser: Edge (latest), Browser: Chrome (latest), Browser: Safari (latest), Platform: Windows, Platform: macOS
Which area does this issue affect?
Notification
Is this an accessibility issue?
- Yes, this is an accessibility issue.
Please describe the bug
Adaptive cards are being sorted according to the time stamp in the activity, if the scroll of the chat is in the middle of the chat while the reorder happens, it will announce as new message ,
this is a problem when one of the adaptive cards contains a set of suggested actions, because once the ordering happens , the suggested actions dissapear.
this was reported by a customer by scrolling up and down multiple times.
Do you see any errors in console log?
No response
How to reproduce the issue?
1.- use a PVA bot which send at least 3 messages , one after other , the last message should contain a set of suggested actions
2.- start the chat, and wait for the suggested actions to show up
3.- scroll up and down
4.- once the suggested actions dissapear corroborate the order of the messages
this is not an easy bug to reproduce, since the re-order doesnt always happen,
What is the expected and actual behavior?
Expected:
to do not throw a new message notification under the scenario described
Actual:
is throwing a new message notifiation
Adaptive Card JSON
No response
Additional context
NA
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reported PVA bot reproduction steps and observe message reordering while scrolling, including the notification and suggested-actions behavior. The issue is resolved when reordering does not announce an existing message as new and the suggested actions remain available in the correct message order.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100