Mus+Ash: We should probably clip windows to their parent's bounds by default |
||||||||
Issue descriptionRight now we don't do any clipping in the Mus window server. We should probably turn on clipping by default (except maybe for transient windows?) so that the child client area does not stick outside the bounds of the parent (eg Chrome renderer sticking outside the bounds of the Chrome window).
,
Sep 13 2016
I don't believe we clip by default with aura::Windows (or rather ui::Layer). But we may want to for embedded windows, such as renderers.
,
Sep 15 2016
Mus-gpu needs a way to clip an oopif to the clip prop tree provided by the embedder. I think we could reuse this mechanism for clip if the ws generated such a clip prop tree? BTW: how do popups currently work? i.e. if an oopif has a combo box? Does it ask the browser to make the unclipped window for the combo-box.
,
Sep 15 2016
I suspect the browser ends up handling popups so that they aren't clipped by frames. I'm not positive though.
,
Sep 16 2016
,
Oct 4 2016
,
Nov 27 2016
Once we complete surface ID propagation, clipping will happen in the parent client.
,
Jan 23 2017
,
Feb 28 2017
Now that we do surface ID propagation, I feel like this bug is obsolete. Marking as WontFix.
,
Feb 26 2018
,
Feb 26 2018
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by rjkroege@chromium.org
, Sep 13 2016