Skip to main content
ethan_carter_87
New Member
Oct 20, 2026 2:23 PM UTC
Question

Auto-layout breaking on responsive web dashboard prototype

Hi everyone, I am currently putting together a responsive gaming client concept in Figma, taking inspiration from the interface structure found on this website. I am running into a frustrating issue where my nested auto-layout containers refuse to resize dynamically when switching between desktop and mobile viewport presets.

 

Whenever the frame scales down, the primary navigation text wraps unexpectedly and forces adjacent button components outside the visible canvas instead of respecting the fill container rules. Has anyone encountered similar inheritance glitches with nested auto-layout groups, and what is the best way to maintain clean responsiveness without rebuilding each screen variant from scratch?

    3 replies

    mith sams
    New Participant
    Oct 20, 2026 4:44 PM UTC

    This usually happens when one frame in the nesting chain is still set to Fixed width, which blocks resizing from flowing down to the children. Select each frame in the chain and set its horizontal resizing to Fill container, then set the nav text layer to Fill container with truncation turned on so it shortens instead of wrapping. Once every level fills its parent, scaling the outer frame will resize everything cleanly.

    Lucas West-
    New Participant
    Oct 22, 2026 5:25 PM UTC

    Can you share the file, a video, or some screenshots perchance? As ​@mith sams said, you should go through your nested frames and ensure each one is set to fill all the way down and the text is set to truncate instead of wrap.

    However, “without rebuilding each screen variant from scratch” could potentially imply there is some component usage here. If not, stop here.

    If, however, you are nesting components, as supposed to just flat frames, (which I strongly recommend against for a beginner because it’s buggy asf,) then there is a little more complexity to it. If you define a component’s root to hug in it’s definition, then instances of that component will also come in set to hug as you would expect. However, perhaps since fill requires the container to be an autolayout, there is a bug/missing feature/unexpected behavior where when you pull in an instance of a component who’s definition has it an axis set to fill, even if you are placing it inside an autolayout container where this would be valid from the beginning, it will annoyingly come in as “fixed” in the axis/axes you had set to “fill” in the definition. You have to know and remember to go in and manually override the sizing back to fill in those axes on each instance root, every time you use the component.

    A little trick here is to set up the parent components to use instance swapping with a placeholder component instead of slots or direct composition in the definition, since instance swapping tries to carry over the sizing setting from the before to the after, if you set the placeholder to fill, then when you swap in your actual component it will also come in set to fill.

    If this or ​@mith sams response solved your issue, please remember to mark it so.

    siwav71894
    New Member
    Oct 23, 2026 4:13 AM UTC

    I'd check a few things in Figma first 😅

    Select the parent frame and set its width to Fill container, then check the nested frames and make sure they aren't using fixed widths. For the nav text, try turning off text auto-resize and setting a fixed width or truncation so it doesn't push the buttons out. Also check the spacing between items and use Space between on the parent auto layout if needed. If it still breaks on mobile, try hiding a few nav items or switching to a hamburger menu at smaller widths. That should be easier than rebuilding every screen from scratch!