This repository has been archived by the owner on Dec 11, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 974
Fixed incorrect state found in tab.pinned #7440
Labels
Milestone
Comments
moving to 0.14.3 |
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
This actually already works with the detachable tabs merge. Closing and marking as 0.14.2. |
This was referenced Apr 13, 2017
bsclifton
removed
the
needs-owner ♞
This issue is tagged for an upcoming release but has no owner.
label
Apr 14, 2017
This was referenced Apr 21, 2017
alexwykoff
changed the title
Incorrect state found in tab.pinned
Fixed incorrect state found in tab.pinned
Apr 26, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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: