On 22.11.2010, at 19:30, Jordi Boggiano wrote: > On Mon, Nov 22, 2010 at 7:27 PM, Lukas Kahwe Smith <[email protected]> > wrote: >> ah .. i thought it renders the templates before it it renders the layout. or >> does it start with the layout and then works itself back up the chain? > > It flattens the whole extends tree at compile time, then at runtime, > it starts at the top of the layout, and works down, rendering blocks > as they come. That also means things like {% stylesheet "foo.css" %} > can not be called in content templates, if you want to output the > stylesheets in your <head> tag. For js though it's ok since you most > likely want that at the end of the page anyway.
Hmm I guess this approach also kinda makes sense in light of ESI compatibility. Aka if an ESI block would rely on being able to inject a js/css file into the head tag it would break. Which also reminds me that we need to ponder how flash messages fit into there. regards, Lukas Kahwe Smith [email protected] -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
