- Electron version: 0.37.6
- Operating system: Windows 10

In VSCode, in order to support screen readers while editing text, we set the contents of a `<textarea>` to the contents of the line and lines surrounding the cursor and we mirror the editor selection in the `<textarea>` via `setSelectionRange`.

Chromium is not the fastest when it comes to setting large amounts of text :) (such as > 10,000 characters) and basically stalls all the time. Apparently, Electron already has some knowledge about when a screen reader is attached to the main process window (in C++ code). Is it possible to expose this as a getter + event when it first happens in the `electron` API.

We could then maintain this costly `<textarea>` sync only when really needed.

atom/browser/native_window_views_win.cc
last_normal_bounds_ = GetBounds();
      } else {
        switch (last_window_state_) {
          case ui::SHOW_STATE_MAXIMIZED:
            last_window_state_ = ui::SHOW_STATE_NORMAL;
            
            
            SetBounds(last_normal_bounds_, false);
            NotifyWindowUnmaximize();
            break;
          case ui::SHOW_STATE_MINIMIZED:
            if (IsFullscreen()) {
              last_window_state_ = ui::SHOW_STATE_FULLSCREEN;
              NotifyWindowEnterFullScreen();
            } else {
              last_window_state_ = ui::SHOW_STATE_NORMAL;
              
              
              SetBounds(last_normal_bounds_, false);
              NotifyWindowRestore();
            }
            break;
        }
      }
      break;
  }
}
}