Why doesn't ampersand compile nesting?

Question

css

All my layout components are written in BEM, I start each new block with something like this:

.footer{
  width: 100%;
  position: relative;
  &__plate{
    position: relative;
    z-index: 3;
    @extend %plate;
  }
}

In theory, styles for footer_plate should be compiled with nesting:

.footer{
  width: 100%;
  position: relative;
}
.footer .footer__plate{
  position: relative;
  z-index: 3;
 ...
}

But for some reason the compiler does this:

.footer{
  width: 100%;
  position: relative;
}
.footer__plate{
  position: relative;
  z-index: 3;
 ...
}

I noticed this recently - it doesn't really bother me, because BEM classes never repeat. However, this nevertheless deviates from the rules of methodology. After all, if a footer_plate appears in some left block, then the styles will be applied to it. Besides often it is necessary to inherit elements of frameworks which repeat. I put them in a quiet class so that the frame element itself does not fall into the compilation. If I inherit a frame element with a modifier into a block element, I have to use !important just because of this shortcoming. Is there a way to tell the compiler to create a nesting if it exists in the code regardless of the ampersand?

Answer 1

Everything works as it should. Where did this "in theory" come from?