elastic.css file not valid in all level of css
5 views
Skip to first unread message
sda
Jan 15, 2011, 9:23:01 AM1/15/11
to Elastic CSS Framework
I'm very impress with this elastic css framework until i try it for
myself, but unfortunately the elastic.css file did not pass the
validation of css level 2.1 and level 3.
It would be good if the elastic.css file that we gonna use pass the
validation.I try to validate some of the parse error by removing the *
and some elements but it will affect the layout as a whole.Any
solution on this?
myself, but unfortunately the elastic.css file did not pass the
validation of css level 2.1 and level 3.
It would be good if the elastic.css file that we gonna use pass the
validation.I try to validate some of the parse error by removing the *
and some elements but it will affect the layout as a whole.Any
solution on this?
Fernando
Jan 15, 2011, 4:54:24 PM1/15/11
to Elastic CSS Framework
indeed there is a solution conditional css file inclusion the * rules
are to avoid this, and yes the css stops validating but its a lo less
work than the problems on all <!-- if [IE] ....
its your call but the only thing you will get is to pass a validation,
and get more work on your hands.
of course you can solve this with a snippet.
from the validation point of view, is there something real you get
from passing a validation?
validations are to check if the css does not have errors, but when you
have to hack to make things work well i think thats a lil different
story.
there are other rules in there besides the * there are _ those will
have to go to a separate file too and use conditional inclusion.
are to avoid this, and yes the css stops validating but its a lo less
work than the problems on all <!-- if [IE] ....
its your call but the only thing you will get is to pass a validation,
and get more work on your hands.
of course you can solve this with a snippet.
from the validation point of view, is there something real you get
from passing a validation?
validations are to check if the css does not have errors, but when you
have to hack to make things work well i think thats a lil different
story.
there are other rules in there besides the * there are _ those will
have to go to a separate file too and use conditional inclusion.
COTIZACION
Jan 15, 2011, 11:26:36 PM1/15/11
to elastic-cs...@googlegroups.com
He is true, validators intend to inform the developer the general health of their code. They just attempt to do it because only human made validations can be accurate.
When it is about hacks, there will be scenarios when browsers simply will not let you by. If it makes you feel any better, from the developer standpoint your code still being considered correct if the css files of authorship validate.
When it is about hacks, there will be scenarios when browsers simply will not let you by. If it makes you feel any better, from the developer standpoint your code still being considered correct if the css files of authorship validate.
2011/1/15 Fernando <tras...@gmail.com>
--
You received this message because you are subscribed to the Google Groups "Elastic CSS Framework" group.
To post to this group, send email to elastic-cs...@googlegroups.com.
To unsubscribe from this group, send email to elastic-css-fram...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/elastic-css-framework?hl=en.
Reply all
Reply to author
Forward
0 new messages