Skip to main content
Question

[Bug] "Lock Aspect Ratio" + Ctrl+Arrow Causes Unstable Resizing and Position Shifts

  • February 12, 2025
  • 1 reply
  • 52 views

yVincent

When using the new "Lock Aspect Ratio" feature and adjusting an element’s size using the Ctrl + Arrow shortcut, the resizing behavior is inconsistent and unstable. The size increments/decrements in an unexpected pattern, and the element’s position also shifts unintentionally.

Steps to Reproduce:

  1. Select a rectangle (or any element) in Figma.
  2. Enable the "Lock Aspect Ratio" feature.
  3. Use the Ctrl + Arrow (Left/Right/Up/Down) shortcut to adjust the element's size.
  4. Observe:
    • The size does not increase/decrease smoothly.
    • Initially, the size changes by 0.5px for 5-6 steps.
    • Then, it starts breaking into irregular decimal values (e.g., 0.49px, 0.48px, etc.).
    • The position of the element also changes, shifting towards the direction of the arrow key pressed.
    • If the element is positioned at the edge of an artboard, it moves slightly instead of just resizing.

Expected Behavior:

  • The element should resize in stable increments (e.g., 1px per step) without decimal inconsistencies.
  • The element’s position should remain unchanged while resizing.

Actual Behavior:

  • The element resizes in unpredictable decimal increments.
  • The position shifts while resizing.

Environment:

  • Figma Web/Desktop
  • Windows 10/11 (issue may also exist on macOS)
  • Latest version (as of February 2025)

Attachments:

Original Size

 

CTRL+Arrow pressed 1 time
​CTRL+Arrow pressed 6 times

 

It also changes the element position on Frame

 

Additional Notes:

This issue disrupts precise resizing workflows, especially for pixel-perfect UI designs. It appears to be a bug related to the "Lock Aspect Ratio" logic interfering with the Ctrl + Arrow shortcut behavior.

Would appreciate any insights from the Figma team or community on a potential fix/workaround. Thanks!

Celine_D
Figmate
  • Community Support
  • February 13, 2025

Hey ​@yVincent ,
Thank you for flagging this bug! We’ve reported internally and our team was able to reproduce this issue.

Our engineering team is currently investigating. Appreciate your patience in the meantime! 🙏🏼


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings