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

Send button should not be disabled after reconnected #4706

Closed
compulim opened this issue Apr 13, 2023 · 0 comments · Fixed by #4707
Closed

Send button should not be disabled after reconnected #4706

compulim opened this issue Apr 13, 2023 · 0 comments · Fixed by #4707
Labels
bug Indicates an unexpected problem or an unintended behavior.

Comments

@compulim
Copy link
Contributor

Is it an issue related to Adaptive Cards?

No

Is this an accessibility issue?

No

What version of Web Chat are you using?

Development build

Which distribution are you using Web Chat from?

Unrelated

Which hosting environment does this issue primarily affect?

Web apps

Which browsers and platforms do the issue happened?

Browser: Edge (latest), Browser: Chrome (latest), Browser: Firefox (latest), Browser: Safari (latest), Browser: IE Mode (latest), Platform: Windows, Platform: macOS, Platform: iOS/iPadOS, Platform: Android

Which area does this issue affect?

Send box

What is the public URL for the website?

No response

Please describe the bug

When using DLASE, reconnection will emit ConnectionStatus.Connecting followed by ConnectionStatus.Online. These values are not observed in DLJS.

After reconnection completed, the useConnectivityStatus returns ["reconnected"], rather than ["connected"].

In our useSubmit() hook, we only check for "connected" but not "reconnected". Thus, after reconnection, useSubmit consider it is still offline and does not submit the send box.

Do you see any errors in console log?

No response

How to reproduce the issue?

  1. Navigate to https://compulim.github.io/webchat-loader/
  2. Use DLASE connection
  3. After Web Chat is loaded, disconnect the Internet and reconnect
  4. Type a message in the send box
  5. Click send button or press ENTER

What do you expect?

It should be able to send message after reconnected.

What actually happened?

The send button become non-functional after reconnected.

Do you have any screenshots or recordings to repro the issue?

No response

Adaptive Card JSON

No response

Additional context

No response

@compulim compulim added bug Indicates an unexpected problem or an unintended behavior. customer-reported Required for internal Azure reporting. Do not delete. Bot Services Required for internal Azure reporting. Do not delete. Do not change color. and removed customer-reported Required for internal Azure reporting. Do not delete. Bot Services Required for internal Azure reporting. Do not delete. Do not change color. labels Apr 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Indicates an unexpected problem or an unintended behavior.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant