Den 25.11.2014 10:50, skrev MiB:
As I often feel inclined to use vendor-prefixes in order to meet business
requirements, my CSS typically don’t validate fully. I always know why and
using SASS have shielded me somewhat from seeing this issue, as I can postpone
any prefixes to the final phase. Are you developers handling this differently
and if so how?
I only run stylesheets through the validator when: 1) I can not find one
of my own "disable this declaration" markers, 2) I can not manage to
debug a problem in browsers locally, and/or 3) I have to share my CSS
code with a developer who is paranoid when it comes to validity --
something I am not.
Point 2) and 3) above also apply to if/when I run HTML through
validators. I have HTML Tidy, and have it set up to clean up most of the
markup versions I may use -- including HTML5 as it stands right now.
My "rule" is that markup and style should ideally follow the "rules"
defined by W3C -- it is definitely the safest approach to designing
cross-browser. But, if a browser (usually a slightly older one) has to
be hacked in order to play ball, making it work as intended across
browser-land is usually more important than serving "perfectly valid code".
regards
Georg
______________________________________________________________________
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
