Jsdom: document.activeElement is always null after upgrading to jsdom 15/16 (jest 25)

Basic info:

We use jest tests with expect(document.activeElement).toBe(myElement) pattern to determine if an element got correctly focused after an interaction. After upgrading to jest 25 (jsdom 15) all such tests broke, document.activeElement appears to be always null. It is also the case if we run it using jsDom 16.

Jest team advised me to open an issue here.

• Node.js version: 10.19.0
• jsdom version: 15 and 16
• jest version: 25.1.0

Minimal reproduction case

import * as React from 'react';

it('should find active element', () => {
    const wrapper = mount(<input />);
    const inputNode = wrapper.find('input').getDOMNode();
    expect(document.activeElement).not.toBe(inputNode);
    inputNode.focus();
    expect(document.activeElement).toBe(inputNode); // fails here with expected being null
});

How does similar code behave in browsers?

Focused element should be reflected in document.activeElement