Skip to content

Conversation

@grouma
Copy link
Member

@grouma grouma commented Apr 15, 2019

Closes #271

@grouma grouma requested a review from jakemac53 April 15, 2019 21:48
var chrome = await Chrome.connectedInstance;
await chrome.close();
await _appDebugServices.debugService.chromeProxyService.tabConnection
.close();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just to clarify, does this only close the application tab?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also what happens if the tab is already closed?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This only closes the tab. In the case that we launch Chrome the resulting chrome process will be killed. The tab can't already be closed because closing the tab results in the daemon shutting down.

@grouma grouma merged commit 4936532 into master Apr 17, 2019
@grouma grouma deleted the close-daemon branch April 17, 2019 00:28
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.

Closing the browser should stop the daemon

2 participants