Mike Wasserman

Indeed, see supportive statements in this [related comment thread](https://github.com/whatwg/fullscreen/pull/153#issuecomment-1315231480) on the PR adding user activation consumption to requestFullscreen. IMO, it seems totally reasonable to grant fullscreen element changes without user...

It's okay to close this issue for now, and folks can reopen it if the need arises. The original motivation was moving a fullscreen element to another display of the...

Sorry, I don't know offhand why Electron wouldn't respect cross-display fullscreen; please link the Electron issue you file here. You mention that it always targets "the primary display", but I'm...

I tried this on Mac with your fiddle and Electron v15.0.0-beta.6 and had the same result. Interestingly, cross-screen window.open() bounds seem to work as intended.

The `window.getScreenDetails()` API entrypoint (and permission) is not implemented on Chrome for Android right now. Perhaps the IDL for ScreenDetailed (etc?) is defined in those builds, but `"version_added": false` seems...

Chromium issue https://issues.chromium.org/u/1/issues/331370720 GH spec issue https://github.com/w3c/window-management/issues/144

Hey @foolip, please help start review of this PR, thanks! Chrome's [initial usage](https://chromestatus.com/feature/6218822004768768) is notably limited in extent, but a change like this could serve a long tail of [use...

Hey @foolip, friendly ping. Thanks in advance for sharing any feedback here, or in other channels, and looping in others.

Hey @domenic, I see you've reviewed some recent PRs in this spec, would you mind taking a first look here? Thanks!

Thanks for taking a look! Chromium implements this with a [new content setting](https://chromestatus.com/feature/6218822004768768): chrome://settings/content/automaticFullScreen It is blocked by default, the default setting cannot be modified, but individual origins can be...