Stacks should dynamically shift content in Preview
Create component - + New state (bigger than the default) - Merge the component with another one or another element into a stack -
Preview mode - click the component to change state and the stack doesn't respect padding .
Please note that stacks is a feature that is intended to be used at design time, and does not dynamically shift the stack in preview. I’m going to rewrite this particular request to be more precisely about the latter suggestion.
Stefan Dickerson commented
Yes please! Trees, accordions, progressive disclosure forms, and the like would all come to life without us having to draw up (and wire together) every permutation of open and closed things!
I wish it could work with the stacks. It works when you are editing the file, but when you publish the prototype it doesn't.
I have the same problem, since the beginning of our project I have some expanding components and it is very important to move the content when the component expands - in design mode it is just perfect, but in preview mode, it isn't.
Cyrill Studer commented
Yes, I would like the stack to update when a component inside it auto-animates to a larger or smaller state!
Absolutely crucial! please add this ASAP. It would help with my workflow immensely and save a ton of time.
Torbjörn Hedberg commented
+1 here as well. Works perfectly in the Design mode so it's a shame it doesn't in Prototype mode.
Brandon Beiler commented
Constantly run into scenarios where this would be insanely helpful. +1
Gabriel Häggebrink commented
+1 Here! Missing this virtually every project I do, would be an amazing addition.
When I launch a preview of a page including a component whose shape changes (addition of an element in the component) it overflows despite the use of the stack function.
Phil Bowell commented
In the same way that stacks resizes it would be great if screens could resize their height dynamically. This would allow for auto-animating between different component states and the elements around them to move but retain the spacing.
An example would be in a form that works with progressive disclosure based on selecting different answers. Rather than animating between two screens, it could be between two states of a component and the screens responds dynamically.
When you have a lot of vertical content, duplicating artboards to create a dropdown menu requires a lot of effort, especially when each message has an accordion style dropdown menu. It would be nice to have the benefits of Stacks for this behavior.
Rigel Closet commented
Auto animate? the point of components is to make everything happen in one art board! please implement this feature, i though stacks will take care of it, until i tried !
Expanded/collapsed states are useless as long as preview mode does not adapt to them. A real shame and lost some hours due this particular design...
Since the stack dynamically expands (changes) in design mode, I have spent some time understanding that this does not happen in Preview.
I can understand why people might think this is annoying to have by default, but it could be an additional option when setting up a stack..
Anyways, it would really be incredibly useful to have this behaviour in the preview too.
I'd like this feature also, it feels like a natural fit for Stacks. What happens now is the opened state overlays the content beneath the closed state.
Elaine, this will not currently work (with auto-animate or otherwise) unless we put all the page's content into one giant component and manually position the content for each state. This precludes making a non-scripted flow.
FWIW, I hope I'm wrong, but I can't get this to work. Yes, I have the most recent version.
Florian Pürschel commented
It is so sad that this feature is missing. I have a list with a lot of expanding elements. When changing the state to "expanded" everything adjusts just fine in design mode. Unfortunately it does not adjust in preview which forces me to add 2342346456 additional artboards to present every possible combination of expanded elements. This is really really annoying
I could really use this feature in prototype now. I have a sidebar with a ton of filters where I have expanded/collapsed states. Right now the expanded state in prototype just goes over the other elements.
The Problem: I have two components A & B. In A's default state component B is y px beneath A. Component A size expands or contracts by z px and changes to a new state. Currently, component B is now y + z px from the bottom of component A.
The Solution: Components that can change shape between states should "push or pull" other components by fixed padding defined assumed by the system or defined by the designer. This behavior should be able to be chained between multiple components & other objects.
Applications: Expandable lists, expandable cards, & my quality of life improves.
Savings: No need to create an endless number of artboards to express simple behavior between components or super long write-ups to hand off to a developer.
Current Time Cost: Per component, n, that has a number of states, y, on the artboard a designer has to create (n*y)! number of artboards to describe the screen behavior. This is a massive pain in the butt! It costs countless hours of write-ups and reconciliation with developers.
This wold be a really cool thing to implement. You already to auto-animate so creating a stack that animate should be relatively simple. Let's say you have a stack of expanding components. Then as each component expands, the stack responds and expands as well.
Two adjacent buttons [components in this case] each with similar states (one hover and one dialog popup) are not behaving as per the expectation. When the pop up dialog state is active, the other button is overlapping onto the dialog. Check the video. This is a limitation. Creating a separate artboard and linking to it should not be the solution when you have components in place. I am unable to use two components with states adjacent to each other or one below the other.
Also, it would be nice to see a component with expanding state pushing the component below and likewise pulling it back to its original position when in collapsing or default state. This could help in a lot of situations. Example - accordions.