Some security checks around destruction/setting bounds.

Some security checks around destruction/setting bounds.

. validate on the client that the node can only be deleted or have its bounds changed by the connection that created the node. note that it's still possible for the client to call the interface directly, but the service will validate also, and then the client's inconsistent state is the client's own fault.
. pass bounds through the INodes array

R=sky@chromium.org
http://crbug.com/365012

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=273116

[sky, 2014-05-23 13:16:28]

LGTM

https://codereview.chromium.org/296133012/diff/1/mojo/services/public/cpp/vie...
File mojo/services/public/cpp/view_manager/lib/view_tree_node.cc (right):

https://codereview.chromium.org/296133012/diff/1/mojo/services/public/cpp/vie...
mojo/services/public/cpp/view_manager/lib/view_tree_node.cc:184: bool
CanMutateNode(ViewManager* manager, ViewTreeNode* node) {
Maybe this should be named OwnedNode since some mutations are still allowed for
nodes from other connections.

https://codereview.chromium.org/296133012/diff/1/mojo/services/view_manager/n...
File mojo/services/view_manager/node.h (right):

https://codereview.chromium.org/296133012/diff/1/mojo/services/view_manager/n...
mojo/services/view_manager/node.h:42: gfx::Rect bounds() const { return
window_.bounds(); }
const gfx::Rect&

[Ben Goodger (Google), 2014-05-27 18:02:29]

The CQ bit was checked by ben@chromium.org

[commit-bot: I haz the power, 2014-05-27 18:03:39]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/ben@chromium.org/296133012/60001

[commit-bot: I haz the power, 2014-05-27 22:48:54]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  win_chromium_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/win_chromium_rel/buil...)

[commit-bot: I haz the power, 2014-05-28 02:42:27]

Change committed as 273116