Unexpected DR scope visibility results

[printjs]

Official document

source

@variable: global;
@detached-ruleset: {
  // will use global variable, because it is accessible
  // from detached-ruleset definition
  variable: @variable; 
};

selector {
  @detached-ruleset();
  @variable: value; // variable defined in caller - will be ignored
}

result

selector {
  variable: global;
}

actuality

source

@variable: #abc;
@detached-ruleset-test: {
  color: @variable; 
};
.selector {
  @detached-ruleset-test();
  @variable: #def;
}

result

.selector {
  color: #def;
}

less version is 2.7.2

[rjgotten]

Afaik detached rulesets are supposed to pull both caller and definition scope into closure and give precedence to caller scope. So; not a bug, but definitely weird behavior. Hopefully it will be removed sometime in the future.

[seven-phases-max]

I can't reproduce your "actuality" results in v2.7.2 so more details needed.

@rjgotten

and give precedence to caller scope.

No, neither DRs nor mixins (unless defined/invoked with parametric namespace) ever did this. (You'll find the mixins scope priority list here).

[rjgotten]

No, neither DRs nor mixins (unless defined/invoked with parametric namespace) ever did this

I thought this was actually reported before in another issue and was deemed expected behavior back then?
Perhaps I'm mixing something up.

[seven-phases-max]

Perhaps I'm mixing something up.

Most likely, because it's just how it works and has been working always. So @wjtgithub's problem is elsewhere.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.