-
Notifications
You must be signed in to change notification settings - Fork 10.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
Documentation: closeOnBeforeUnload #4770
Labels
documentation
Improvements or additions to documentation
Comments
christopherreay
added
the
to triage
Waiting to be triaged by a member of the team
label
Jul 17, 2023
darrachequesne
added a commit
to socketio/socket.io-website
that referenced
this issue
Aug 4, 2023
Hi! I have updated the documentation for the Could you please check if that's clearer now? |
darrachequesne
added
documentation
Improvements or additions to documentation
and removed
to triage
Waiting to be triaged by a member of the team
labels
Aug 4, 2023
Hey,
thank you for taking the time to respond :)
I think it is clearer, yes. To my mind it is still written in double
negatives, and would be clearer if it explained exactly what events are
emitted when.
tyty
Christopher Reay (they / them)
Be prepared to have your predictions come true
…On Thu, 3 Aug 2023 at 17:26, Damien Arrachequesne ***@***.***> wrote:
Hi! I have updated the documentation for the closeOnBeforeUnload option:
https://socket.io/docs/v4/client-options/#closeonbeforeunload
Could you please check if that's clearer now?
—
Reply to this email directly, view it on GitHub
<#4770 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAB2PPRBGRYTH334IIE2WIDXTQ6VFANCNFSM6AAAAAA2MKACCE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
darrachequesne
added a commit
to socketio/socket.io-website
that referenced
this issue
Aug 4, 2023
@christopherreay thanks for your feedback 🙏 I've added a screenshot for both cases. I think we can now close this, please reopen if needed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
description of operation of function is unclear
https://socket.io/docs/v4/client-options/#closeonbeforeunload
To Reproduce
Read docs for the function
Expected behavior
Describing things only in terms of negatives leaves the developer unsure of what actually is happening.
With
closeOnBeforeUnload
set tofalse
disconnect
event to be emitted by the Socket instance when the user reloads the pageclose
event to be emitted by the Socket instanceWith
closeOnBeforeUnload
set totrue
disconnect
event when reloading the page)close
event to be emitted by the Socket instancebeforeunload
independently in your application code.Platform:
n/a
Additional context
The text was updated successfully, but these errors were encountered: