Skip to content
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

Split screen tab is not found #104

Open
daveodonnell opened this issue Aug 23, 2023 · 3 comments
Open

Split screen tab is not found #104

daveodonnell opened this issue Aug 23, 2023 · 3 comments
Assignees
Labels
Bug the issue is a code defect that should be fixed Waiting for more info more information is needed and the reporter was at-mentioned.

Comments

@daveodonnell
Copy link

daveodonnell commented Aug 23, 2023

After creating a split screen tab, the new tab on the right does not appear in the all tabs query.
Sending a message from the split screen tab to the service worker, and looking at sender.tab will get information about the tab (Id, URL, etc) but that seems to be the only way that the service worker can know the tab exists.

Using
chrome.tabs.query({ }, function(tabs){
for(i = 0; i < tabs.length; i++){
console.log(tabs[i].id);
console.log(tabs[i].url);
}
Will not get the ID or URL of the split screen tab on the right

Is there any way that a service worker can correctly find the split screen tab, without waiting for a message from the content script?

The extension that we work on requires that we know the list of all currently opened tabs in the service worker

@ManikanthMSFT
Copy link
Collaborator

Hi @daveodonnell, we apologize for the delay in addressing the issue.

Could you please confirm if the issue is resolved?

@ManikanthMSFT ManikanthMSFT self-assigned this Jun 11, 2024
@sivMSFT sivMSFT added Bug the issue is a code defect that should be fixed Waiting for more info more information is needed and the reporter was at-mentioned. labels Jun 11, 2024
@daveodonnell
Copy link
Author

daveodonnell commented Jun 11, 2024 via email

@ManikanthMSFT
Copy link
Collaborator

@daveodonnell, thank you for the confirmation. We are looking into this and will notify you as soon as we have an update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug the issue is a code defect that should be fixed Waiting for more info more information is needed and the reporter was at-mentioned.
Projects
None yet
Development

No branches or pull requests

3 participants