I don't like that having an extension behaves differently than not. That is sure to trip some people up. In my ideal syntax we'd have the following:
@import => A browser-based import with no special meaning @include => Does what @import does now for sass/scss files @mix => Does what @include does now for mixins. But that's an awful lot of rearranging for only a minor syntactic improvement. So instead, I could get behind extending import with a modifier or something to mean it should be done locally instead of remotely. @import "foo.css" !local; or something to that effect. The Sass parser already has a CSS mode, so this would be pretty simple to implement and with @extend and nested imports in sass 3.1, it's actually a quite nice behavior to have. Chris On Sat, Mar 19, 2011 at 11:04 AM, Raving Genius <rg+goo...@ravinggenius.com>wrote: > 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. > > -- 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.
