[dev] [commits] Horde branch master updated. b31b393c5d7952e4c7391cc41c0b91b24a593fa6

[Michael M Slusarz]

Quoting Rui Carneiro <rui.carneiro at portugalmail.net>:

> On Sat, Mar 16, 2013 at 1:11 AM, Michael M Slusarz <slusarz at horde.org>wrote:
>
>> 1) Patch CssTidy to work with CSS 3 rules
>> 2) Re-write CssTidy to work with CSS 3 rules.
>> 3) Add your local rules as an External stylesheet  
>> (Horde_PageOutput#**addStylesheet()),
>> which isn't parsed like Horde stylesheets.
>>
>
> I am not considering the first two options because CssTidy is a dead
> project (last stable version is from 2007).

Exactly.  That's why option #2 exists above - rewrite css tidy to work  
for CSS 3 rules.

> The 3rd option would be an option if CssTidy had @media queries support.
> Currently our installation has a lot of media queries to adapt
> Horde to a couple of different resolutions and we are quite happy with the
> final result. AFAIK if I start using Horde_PageOutput#**addStylesheet()
> to add this extra stylesheet an extra request will be made and this
> stylesheet will not be minified. Am I right?

It won't be minified.  But you can't use things like relative paths in  
the CSS either and expect it to resolve correctly to the current Horde  
settings.  So that's a big loss of functionality (that's the main  
reason we use csstidy in the first place - to parse the CSS to allow  
us to do this path translation automatically).

michael

___________________________________
Michael Slusarz [slusarz at horde.org]