> Let's say the client sends me a pic from patterntap<http://patterntap.com/tap/pattern/9475915264bcb21db2a0cf>and asks me to build such a menu. In a quick glance, I can see the navbar is
> a list so i write css as if I knew the markup:

> .-nihongoup-navbar-menu {
>   @include inline-block-list;
>   background-color: black; padding-top: .5em; }

> .-nihongoup-navbar-item:hover {
>   @include border-radius: 5px 5px 0 0;
>   background-color: white; }

> And so on. But then the developer finally gives me access to the markup,
> generated by his framework. If it is semantic it might be an html5 <nav>
> element, if it is just good it will be a <ul> and <li> elements, but it
> might be a set of <div> elements. Of course, I'd rather rewrite the markup,
> but let's say I don't want or just can't. I can write a selector that works
> and then extend it:

> ul.menu-class-the-framework-thinks-is-clever {
>   @extend .-nihongoup-navbar-menu; }

> ul.menu-class-the-framework-thinks-is-clever > li {
>   @extend .-nihongoup-navbar-item; }

> Now this second @extend rule will printout several classes. Now you might
> have noticed I named the extendable classes with a starting dot and hiphen.
> I did it to prevent clashing with any other class in the markup -- I really
> don't trust the framework nor the future mantainers of this code. But
> wouldn't it be wonderful if I could tell the extendable classes they
> shouldn't be printed in the css file?

> This is something I hope gets implemented soon. I didn't find anything in
> SASS 3.1 Reference file.

> --
> You received this message because you are subscribed to the Google Groups
> "Compass" group.
> To post to this group, send email to compass-users@googlegroups.com.
> To unsubscribe from this group, send email to
> compass-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/compass-users?hl=en.