The javascript stack concept exists so that the stack remains constant and can be cached by the client's browser.
You are now asking to break this contract and have stacks be dynamic based on what components are on a page which would eliminate the ability to cache them in the client's browser. I suggest that you re-think your javascript stacks so that you bunch things together that really belong together. Cheers, Lance. On Monday, 5 March 2012, Jochen Berger <foober...@googlemail.com> wrote: > Hi, > > I just observed that if I add a JS library to two different stacks and import them in a page, that asset is added to the page twice. > This happens because JavaScriptSupportImpl does check for duplicate stylesheets (L 327) and stacks (L 294) but not for duplicate scripts. Is that expected or should I add a JIRA/patch? > > Regards, > Jochen > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
