- From: Andreas Tolfsen <ato@mozilla.com>
- Date: Wed, 18 May 2016 18:25:39 +0100
- To: public-browser-tools-testing@w3.org
Sam Uong <samuong@google.com> writes: > On Wed, May 18, 2016 at 5:16 AM James Graham <james@hoppipolla.co.uk> > wrote: > > > On 18/05/16 13:06, Andreas Tolfsen wrote: > > > > > Related to Set Window Size directly, do we feel it is necessary to > > > add a provision to wait for the window to change its size before > > > returning? > > > > The window may never change its size e.g. if you have a tiling wm it > > may ignore windows' requests to change their own size. Or the size > > may change multiple times e.g. if there is a transition animation > > that exposes intermediate states to the window. > > > > In general I doubt we can make strong guarantees about the > > behaviour across different OSes here. For Servo we have considered > > implementing some logic to wait for a quiescent state in the window > > size e.g. no size changes recorded within 200ms, and then returning > > whatever the window size is at that point. In the case of the WM > > blocking the size change one would therefore incur a mandatory delay > > before this command returns. But I think it should be a rare enough > > command that making it super-performant isn't that important. > > We've also noticed that even when it does change size, it sometimes > changes to a size that is different from the one requested. This > happens when window managers clip windows to fit into the screen, > or when they decide that it is big enough that the user meant to > maximize. This is to be expected, and incidentally why the specification makes no guarantees that the window is the requested size when returning. Marionette contains such a check at the moment, but this is non-confirming behaviour and will be removed shortly.
Received on Wednesday, 18 May 2016 17:26:10 UTC