[
https://issues.apache.org/jira/browse/WICKET-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12806850#action_12806850
]
Igor Vaynberg commented on WICKET-2693:
---------------------------------------
juergen,
something like this cant be pluggable because if i design my custom component
against one render strategy, most likely it wont work when used in an app with
another one. i think this should be a contract.
> improve css/js contributions
> ----------------------------
>
> Key: WICKET-2693
> URL: https://issues.apache.org/jira/browse/WICKET-2693
> Project: Wicket
> Issue Type: Improvement
> Reporter: Igor Vaynberg
> Assignee: Igor Vaynberg
> Fix For: 1.5-M1
>
>
> currently the order of css contributions is
> page (1st)->container(2nd)->component(3rd)
> we should inverse this order and allow deepest nested components to
> contribute first, this way an outer container's contributions will appear
> below allowing the container to override the css/javascript
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
