Version: 62

When the user presses Ctrl+Tab, an accessibility focus event is fired on a menu button, even though it does not actually have focus (the new tab has content that is focused). Occasionally a screen reader will read the button before reading what is actually focused, although this is intermittent. It would be better to fire focus events only what actually has focus.

The code that causes this behavior is
View::AdvanceFocusIfNecessary() called by
View::SetFocusBehavior() called by
WebView::SetWebContents()

It's unclear to me why that particular button gets focus. The code was added by @mohsen  in  bug 323956 
Review URL: https://codereview.chromium.org/108063004

I'm skeptical about changing something so core, but it would be good to understand the reasoning behind focusing this button.