* Output of `node_modules/.bin/electron --version`: 2.0.0
* Operating System (Platform and Version): Windows 10

**Expected Behavior**
When I disable a window twice via `setEnabled(false)`, I expect the second disable to have no effect.

**Actual behavior**
The second disable is "queued" up, such that I am forced to enable the window twice to get back to normal.

**To Reproduce**
In the electronquickstart repo, in main.js' `createWindow()`, add these lines:

    mainWindow.setEnabled(false);
    mainWindow.setEnabled(false);
    mainWindow.setEnabled(true);

The window will be disabled when launched. 

You see the same issue if you do it in reverse:

    mainWindow.setEnabled(true);
    mainWindow.setEnabled(false); // this doesn't actually disable it, because the window was enabled from the getgo

If this is expected behavior, can the [docs](https://github.com/electron/electron/blob/master/docs/api/browser-window.md#winsetenabledenable) be updated to explain this behavior.
atom/browser/native_window_views.h
std::unique_ptr<EventDisabler> event_disabler_;
#endif
#if defined(OS_WIN)
  
  AtomDesktopWindowTreeHostWin* atom_desktop_window_tree_host_win_;
  ui::WindowShowState last_window_state_;
  
  
  
  
  gfx::Rect last_normal_bounds_;
  gfx::Rect last_normal_bounds_before_move_;
  
  
  
  
  
  
  gfx::Rect last_normal_bounds_candidate_;
  bool consecutive_moves_;
  
  TaskbarHost taskbar_host_;
  
  bool checked_for_a11y_support_ = false;
  
  bool thick_frame_ = true;
  
  gfx::Rect restore_bounds_;