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
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