You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2013/06/28 10:54:20 UTC
[jira] [Updated] (WICKET-5257) Make css class strings used in the
framework configurable
[ https://issues.apache.org/jira/browse/WICKET-5257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov updated WICKET-5257:
------------------------------------
Fix Version/s: 7.0.0
> Make css class strings used in the framework configurable
> ---------------------------------------------------------
>
> Key: WICKET-5257
> URL: https://issues.apache.org/jira/browse/WICKET-5257
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 7.0.0
> Reporter: Martin Grigorov
> Assignee: Martin Grigorov
> Fix For: 7.0.0
>
>
> From the roadmap document for Wicket 7:
> In a few places in core we have hardcoded css strings like wicket_orderUp and classes used inside the feedback panel - these should be made into application settings so they can be configured to conform to the application's css infrastructure.
> Once we extract wicket_orderUp we should get rid of cssprovider and defaultcssprovider classes.
> getApplication().getCssSettings().setSortOrderDownClass("sort-order-down");
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira