You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2014/05/27 09:20:05 UTC

[jira] [Updated] (TAP5-1377) Combine CSS files in production mode

     [ https://issues.apache.org/jira/browse/TAP5-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jochen Kemnade updated TAP5-1377:
---------------------------------

    Labels: bulk-close-candidate  (was: )

This issue has been last updated about 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future.

If the issue still persists with the most recent development preview of Tapestry (5.4-beta-6, which is available from Maven Central), please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the dev@tapestry.apache.org mailing list first.


> Combine CSS files in production mode
> ------------------------------------
>
>                 Key: TAP5-1377
>                 URL: https://issues.apache.org/jira/browse/TAP5-1377
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-core
>    Affects Versions: 5.2
>            Reporter: Dan Adams
>              Labels: bulk-close-candidate
>
> When in production mode, combine CSS files into a single file as is done with javascript resources. 
>  * Any relative references to urls in the CSS contents should be absolutized based on the URL of the original CSS path so that things like background images continue to function. 
>  * @import statements should also be unpacked so that designers have flexibility in how the files are structured. 
>  * Any CSS files that have a class on the link element of "nocombine" or that have a non default/non-screen media should not be combined.
>  * Record a comment before each file saying which CSS file it originally came from



--
This message was sent by Atlassian JIRA
(v6.2#6252)