Changes between Version 15 and Version 16 of CoordinatedGraphicsSystem
- Timestamp:
- Aug 4, 2012, 5:33:06 AM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TabularUnified CoordinatedGraphicsSystem
v15 v16 129 129 The web process owns the frame and the content. It decides when to render a new frame, which information to include in the layer tree, how the backing stores behave, and also how the animations are timed. 130 130 The UI process is responsible for rendering the latest frame from the web process, compensating for user interaction not yet committed by the web process. 131 132 ''An example for that is scrolling adjustments - the web process tells the UI process which layers are fixed to the viewport, and the UI process knows the exact scroll position for each paint. It’s the UI process’ job to account for the difference. Another role of the UI process is to periodically notify the web process of viewport changes (e.g. panning), to allow the web process to decide whether or not to create/destroy tiles, as well as moving content into view when writing in text fields.''131 132 ''An example for that is scrolling adjustments - the web process tells the UI process which layers are fixed to the viewport, and the UI process knows the exact scroll position for each paint. It’s the UI process’ job to account for the difference. Another role of the UI process is to periodically notify the web process of viewport changes (e.g. panning), to allow the web process to decide whether or not to create/destroy tiles, as well as moving content into view when writing in text fields.'' 133 133 134 134 === Classes ===