My goal: Create a full browser width state button, which contains a full browser width object (rectangle).
I have tried to play around with this, and found that if I drag the rectangle inside a state button, it doesn't stretch to browser.
However, if I draw the rectangle first set it as stretch to browser width and then just the drag the state button on top of the rectangle, it works out.
I know this might sound as a lame workaround, however only to enable you and meanwhile will also share this bug with our team for further investigation.
Here is a small example file for your reference -
Hope this helps!
Thanks for the work around, but unfortunately this doesn't place the rectangle into the button itself, meaning it has to be always on top, which gives me another challenge of 'layering' the various object I need nested in the button (for layout purposes).
Let's give it a try and we will work together in case of any further challenges.
Thanks Ankush, but I think you misunderstood. I did try it, and as soon as I discovered that the object won't be inside the statebutton I had to stop, since I need it layered below other objects in the statebutton (which is not possible when it's outside the statebutton.
Why is this important? I'm trying to pin objects to the top of the browser (page header). Unfortunately there is another bug that prevents proper fluid layout of objects when pinned. The workaround for this other bug is to lay them all into statebutton & pin just the statebutton. Damned if you do, damned if you don't 😞
See details about the other bug here... Re: fluid width page design & pinning inconsistencies?
Logged one more bug that a composition inside another composition both cant be stretched to browser width.
Now, the closest solution to me looks like what has suggested in the previous thread, i.e making a combination of fluid + fixed width breakpoints.