Layout markers in performance tool have locations when it's a synchronous
reflow, seen in this[0] example, within some JS marker, whereas async
reflows doesn't display the reason the layout was invalidated on previous
frames, which looks similar to the console reflow logs, some being sync,
some being async:
```
reflow: 0.03ms function go, sync-reflow.html line 27
reflow: 0.23ms function go, sync-reflow.html line 27
reflow: 0.04ms
reflow: 0.27ms
```
[0]
http://jsantell.github.io/browser-render-pipeline/sync-reflow.html
On Wed, Aug 17, 2016 at 12:46 AM, Jaroslav Šnajdr <
jsn...@gmail.com> wrote:
> Another difference between the two features is that the console reflow
> logging shows you the JS location that triggered the reflow (i.e., setting
> element size or changing a style from JS), while the "Layout" marker in the
> performance timeline doesn't. Or maybe it does if you enable some checkbox,
> but I didn't find anything like that.
>
> Jarda
>
> On Tue, Aug 16, 2016 at 10:04 PM, Brian Grinstead <
bgrin...@mozilla.com>