Skip to main content

For days now, every time I try to copy/clone an element from an auto-layout and paste or move it outside of this auto-layout, in many cases the element starts to “glitch” and it becomes impossible to drag it across the canvas correctly. Its origin point seems to have shifted, and when I try to move it, the center of movement is not associated with the pointer, but with a position 10-20-30px further away both vertically and horizontally.


Moreover, any keystroke (right, left, up, down… any!) to move the element any number of pixels (it could be 1px, 8px, 10px…) causes the element to shift a fixed number of pixels (even in decimals) that has nothing to do with the input given.


This is becoming exasperating and forces me to copy, paste, delete, and re-paste each element every time I do this. It’s a disaster…


Is anyone else experiencing this? I can’t believe no one else is going through the same problem.


Test

Hi @DavidTC, Thank you for bringing this to our attention. I appreciate you sharing the video, and I noticed that the mouse pointer position is away from that element.


It seems that the tool is not functioning as expected. However, I haven’t encountered this issue on my end yet, and I couldn’t find a related report so far.

Could you please try clearing your cache in your browser and desktop app, and try doing this action again? - Clear the Figma desktop app cache


If the issue persists, I recommend submitting a bug report for further investigation from here: https://help.figma.com/hc/en-us/requests/new?ticket_form_id=360001744374

When you submit, please include the following:



  • Your Figma account email address

  • Attach a video showing the issue

  • Include the URLs of the affected files and add support-share@figma.com as an editor on these files (this will not impact your billing)


Thank you for your help with this!


If anyone in our community has any workarounds or insights, please feel free to share them here.

Hi!


Thanks for your response.


I noticed the issue was “fixed” a couple of days ago. Could probably be something related with what you mentioned, but to be honest I didn’t change anything. Just kept working with the issue and thought it would be arranged soon enough.


Thanks again!

Reply


Terms & ConditionsCookie settings