switch_to_window does not send Chrome's Target.activateTarget CDP command

[vdbijl]

We have a patch in our code that speeds up coming back to a window. See the code below.

When a spec switches away from a window and later switches back, Chrome's renderer for that window remains in a backgrounded state. CDP input commands (e.g. Input.dispatchMouseEvent) then stall for ~5 seconds while Chrome reactivates the renderer. This affects any spec that uses multiple windows.
Calling page.activate after switching sends Target.activateTarget, which wakes the renderer immediately. This reduces wait time, on some specs more than 10s.

We use the following patch.

 module CupriteActivateOnSwitch
  # Sends Target.activateTarget after switching, waking Chrome's renderer for the target window.
  # @return [true]
  def switch_to_window(target_id)
    super
    @page.activate
  end
end
Capybara::Cuprite::Browser.class_eval {prepend CupriteActivateOnSwitch}

[route]

thats interesting! do you think you can come up with a test to harden this behavior?

[vdbijl]

Thanks! I'll have a look at it. I cannot share the example that we have, so I'll have to cook something else. It might takes some time because of holidays.