I would prefer not to add a CSS validator to the application compilation
time. I don't think it would catch enough stuff often enough. We should
check for invalid css usage as part of the build by running a command-line
tool, but I would do it in a way that committers don't have to install
that t
our users it
would make the css less legible. It’s enough that we document these atts
somewhere.
From: Harbs
Sent: Thursday, November 30, 2017 1:15:44 PM
To: dev@royale.apache.org
Subject: Outputting valid/efficient CSS
I just ran some CSS output by Royale
Related:
It would be nice to add CSS optimization/minification to the Royale toolchain.
A nice tool for that is csso[2] which can be used with a command line
interface[3]
Harbs
[2]https://github.com/css/csso
[3]https://github.com/css/csso-cli
> On Nov 30, 2017, at 1:15 PM, Harbs wrote:
>
>
I just ran some CSS output by Royale through a CSS validator.[1] It turned up
some issues, but most were results of my migration from Flex.
The one exception I found was:
* {
effect-timer-interval: 10;
}
effect-timer-interval is not a valid CSS property. It comes from the defaults
cs
