Skip to content

Conversation

stefwalter
Copy link
Contributor

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.

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.
@stefwalter
Copy link
Contributor Author

@petervo Could you review?

@martinpitt
Copy link
Contributor

@petervo: Friendly ping, to unblock cockpit-project/cockpit#7687 ?

@petervo
Copy link

petervo commented Dec 6, 2017

@martinpitt I don't have merge permissions here. But i'm fine with changes

@martinpitt
Copy link
Contributor

Neither have I. It's surprisingly difficult to determine who actually has push privs in a GitHub project..

@martinpitt
Copy link
Contributor

@spadgett , @jwforres, could you please have a look at this? Thanks!

@@ -105,6 +105,9 @@
var defaultCols = 80;
var defaultRows = 24;

/* Whether the component is preventing a connection */
var preventing = true;
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants