Wrong line-numbers on source-map selectors - chrome reports position of first element, not last element

The following less would point into the line of html>body form although the definition was explicitly for input. However, this would work correctly when using the & operator, but it is a pain to change all of the less definitions like that

html>body form  {

    input {
        color: cyan !important;
    }

    & input {
        background: yellow !important;
    }
}

I think this can be extent to other operators supported in less, but never the less, either empty or any operators should be supported correctly by the source maps, since it is valid less code.

[lukeapage]

note: work-around from #1715 is to control and click on the property not the selector. note 2: chrome won’t fix it so it would have to be addressed in less, probably finding the last element index ? in a selector

[dotnetwise]

Yes, but only for not “nested rules”

If you nest anything in a big rule, then all the sourcemap lines will point to its top.