Skip to content
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.

Add test for new tab activation #9178

Closed
bsclifton opened this issue May 31, 2017 · 1 comment · Fixed by #9179
Closed

Add test for new tab activation #9178

bsclifton opened this issue May 31, 2017 · 1 comment · Fixed by #9179

Comments

@bsclifton
Copy link
Member

Tests for code introduced with 0391096

@bsclifton
Copy link
Member Author

NOTE: this is a follow up for:
1a76ade
and
0338a03

bsclifton added a commit that referenced this issue May 31, 2017
bsclifton added a commit that referenced this issue Jun 1, 2017
Fixes #9178

During this process, three issues were found/fixed:
- window was not being checked if truthy when closed
- tab close action NEXT was not being respected
- because getNextTabIdByIndex searches forward and backwards, the setting to first block was dead code (and was removed)
bsclifton added a commit that referenced this issue Jun 1, 2017
Fixes #9178

During this process, three issues were found/fixed:
- window was not being checked if truthy when closed
- tab close action NEXT was not being respected
- because getNextTabIdByIndex searches forward and backwards, the setting to first block was dead code (and was removed)
@bsclifton bsclifton added this to the 0.18.x milestone Jun 5, 2017
bsclifton added a commit that referenced this issue Jun 16, 2017
Fixes #9178

During this process, three issues were found/fixed:
- window was not being checked if truthy when closed
- tab close action NEXT was not being respected
- because getNextTabIdByIndex searches forward and backwards, the setting to first block was dead code (and was removed)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant