Component responsiveness
M
Mosaad
When we need to create responsive variants with some functionality, variant count goes out of hand since we need to recreate the functionality for each breakpoint.
If there was a way to control breakpoints in components separately from functionality, we would would dramatically reduce the number of variants and it would be much easier to update the functionality later once instead of having to remember to update it for all other breakpoints.
Log In
Autopilot
Merged in a post:
Adjust Children per Breakpoint in Tickers, Carousels, and Slideshows
J
Jakob Hauritz
Add the ability to adjust children at each breakpoint. Currently, this requires creating a separate mobile/tablet specific component, etc.
Autopilot
Merged in a post:
Allow setting breakpoint constraints for components without creating additional breakpoints.
J
Jakob Hauritz
Allow creating components with their own breakpoint constraints, so you can add responsive behavior without adding breakpoints on the main canvas. For example, imagine a blog post component that takes up 60% of the screen.
On very large screens, it looks too wide. You could set a max width for that component and create a new version of it with its own breakpoint. When the screen exceeds the original size, it automatically switches to the new component, even though there’s no breakpoint on the canvas itself.