#72: Task Scheduling

Visit on Github.

Opened Sep 14, 2015

The CSS Houdini effort is looking to specify a pipeline model for execution of script in layout/raster: https://docs.google.com/document/d/1Mw6qNw8UAEfW96CXaXRVYPPZjqQS3YdK7v57wFttAhs/edit?pli=1#

This (re)raises the question about ordering for delivery of other tasks in the platform (Mutation Observer change records, Object.observe records, setTimeout callbacks, setIdleCallback callbacks, requestAnimationFrame callback delivery). This has been discussed at some length, e.g., with @wycats at TC39.

The open question here is if the TAG should try to untangle this and generate a recommendation for scheduling in the non-layout/raster bits of frame generation.

/cc @annevk

Discussions

2018-12-19

Minutes

Travis: timing ... intersection observer ...

[david recently suggested writing tests]

David: Intersection observer issue led me to that one.

Travis: happy to participate in some time to collaborate on writing tests... Will reach out on the 14th

2019-01-15

Minutes

David: We put this on the agenda today as a reminder to have me look into it.

Travis: I probably won't get to this by the F2F. Anyone want to take and drive this forward?

David: I can try to make some progress by the next F2F.