- 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/browser.cc
: is_quiting_(false),
      is_exiting_(false),
      is_ready_(false),
      is_shutdown_(false) {
  WindowList::AddObserver(this);
}
Browser::~Browser() {
  WindowList::RemoveObserver(this);
}
Browser* Browser::Get() {
  return AtomBrowserMainParts::Get()->browser();
}
void Browser::Quit() {
  if (is_quiting_)
    return;
  is_quiting_ = HandleBeforeQuit();
  if (!is_quiting_)
    return;
  atom::WindowList* window_list = atom::WindowList::GetInstance();
  if (window_list->size() == 0)
    NotifyAndShutdown();
  window_list->CloseAllWindows();
}
void Browser::Exit(int code) {