Skip to content

Invalid CSS #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
mrichman opened this issue May 5, 2009 · 3 comments
Closed

Invalid CSS #1

mrichman opened this issue May 5, 2009 · 3 comments

Comments

@mrichman
Copy link

mrichman commented May 5, 2009

I ran my CSS against the W3C validator (http://jigsaw.w3.org/css-validator/validator), and got the following error:

Property overflow-x doesn't exist in CSS level 2.1 but exists in [css3] : hidden

This occurs on line 176 of the screen.css generated by the compass framework for Blueprint:

/* line 97, ../../../../../../../Library/Ruby/Gems/1.8/gems/chriseppstein-compass-0.6.5/frameworks/blueprint/stylesheets/blueprint/modules/_grid.sass */

  • html .column, * html div.span-1, * html div.span-2, * html div.span-3, * html div.span-4, * html div.span-5, * html div.span-6, * html div.span-7, * html div.span-8, * html div.span-9, * html div.span-10, * html div.span-11, * html div.span-12, * html div.span-13, * html div.span-14, * html div.span-15, * html div.span-16, * html div.span-17, * html div.span-18, * html div.span-19, * html div.span-20, * html div.span-21, * html div.span-22, * html div.span-23, * html div.span-24 { overflow-x: hidden; }
@whicks1
Copy link

whicks1 commented May 11, 2009

I agree, the blueprint grids are overflow happy, & setting to hidden is not always the desired effect. Can this be abstracted out into a mixin unto itself?

@chriseppstein
Copy link
Member

This property was added in blueprint 0.8 and I don't fully understand what it is trying to achieve. My goal is to have the blueprint port stay as true to blueprint proper as makes sense. I'm not inclined to make a change just to silence a validation error that is valid in css3 and likely harmless in css2 (browsers discard properties they don't understand).

What, if any, real issue does this cause?

@chriseppstein
Copy link
Member

Ok. I waited 5 days for further comments. Closing this issue.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants