You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.
Did you search for similar issues before submitting this one?
Yes
Describe the issue you encountered:
When querying tab objects via the chrome.tabs API, the pinned property does not accurately communicate whether or not a tab is presently pinned.
Platform (Win7, 8, 10? macOS? Linux distro?):
Desktop
Brave Version (revision SHA):
0.13.4
Steps to reproduce:
Navigate to, and pin, about:extensions
Press Ctrl+Shift+I to open the developer tools, switch to Console
Run chrome.tabs.getCurrent(tab => console.log(tab.pinned))
Actual result:
The pinned value is false.
Expected result:
The pinned value should be true.
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
The text was updated successfully, but these errors were encountered:
bsclifton
added
needs-owner ♞
This issue is tagged for an upcoming release but has no owner.
and removed
needs-owner ♞
This issue is tagged for an upcoming release but has no owner.
labels
Apr 7, 2017
Did you search for similar issues before submitting this one?
Yes
Describe the issue you encountered:
When querying tab objects via the
chrome.tabs
API, thepinned
property does not accurately communicate whether or not a tab is presently pinned.Platform (Win7, 8, 10? macOS? Linux distro?):
Desktop
Brave Version (revision SHA):
0.13.4
Steps to reproduce:
chrome.tabs.getCurrent(tab => console.log(tab.pinned))
Actual result:
The
pinned
value isfalse
.Expected result:
The
pinned
value should betrue
.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
The text was updated successfully, but these errors were encountered: