Details
-
New Feature
-
Resolution: Unresolved
-
Major
-
None
-
1.4, 1.5
-
None
Description
The final portion of framework work left over from the implementation of FLUID-3681 involves the implementation of what has come to be called a "phased renderer component". This is a renderer component which participates in an overall rendering workflow, which in one pass of an invocation of the fluid renderer, renders the markup for all such components participating in the tree. This requires new lifecycle points (phases) for the components which participate - in the initial phase, they are instantiated with no container in the DOM, and respond only to requests for component tree fragments and I/O requests they require before rendering can proceed. Once rendering is complete, they are then attached to the renderer tree and DOM as fluid decorators.
This workflow will also execute on the server, with phase 2 occuring on the client after markup is produced on the server.
Attachments
Issue Links
- depends on
-
FLUID-5046 Rewrite fluid.rendererComponent to modern framework standards, preparing for more fundamental changes to renderer
-
- Open
-
-
-
- Reopened
-
-
-
- Reopened
-
- relates to
-
FLUID-4261 "Tag Singularity Problem" prevents expression of some component trees, especially in recursive cases
-
- Open
-
-
-
- Open
-