You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Felix Scheffer (JIRA)" <ji...@apache.org> on 2015/03/18 15:51:39 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 ]
Felix Scheffer updated TAP5-1377:
---------------------------------
Attachment: 0002-TAP5-1377-Combine-CSS-files-in-production-mode.patch
Some basic support for combing css files but not 100% of what the OP asked for in the description:
* No unpacking of @import statements. Requires parsing the css file (=lots of extra work).
* The file name of the original file is not added to the combined file (We dont do that when combining js files)
* There is no support for "nocombine"
* Stacks with conditional style sheets are not combined. (One css file per condition would be required)
> 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.3, 5.4, 5.2
> Reporter: Dan Adams
> Attachments: 0002-TAP5-1377-Combine-CSS-files-in-production-mode.patch
>
>
> 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.3.4#6332)