microsoft / microsoft/BotFramework-WebChat
When the cognitive speech is enabled, the normal send button disappears
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.8k
- Forks
- 1.6k
- Avg merge
- 22h 58m
- Merged PRs (30d)
- 2
Description
Is your feature request related to a problem?
yes, I want that when user comes to our bot they see the mic button but when they start to type mic button should be changed to the send button or there should be a separate mic and send buttons for the typing box.
Describe the suggestion or request in detail
Initial State: When the user first accesses the chat interface, they see a microphone button. This suggests that the primary input method is voice.
Transition State: As soon as the user starts typing in the text input box, the microphone button dynamically changes into a send button. This indicates to the user that they can now send their message via text input.
Separate Buttons Option: Alternatively, instead of dynamically changing the mic button to a send button, you could also provide separate mic and send buttons next to the text input box. This would allow users to choose between voice input and text input more explicitly.
Describe alternatives you have considered
No response
Additional context
No response
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
No file, test, or entry point is named; start by locating the chat input controls and the cognitive speech microphone/send-button logic. Reproduce the initial voice-input state and typing transition, then verify that typing exposes a usable send action while preserving the intended microphone behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100