Reading overview of the renderingNG architecture, I noticed that they speak about compositor thread in the render process. Look at these sentences:

• A data handler that maintains a composited layer list, display lists and property trees.
• A lifecycle runner that runs the animate, scroll, composite, raster, and decode and activate steps of the rendering pipeline. (Remember that animate and scroll can occur in both the main thread and the compositor.)
• An input and hit test handler performs input processing and hit testing at the resolution of composited layers, to determine if scrolling gestures can be run on the compositor thread, and which render process hit tests should target.

After that I don't quite understand following:

• What does composited layer list mean? Is it Layer Tree?
• What is the display list?
• What are the property lists?
• Does compositor treat inputs from a user? Is it entry point for the inputs? If it is, then what the compositor uses for detection on what element user has interacted?

I also read the Inside look at modern web browser, and there talked same about compositor, that it treats inputs from user, but there didn't talk about components what it uses.

Well, I've got confused

Main question: What does compositor thread use exactly and how, after the user has done interaction with page?