New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 661734 link

Starred by 10 users
Status: WontFix
Owner:
█ spqc...@chromium.org
Last visit > 30 days ago
Closed: May 2017
Cc:
erikc...@chromium.org
█ shrike@chromium.org
mac-bugs-priority@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: Bug

Blocking:
issue 660126
issue 680023



Sign in to add a comment

Investigate tracking which `NSTouchBarItem`s are visible

Project Member Reported by sdy@chromium.org, Nov 2 2016 
Possible subproject of  issue 660126 . Might be easy with KVO; NSTouchBarItem.h has this comment above its isVisible property:

"When YES, this item is attached to a visible touch bar, and is being displayed. Note that some types of items are never considered visible, for example spaces, other items proxys, and groups. This property is key value observable."

Similar (but a little more confusing), in NSTouchBar.h, for its isVisible property:

"When YES, the touch bar is attached to an eligible touch bar provider, and its items are displayable, assuming adequate space. This property is key value observable."

Comment 1 by sdy@chromium.org, Nov 2 2016 

The docs also mention using KVO to track the `touchBar` member of touch bar providers:

"Most responders provided by AppKit implicitly conform to the NSTouchBarProvider protocol and support key-value observing (KVO). You can take advantage of this KVO support to keep track of bar state, such as which items are visible as the user customizes and interacts with the Touch Bar."

(from https://developer.apple.com/reference/appkit/nstouchbar)

Comment 2 by spqc...@chromium.org, Jan 25 2017

Blocking: 680023

Comment 3 by shrike@chromium.org, Feb 9 2017

Blocking: 690611

Comment 4 by spqc...@chromium.org, Feb 11 2017

Components: -UI UI>Browser>Touchbar

Comment 5 by spqc...@chromium.org, Mar 9 2017

Owner: spqc...@chromium.org
Status: Assigned (was: Available)

Comment 6 by shrike@chromium.org, May 4 2017

Blocking: -690611

Comment 7 by shrike@chromium.org, May 4 2017 

Seems like we don't have to worry about this anymore? If we don't, let's close it.

Comment 8 by spqc...@chromium.org, May 4 2017

Status: WontFix (was: Assigned)
►

Sign in to add a comment