The community members are discussing an issue where the token selection in a project switches to a local token when the user switches to another element and then comes back. The initial intention was to prevent users from accidentally editing tokens, but the community members have concluded that they should remember the previously selected token on an instance. They have also discussed the order of tokens and how local styles can conflict with token styles. A community member has shared a link to a related GitHub issue, but there is no explicitly marked answer in the comments.
So I tried creating tokens in my new project but whenever I select a token and then switch to some other element and come back again, the selection switches to local token
@Alex This is what I mean. When I switch to some other element and switch back to the previous element (where a token was selected) then the local token is automatically selected. It was confusing.
To make matters worse, I had a conflict where if I edited some local styles and switched to token, the styles in right panel would be marked in red. (I resolved this one though, just clear local styles and select token again.)
And another question, how is the order of tokens decided? In a template I copied (Marketing template) there are some elements with local style in first position. The last token in these seem to stay selected.
