Position Constraint L + R not working on Elements with fixed Scroll Position

Hey ​@seb8 — welcome to Figma Forum, and thanks for surfacing this. I know switching back and forth between tabs can be frustrating.

I looked into this and found a few other designers reporting the same behavior in this thread: Left and Right constraint disabled when min/max width are set. Our product team is tracking the issue, and ​@Junko3 has been posting updates there. You might also find ​@Wirkkarl’s last reply helpful — they suggested a potential solution:

When you set both min/max width, Figma can’t apply both left & right constraints simultaneously because it would conflict with the fixed range you just defined. So it disables them to avoid layout ambiguity.

At Phonexa, we dealt with this when building responsive components in our internal dashboard. The workaround we found was using “center” constraint + fixed width for predictable scaling, or switching to auto layout where possible — gives more flexibility for responsiveness without constraint collisions.

Hope that helps!

If those don’t solve things for now, let me know how often this impacts your workflow, and I’ll flag it with the right team members so they can take a closer look. I can’t share a specific timeline for a fix, but I’ll make sure your experience is surfaced internally.

​@Tom Reem The thread you linked explains that Left/Right constraints are disabled when min/max values are set. It does not address the case where an element has no min/max values but is set to position: Fixed in prototype view.

With min/max values, it makes sense that horizontal constraints cannot work since they would conflict. But for fixed positioning, there should be no reason constraints are disabled. In CSS, position: fixed still respects left and right constraints.

This becomes a real issue for fixed navbars. You cannot make them fully responsive, even though the rest of the layout can be responsive with left/right constraints and inner containers using max widths.

​@Tom Reem , ​@Mike Zachariades thanks for your feedback and insights! ​@Tom Reem The quoted topic doesn’t solve this problem, unfortunately. I rarely work with min-max width on fixed elements. This issue mostly concerns navbars and sticky bottom bars on mobile views, which need to be resized regularly for quality assurance and prototyping on multiple devices. I have to deal with this issue on a weekly basis, often across multiple frames simultaneously. I would greatly appreciate it if this could be fixed in the future :)

Thanks again for your feedback!

Hey ​@seb8 and ​@Mike Zachariades — thank you both for taking the time to review the other thread and clearly outline the differences you’re seeing here, especially around fixed elements and how this impacts navbars and QA workflows. That detail helps us understand where the current behavior falls short. 🙏🏻

I have to admit I wasn’t able to completely recreate the issue on my test account. To make sure we’re tracking this correctly with our engineering team, it would be super helpful if you could share your file with our Product Support team. That way we can confirm the setup and ensure nothing gets lost in translation. When you have a chance, please include:

• the link to this Forum thread for context
• a full-size screen recording of the issue in action (if possible)
• a link to the affected file (with support-share@figma.com added as ‘can edit’).

We’ll be keeping an eye out for your reply and will continue to monitor this thread for more insights. Thanks again for laying this out. Your patience and persistence here helps make sure we’re making the mark. 🎯

While it’s not related to the issue you linked, there was an older forum post asking about the same bug a long time ago, maybe this one provides more context. 

Hopefully this new bug report is going to bring a bit of renewed attention to it & get it fixed. As Seb mentioned, the functionality actually works, you just have to do it in a specific order (cancel fix position, set L+R constraint, and then go back to set fix position again), so I can’t imagine there’s tech difficulties in this.