Couple of changes for client area

Couple of changes for client area

Makes DesktopWindowTreeHostMus update the client area on the server
any time the bounds change.
Makes DesktopNativeWidgetAura not update the
transparency and fills-bounds-completely of the content_window_. This
way DesktopNativeWidgetAura won't fill the client area and you can see
the client decorations from the window manager. Also
DesktopWindowTreeHostMus makes sure to mark the content_window_ layer
as not fills bounds opaquely for same reason.
Lastly makes it so the client that changes the client area isn't told
about the change, and a bit of logging that fits in with other logging
in the file.

BUG=664625
663525
TEST=none
R=erg@chromium.org

Committed: https://crrev.com/2e855ae5b7a081bc374880e100fe4b00887c0f48
Cr-Commit-Position: refs/heads/master@{#435696}

[sky, 2016-12-01 19:18:23]

The CQ bit was checked by sky@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-12-01 19:19:07]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[Elliot Glaysher, 2016-12-01 19:21:24]

lgtm

https://codereview.chromium.org/2535753009/diff/20001/ui/views/mus/desktop_wi...
File ui/views/mus/desktop_window_tree_host_mus.cc (right):

https://codereview.chromium.org/2535753009/diff/20001/ui/views/mus/desktop_wi...
ui/views/mus/desktop_window_tree_host_mus.cc:139: // be called after window size
changed.
I believe you can kill this todo now.

[sky, 2016-12-01 19:23:58]

https://codereview.chromium.org/2535753009/diff/20001/ui/views/mus/desktop_wi...
File ui/views/mus/desktop_window_tree_host_mus.cc (right):

https://codereview.chromium.org/2535753009/diff/20001/ui/views/mus/desktop_wi...
ui/views/mus/desktop_window_tree_host_mus.cc:139: // be called after window size
changed.
On 2016/12/01 19:21:24, Elliot Glaysher wrote:
> I believe you can kill this todo now.

Done.

[sky, 2016-12-01 19:24:02]

The CQ bit was checked by sky@chromium.org

[sky, 2016-12-01 19:24:03]

The patchset sent to the CQ was uploaded after l-g-t-m from erg@chromium.org
Link to the patchset: https://codereview.chromium.org/2535753009/#ps40001
(title: "nuke todo")

[commit-bot: I haz the power, 2016-12-01 19:24:49]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-12-01 20:19:37]

CQ is committing da patch.

Bot data: {"patchset_id": 40001, "attempt_start_ts": 1480620242876890,
"parent_rev": "6a62305c086e06d9db62d9993a974c6ec9b5b065", "commit_rev":
"ec07fdb9189105066402c971eb5079231f1b5654"}

[commit-bot: I haz the power, 2016-12-01 20:20:02]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2016-12-01 20:22:26]

Description was changed from

==========
Couple of changes for client area

Makes DesktopWindowTreeHostMus update the client area on the server
any time the bounds change.
Makes DesktopNativeWidgetAura not update the
transparency and fills-bounds-completely of the content_window_. This
way DesktopNativeWidgetAura won't fill the client area and you can see
the client decorations from the window manager. Also
DesktopWindowTreeHostMus makes sure to mark the content_window_ layer
as not fills bounds opaquely for same reason.
Lastly makes it so the client that changes the client area isn't told
about the change, and a bit of logging that fits in with other logging
in the file.

BUG=664625 663525
TEST=none
R=erg@chromium.org
==========

to

==========
Couple of changes for client area

Makes DesktopWindowTreeHostMus update the client area on the server
any time the bounds change.
Makes DesktopNativeWidgetAura not update the
transparency and fills-bounds-completely of the content_window_. This
way DesktopNativeWidgetAura won't fill the client area and you can see
the client decorations from the window manager. Also
DesktopWindowTreeHostMus makes sure to mark the content_window_ layer
as not fills bounds opaquely for same reason.
Lastly makes it so the client that changes the client area isn't told
about the change, and a bit of logging that fits in with other logging
in the file.

BUG=664625 663525
TEST=none
R=erg@chromium.org

Committed: https://crrev.com/2e855ae5b7a081bc374880e100fe4b00887c0f48
Cr-Commit-Position: refs/heads/master@{#435696}
==========

[commit-bot: I haz the power, 2016-12-01 20:22:27]

Patchset 3 (id:??) landed as
https://crrev.com/2e855ae5b7a081bc374880e100fe4b00887c0f48
Cr-Commit-Position: refs/heads/master@{#435696}