Chrome Version: Chrome stable 71, Chrome Dev 73
OS: Linux/Debian

## What steps will reproduce the problem?

(1) Go to: https://fullscreenchangetest.glitch.me
(2) Click the 'toggle fullscreen' button, note the h1 text change to 'is fullscreen', and hit ESCAPE to exit fullscreen and the h1 text change back to 'is not full screen'
(3) Open up devtools and start device emulation
(4) Click 'toggle fullscreen' and notice the whole tab go fullscreen, as the browser chrome is replaced by black bars, and the h1 text correctly updates to 'is fullscreen'.
(5) Now hit ESCAPE.

## What is the expected result?

When hitting ESCAPE during (5), I expect the content to exit fullscreen mode, fire `fullscreenchange`, and set `document.fullscreenElement` to null.

## What happens instead?

When hitting ESCAPE during (5), the browser exits fullscreen mode (browser chrome is now visible), but the DOM content still thinks its in fullscreen (h1 text is 'is fullscreen', and `document.fullscreenElement` is not null.

## Other

A colleague on OS X was not able to reproduce this issue. Note that clicking "toggle fullscreen" to programmatically exit fullscreen works as expected; it is only the user gesture (ESCAPE) that results in an unexpected state.