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

chrome.tabs.query returns main Brave frame #8822

Closed
jonathansampson opened this issue May 10, 2017 · 1 comment
Closed

chrome.tabs.query returns main Brave frame #8822

jonathansampson opened this issue May 10, 2017 · 1 comment
Assignees

Comments

@jonathansampson
Copy link
Collaborator

jonathansampson commented May 10, 2017

  • Did you search for similar issues before submitting this one?
    Yes

  • Describe the issue you encountered:
    The chrome.tabs.query method returns the main Brave application frame in its results.

  • Platform (Win7, 8, 10? macOS? Linux distro?):
    Desktop

  • Brave Version (revision SHA):
    4e86cab

  • Steps to reproduce:

  1. Open the developer tools on about:extensions
  2. Run chrome.tabs.query({}, t => console.dir(t))
  • Actual result:
    …/app.asar/app/extensions/brave/index.html is included in the results.

  • Expected result:
    The results only include browser tabs.

  • Will the steps above reproduce in a fresh profile? If not what other info can be added?
    Yes

  • Is this an issue in the currently released version?
    Yes

  • Can this issue be consistently reproduced?
    Yes

  • Any related issues:
    Extension API: chrome.tabs.query #8811

@jonathansampson
Copy link
Collaborator Author

Some queryInfo arrangements will return the Brave frame, while others will not. For instance, if you limit the results only to pinned tabs, the Brave frame will not be returned. If you limit it to audible tabs, the Brave frame will be returned (in additional to any audio-producing tabs).

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

No branches or pull requests

2 participants