Re: CSS Triggers

2016-04-06 Thread Xidorn Quan
On Wed, Feb 24, 2016 at 8:53 AM, Boris Zbarsky wrote: > On 2/23/16 4:18 PM, Jordan Santell wrote: > >> are there any other suggestions on how we >> can observe this data and minimize incorrect results? >> > > In an automated way, or manually? > > Because you can look at nsStyleStruct.cpp to figur

Re: CSS Triggers

2016-04-06 Thread Jean-Yves Perrier
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&#x

Re: CSS Triggers

2016-02-23 Thread Boris Zbarsky
On 2/23/16 4:18 PM, Jordan Santell wrote: are there any other suggestions on how we can observe this data and minimize incorrect results? In an automated way, or manually? Because you can look at nsStyleStruct.cpp to figure out what we will do in response to various property changes. Note th

CSS Triggers

2016-02-23 Thread Jordan Santell
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 eff