[
https://issues.apache.org/jira/browse/TAP5-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robin Komiwes updated TAP5-1113:
--------------------------------
Description:
Actually Palette component is initialized using this portion of code:
renderSupport.addScript("new Tapestry.Palette('%s', %s, %s);", clientId,
reorder, naturalOrder);
In order to be less dependent from a particular JS framework, it should be done
using :
renderSupport.addInit(...);
was:
Actually Palette component is initalized using this portion of code:
renderSupport.addScript("new Tapestry.Palette('%s', %s, %s);", clientId,
reorder, naturalOrder);
In order to be less dependent from a particular JS framework, it should be done
using :
renderSupport.addInit(...);
> Palette client side instanciation should be done using Tapestry.initializer
> ---------------------------------------------------------------------------
>
> Key: TAP5-1113
> URL: https://issues.apache.org/jira/browse/TAP5-1113
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.2.0
> Reporter: Robin Komiwes
> Priority: Minor
>
> Actually Palette component is initialized using this portion of code:
> renderSupport.addScript("new Tapestry.Palette('%s', %s, %s);", clientId,
> reorder, naturalOrder);
> In order to be less dependent from a particular JS framework, it should be
> done using :
> renderSupport.addInit(...);
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
