-
Notifications
You must be signed in to change notification settings - Fork 49
Only respect prevent argument until connected #31
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
base: master
Are you sure you want to change the base?
Only respect prevent argument until connected #31
Conversation
Once we're connected, either explicitly or due to to the button click, we should no longer respect the prevent option or reconnect when it cycles.
@petervo Could you review? |
@petervo: Friendly ping, to unblock cockpit-project/cockpit#7687 ? |
@martinpitt I don't have merge permissions here. But i'm fine with changes |
Neither have I. It's surprisingly difficult to determine who actually has push privs in a GitHub project.. |
@@ -105,6 +105,9 @@ | |||
var defaultCols = 80; | |||
var defaultRows = 24; | |||
|
|||
/* Whether the component is preventing a connection */ | |||
var preventing = true; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The change looks fine, but the var name is a bit confusing (particularly because we have a scope var called prevent
). Can we call this something like connectionRequested
or overridePrevent
and flip the logic? I think it would make the intent more clear.
Once we're connected, either explicitly or due to to the button
click, we should no longer respect the prevent option or reconnect
when it cycles.