I agree that @import foo.css should work as in regular CSS, but the proposal for @import foo makes a lot of sense to me. The proposed behavior would be a win because it would automatically remove an extra GET request by inlining the CSS. It would also be more consistent with importing sass or scss files without an extension.
On Mar 19, 2:42 am, Alexander Sergeyev <etorea...@gmail.com> wrote: > Since Sass is a CSS3 superset, @import "foo.css" must work as it does in CSS > > Nathan, > we're agree that @import "foo.css" should work as it does in CSS, there is > no contradiction with my proposal. Proposal is just and only about extending > of @import "foo". This command is SASS-specific, so it wouldn't ruin the > consistency if you allow one more extension besides .sass and .scss to be > processed. Again to sum up: > > @import "foo.css" will work as it does in CSS > @import "foo" will include contents of foo.(sass|scss|css) -- You received this message because you are subscribed to the Google Groups "Haml" group. To post to this group, send email to haml@googlegroups.com. To unsubscribe from this group, send email to haml+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/haml?hl=en.
