We built a tool, Oh no! Reflow![1], to detect synchronous reflows that occur in the browser. This was useful to help us detect the most egregious cases where sync reflow occur. It'd be good if we could get a sense of how much sync reflow is happening out in the wild now as well, so that we can get a better sense of how we should prioritize addressing them. Ideally, we'd capture: 1) At least the top-most stack frame of the reflow 2) Perhaps how long the reflow took (although if there's wide variation on this measurement, it's utility is debatable) 3) How many times the reflow occurred