Chrome Version: 67.0.3364.0 (Developer Build) (64-bit) Revision	248ce84359e18e425f774147d1de4bbeac9ebe27
OS: macOS Version 10.13.3 (Build 17D47)

What steps will reproduce the problem?
(1) Set a breakpoint on -[RenderWidgetHostViewCocoa resignFirstResponder]
(2) Open two tabs
(3) Switch between them

What is the expected result?
RenderWidgetHostViewCocoa from the deactivating tab should get -resignFirstResponder and the new tab should get -becomeFirstResponder.

What happens instead?
When I set a breakpoint in -[FramedBrowserWindow makeFirstResponder:] and activate a different tab, the current responder is a TabbedBrowserWindow, and a new one is a RenderWidgetHostViewCocoa.

When I set a regexp breakpoint on *resignFirstResponder* it only ever gets called for TabbedBrowserWindow. And it's a mystery how the firstResponder gets to TabbedBrowserWindow in the first place.

The fix for  crbug.com/818133  (https://chromium-review.googlesource.com/c/chromium/src/+/943064) is related to this bug: with that CL applied if you focus a password text field on one tab and switch to another, the secure input would still be enabled.