Metadata
- Source
- FLUID-3678
- Type
- Bug
- Priority
- Major
- Status
- Open
- Resolution
- N/A
- Assignee
- Antranig Basman
- Reporter
- y z
- Created
2010-07-19T16:49:11.908-0400 - Updated
2014-07-30T15:34:52.609-0400 - Versions
-
- 1.2
- Fixed Versions
- N/A
- Component
-
- Renderer
Description
Not sure if that's a bug but these are the steps to reproduce:
Attempt to call fetchResources for some html template.
In callback try to fluid.parseTemplates this templates.
Finally call fluid.reRender(templates after they were parsed, someNode in current markup, component tree, {cutpoints: some cutpoints});
Notice that selectors in component tree were not rendered (found) by the renderer. Supposedly due to the fact that the renderer tryes to render them before the markup is final (i.e. contains the template in the node).
Please refer to the "FLUID-3678: Fetching and rendering a template into a node" renderer test case in the attached patch.
Attachments
Comments
-
y z commented
2010-07-19T16:50:39.833-0400 Testcase for the issue.
-
y z commented
2010-07-20T11:14:35.992-0400 Looks like it works if cutpoints are specified in resources structure passed to fetchResources and parseTemplates and not to the reRender function in the options.
-
Justin Obara commented
2014-07-30T15:34:52.609-0400 @@Antranig Basman is this something that we should fix, or should we not expect reRender to be called directly?