[
https://issues.apache.org/jira/browse/WICKET-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12722414#action_12722414
]
Pierre Wargnier commented on WICKET-2331:
-----------------------------------------
In fact the scripts are 95% similar, but it's why the parameters are for, isn't
it ?
They are in-lined, so they will be both evaluated before the page is displayed.
Ok, on production environment, the licence stuff will be striped down and the
overhead is not that huge.
Perhaps it's better to use another JS outside Wicket and to make it point to a
standard Wicket text field if good performances are required and many dates are
on a page ?
> Using 2 date fields and 2 date pickers create 2 inline javascript
> -----------------------------------------------------------------
>
> Key: WICKET-2331
> URL: https://issues.apache.org/jira/browse/WICKET-2331
> Project: Wicket
> Issue Type: Bug
> Components: wicket-datetime
> Affects Versions: 1.4-RC4
> Reporter: Pierre Wargnier
> Attachments: date1.txt, date2.txt
>
>
> You create 2 DateTextField in the same page and add one new DatePicker to
> each of them.
> It will create twice the same inline javascript: of about 2 786 bytes with
> the licence in it. If you want X field, you will get a payload of X * 2786
> bytes.
> If you add the same DatePicker object to the 2 DateTextField, you have only
> one javascript but the second DatePicker does not work.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
