Sourcemap points to topmost selector of nested selectors/rules

[enterframe]

When I try to to access the less-source using the chrome-debugger (&sourcemaps) by clicking a selector (.inner) in it´s inspector, it always points me to the topmost less-selector defined (.topmost):

.topmost {
  .inner {
    ...
  }
}

There´s a workaround using the &-operator like:

.topmost {
  & .inner {
    ...
  }
}

I´ll ask myself if this is a bug or an expected behaviour.

[matthew-dean]

To my recollection, this is a Chrome bug. Someone may be able to find the relevant issue.

[lukeapage]

Its a duplicate. Chrome gets all the information but navigates to the
source of the upmost selector. I raised a chrome bug, but can't remember if
they fixed it or we came to the conclusion we needed to workaround.

[lukeapage]

of #1492