Awhile back, Google's Paul Lewis made a page listing all CSS triggers for Chrome[0], mapping CSS property changes to whether or not they caused paint, reflow and compositing. We initially had some data for this from the devtools timeline/profiler on this, and they're going through an effort to add other browsers' data to the page as well. Right now they're using some of our outdated marker data, and I'd like to update this and make sure it's accurate, both for web developers and gecko hackers.
I made an addon[1] that goes through their test suite and spins up our timeline marker tracker and records what markers we observe when a CSS property changes. An issue is, the markers seem non-deterministic at times, like other things could schedule paints or layouts in the future that results in cluttering up the results, getting series of paint markers when idling. In lieu of having our markers have the original cause or source (possibly a good chunk of work), are there any other suggestions on how we can observe this data and minimize incorrect results? [0] https://csstriggers.com/ [1] https://github.com/jsantell/gecko-css-triggers _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
