[
https://issues.apache.org/jira/browse/WICKET-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12806795#action_12806795
]
Juergen Donnerstag commented on WICKET-2693:
--------------------------------------------
With the pluggable approach you can even mix them. Lets says parent first for
wicket core and child first for your own components.
I'll commit that change to 1.5 since it improves the flexibility anyway. And if
we want to change the default implementation, we start the vote.
> 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.
