-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Reconnect feature is missing when websocket connection is closed. #1852
Labels
Needs Clarification
Requires additional input
Comments
fix on #1851 |
12 tasks
The PR does not solve this issue. Also I think this is a non-issue. See PR review. I vote for closing this issue as 'wontfix'. |
@levino @nujabes403 |
12 tasks
I'm closing this PR because of the PR #1966 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected behavior
After websocket connection is closed, it should try reconnecting.
Actual behavior
After websocket connection is closed, it doesn't do anything except notifying "connection is closed".
Steps to reproduce the behavior
Try offline mode on chrome developer tool.
Versions
npm 5.6.0
node 8.11.3
web3js 1.0.0.beta-35
OS X high sierra
The text was updated successfully, but these errors were encountered: