* 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.cc
const gfx::Rect& bounds) {
  if (changed_widget != widget())
    return;
  
  
  const auto new_bounds = GetBounds();
  if (widget_size_ != new_bounds.size()) {
    if (browser_view()) {
      const auto flags = static_cast<NativeBrowserViewViews*>(browser_view())
                             ->GetAutoResizeFlags();
      int width_delta = 0;
      int height_delta = 0;
      if (flags & kAutoResizeWidth) {
        width_delta = new_bounds.width() - widget_size_.width();
      }
      if (flags & kAutoResizeHeight) {
        height_delta = new_bounds.height() - widget_size_.height();
      }
      auto* view = browser_view()->GetInspectableWebContentsView()->GetView();
      auto new_view_size = view->size();
      new_view_size.set_width(new_view_size.width() + width_delta);
      new_view_size.set_height(new_view_size.height() + height_delta);
      view->SetSize(new_view_size);
    }
    NotifyWindowResize();
    widget_size_ = new_bounds.size();
  }
}
void NativeWindowViews::DeleteDelegate() {