electron/atom
Birunthan Mohanathas 7d2226e05e Let Chromium manage document.visibilityState and document.hidden
Chromium already includes the necessary plumbing to manage the
visibility properties and `visibilitychange` event so this gets rid of
most of our custom logic for `BrowserWindow` and `BrowserView`.

Note that `webview` remains unchanged and is still affected by the issues
listed below.

User facing changes:

- The `document` visibility properties and `visibilitychange` event are
  now also updated/fired in response to occlusion changes on macOS. In
  other words, `document.visibilityState` will now be `hidden` on macOS
  if the window is occluded by another window.

- Previously, `visibilitychange` was also fired by *both* Electron and
  Chromium in some cases (e.g. when hiding the window). Now it is only
  fired by Chromium so you no longer get duplicate events.

- The visiblity state of `BrowserWindow`s created with `{ show: false }`
  is now initially `visible` until the window is shown and hidden.

- The visibility state of `BrowserWindow`s with `backgroundThrottling`
  disabled is now permanently `visible`.

This should also fix #6860 (but not for `webview`).
2017-06-06 15:16:01 -07:00
..
app Remove unsupported debugger in node processes 2017-05-11 15:02:27 -07:00
browser Let Chromium manage document.visibilityState and document.hidden 2017-06-06 15:16:01 -07:00
common Remove unused customWindowButtons switch 2017-06-05 13:57:25 -07:00
node Use v8::ArrayBuffer::Allocator inside Node 2017-05-18 16:26:46 +09:00
renderer move popup related code to nativewindow 2017-05-26 03:39:36 +02:00
utility Restore delivering IPC messages to utility handlers 2017-04-04 20:40:57 -07:00
CPPLINT.cfg