Hey Community,
been observing an issue for a while now while working with Branches and Merges and was wondering whether this happens to you guys, too, and what the hell causes it.
I have a component set with a few variants; let’s say, a Chip component with different size variants. All of them have a nested instance of another component, which is called State Layer. This State Layer unifies all interaction states and changes, when interacting with a component, where it’s used, such as the Chip. It is positioned absolutely, spans the entire surface of the affected component and is set to Top/Bottom, Left/Right to scale properly.
To not disturb the developers in dev mode with this helper component and its layers, we usually lock it as designers can access its props from the instance Chip, etc., so there’s no need to have its layers available for scanning.
Now, I don’t know, whether this is a Branch/Merge issue or related to something else, but, what I noticed during my work on the branch, when this State Layer was implemented in the Chip, positioned, resized and locked as usual, was that the next day upon reloading the page, the State Layer in all Chips was moved to X: -4, so offset by 4px. Now, I was wondering, whether it hadn’t saved the positioning, so I repositioned it again: Select all, set X to 0px - done. Next day: same problem. Now, when the work was done, I corrected it one more time before merging it to the Main Branch of our Design System and it seemed to be OK. Then suddenly, when I checked on the component two days later, everything was again offset by -4px on the x-axis. Fun fact though: It didn’t perceive this as a change, which would require publishing. And currently, I cannot tell, whether this also automatically overrides all Design Files, where the Chip has been in use and updated after the merge. What I do know, however, is that after trial and error for a few minutes, I found, that when unlocking the State Layer, repositioning it, keeping it unlocked, fixes the issue permanently. Now, it defeats the purpose, though, and I am afraid that it will show again, should I lock it now.
Any ideas, what’s going on here?