diff options
| author | derat@chromium.org <derat@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-11-23 00:43:51 +0000 |
|---|---|---|
| committer | derat@chromium.org <derat@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-11-23 00:43:51 +0000 |
| commit | ebc335f384af41ec5b919588a9217253073dc299 (patch) | |
| tree | 30b51570ed1125f6ab3b24fb53cac0e3f497de79 /ui/gfx/empty.cc | |
| parent | d1d672d4ac6331bdc659bdff4570a91adea23ab6 (diff) | |
| download | chromium_src-ebc335f384af41ec5b919588a9217253073dc299.zip chromium_src-ebc335f384af41ec5b919588a9217253073dc299.tar.gz chromium_src-ebc335f384af41ec5b919588a9217253073dc299.tar.bz2 | |
Make Aura and compositor stacking methods more intuitive.
aura::Window::StackChildAbove() and ui::Layer::StackAbove()
stacked entity A directly above entity B... unless A was
already somewhere above B in the stack, in which case they'd
do nothing. I see the caveat as making these methods less
useful, and I'm unable to think of any benefits from it, so
this change makes the methods place A directly above B in
all cases (possibly lowering A in the stacking order if it
was previously far above B).
This also fixes an issue in the Aura shell's shadow-stacking
code where ShadowController could inadvertently raise a
window to the top of the stacking order.
BUG=101977
TEST=added
Review URL: http://codereview.chromium.org/8653005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@111264 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'ui/gfx/empty.cc')
0 files changed, 0 insertions, 0 deletions