You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2014/12/24 02:46:13 UTC
[jira] [Closed] (TAP5-2190) Alerts component should not
automatically import the core stack
[ https://issues.apache.org/jira/browse/TAP5-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-2190.
--------------------------------------
Resolution: Fixed
Fix Version/s: 5.4
Assignee: Howard M. Lewis Ship
> Alerts component should not automatically import the core stack
> ---------------------------------------------------------------
>
> Key: TAP5-2190
> URL: https://issues.apache.org/jira/browse/TAP5-2190
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.4
> Reporter: Felix Gonschorek
> Assignee: Howard M. Lewis Ship
> Priority: Minor
> Fix For: 5.4
>
>
> The Alerts component (org.apache.tapestry5.corelib.components.Alerts) @Import's the "core" stack.
> If you want to disable the core stack (which is now included by default, see TAP5-2169) you can disable the auto include of the core stack with the following approach:
> public void contributeMarkupRenderer(OrderedConfiguration<MarkupRendererFilter> configuration) {
> configuration.override("ImportCoreStack", null);
> }
> But if you place the alerts component in your template, the core stack get's again included and the bootstrap css messes up your layout completely.
> The Alerts component is the only component in tapestry-core which has an @Import(stack="core") annotation.
> My suggestion: remove it :-)
> thx
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)