I filed both of the issues discussed on this thread: https://github.com/servo/servo/issues/3187 https://github.com/servo/servo/issues/3188
Cameron On Aug 28, 2014, at 7:20 PM, Patrick Walton <pwal...@mozilla.com> wrote: > I believe the answer today is "nothing"--i.e. it's a Servo bug. Clark's work > doubles as a nice way to fix it :) > > Patrick > > On August 28, 2014 7:18:27 PM PDT, Robert O'Callahan <rob...@ocallahan.org> > wrote: > On Fri, Aug 29, 2014 at 2:10 PM, Patrick Walton <pwal...@mozilla.com> wrote: > It might happen if layout is flushed from outside the script task; window > resizing/device rotation being what immediately comes to mind, as today in > Servo those events go straight from compositor to layout without hitting the > script task at all. (As an alternative design, we could route such events > through the script task; this would remove the necessity of the mutex but > would block layout for such events if script is running, even if the script > hasn't touched the DOM.) > > Hmm. So given > > var v = e.getBoundingClientRect(); > // layout change is triggered by window resizing or whatever > var v2 = e.getBoundingClientRect(); > > what in Servo, prior to Clark's work, ensures v and v2 are the same? > > Rob > > -- > Sent from my Android phone with K-9 Mail. Please excuse my brevity. _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
