Also, note that in general, I can't figure out a way to resize the omnibox with keyboard only -- I only see how to do this by dragging the mouse. We should figure out a keyboard-only equivalent. Separate issue, but wanted to at least mention. 

Devlin, any thoughts on who could take this focus indication issue on? 

Yes, the extension overflow menu on mac is... terrible :(  There is no keyboard highlight indication, and the keyboard navigation is unintuitive, and likely broken.  Unfortunately, this is because of Mac's (lack of) support for custom views in a menu, and we have very little control over this.  I've talked with tapted@ and ellyjones@ about it in the past to see if there's any good way we can do this, and we couldn't come up with any.  +also karandeepb@ and sdy@ in case they have ideas.

There are two possible paths forward, I think:
- Make the entire wrench menu a custom view.  This is what we do for bookmark folders on mac.  Everyone I've talked with about this totally hates this idea, because the bookmark folders break constantly and are crazy-complicated.
- Make the wrench menu use MacViews.  This is the best solution, I think, and would solve all the problems (since none of these issues exist on Views).  Unfortunately, last I heard, menus were slated to be one of the last things converted. :(

> Also, note that in general, I can't figure out a way to resize the omnibox with keyboard only -- I only see how to do this by dragging the mouse. We should figure out a keyboard-only equivalent. Separate issue, but wanted to at least mention.

This is achievable (slowly) by using the context menu to hide/show specific extensions, which is keyboard-accessible.

Assigning to @tapted assuming that we'll solve this as part of MacViews if not sooner.

Note that the Zoom and Cut/Copy/Paste controls are similarly not keyboard-accessible.

We're not moving away from native menus for MacViews, so this won't come for free with anything that's in my queue. This is incomplete feature work - an Extensions person should own this.

Perhaps BrowserActionCell just needs to draw a focus ring manually using code like what's at https://developer.apple.com/library/content/documentation/Cocoa/Conceptual/ControlCell/Articles/ManipulateCellControl.html#//apple_ref/doc/uid/TP40002338-SW5

Ah, except, getting the key events needs some tricks too. I started hacking a bit on  Issue 696234  -- seems feasible.

Yes - if we can intercept the key events and receive focus, then drawing the focus ring is totally doable.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

MacViews has fixed this (yay!)