What am I doing wrong? 
-
-
Replying to @akemalakcay
Did you figure this one out? I tried recreating the same scenario and I think it works for me. If it was an issue maybe it's fixed now?
1 reply 0 retweets 0 likes -
Replying to @gavinmcfarland
Not exactly, had to create seperate components for each banner version. It sucks
1 reply 0 retweets 0 likes -
Replying to @akemalakcay
Are you able to send me a link? I'd like to check this out. Feel free to DM me it.
1 reply 0 retweets 0 likes -
Replying to @gavinmcfarland
Can't really share that file, but if you want me to take a look at your problem and show you my solution in your file, go ahead. :)
1 reply 0 retweets 0 likes -
Replying to @akemalakcay
It's ok, I was able to recreate the problem. I just wanted to understand it better to see what was going on.
1 reply 0 retweets 1 like -
Replying to @gavinmcfarland @akemalakcay
Hi
@mwichary can I check, is this something you or your team are aware of? The width of the swapped instance is not being respected. I suspect there are certain limitations on swapping instances inside nested instances of components. Is this intended? https://www.figma.com/file/igeFEbp2MnafAsS12XblVL/Instance-Swapping-Issue?node-id=0%3A1 …pic.twitter.com/3TPOxHg5UY1 reply 0 retweets 1 like -
Replying to @gavinmcfarland @akemalakcay
The engineers are looking at this. Thanks for reporting!
1 reply 0 retweets 1 like -
Got an update: it’s not the easiest of fixes, but we intend to fix it. Please bear with us!
1 reply 0 retweets 3 likes -
Replying to @mwichary @akemalakcay
Ooh exciting. After posting I realised it might be a tough one because normally you can't alter the size of nested instances. Would open up a lot of possibilities though. Thanks!!
1 reply 0 retweets 0 likes
Exactly the issue!
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.