An unfixed prototyping bug in figma
HTML-код
- Опубликовано: 9 сен 2024
- A prototyping bug in figma that you should know about.
This bug was reported to figma, they know about it, and still, for more than 6 month (at the time that this video was made) its not being fixed.
#yarivbe #figmaprototype #figma #figmatutorial
I see this bug for years now. Basically animations within interactive components are not compound but they stop and the top parent only is animated. I don't get why they never responded to any bug report regarding that specific bug..
Yes, your are right. I have no idea why they don't fix it. It's quite annoying...
Very weird, it still doesn't work after the update. This means that all design systems are not prototype compatible, as they all has this nested structure e.g. for FAQs components.
Yes, exactly - its even more weird because its not consistent - on some content card components it work and some not. Definitely frustrating...
@@YarivBE
I think it has to do with sizes, as you know they don't allow changes in sizes of any instance's inner children, so maybe because the accordion interaction is changing the height of the last instance it doesn't work, maybe if the interaction was to change to a variants which only has a different color it would work? I will try it. In all cases this is not an excuse for them because the point of the prototype mode is to change things, whether they are instances or not.
@@mo_1023
Well, i dont fully get why is that bug happening, but after they visited my file and confirmed that yes, there is a bug, then its 100% there is :)
If you find out something interesting about it - will happy to know! Thanks :)
This bug is still present today in the last version of Figma... I just encountered it while trying to create a "press to delete" feature. Tried everything, it just doesn't work. Anyone found a workaround ?
Yep... bug is still there :) It just doesnt work, more than a year and there is no solution yet, unfortunately.
Hi Yariv, thanks for telling us about this bug. I'm having trouble with a button component set. When I place it in another component, it acts strangely in the prototype. For example, the button that's supposed to be outline ends up being filled instead. I'm not sure if this is related to the bug, but I've tried remaking it multiple times, and it's really frustrating.
Hi Behnaz and thank a lot for you great feedback 🙂Definitely could be related to this bug, but i need to see the file in order to know it for sure.
If you want, tag me on your file and i'll take a look see if thats the case.
Thanks :)
Thank you
You are welcome :) Important to know... And even after all the latest updates - still not fixed 🙂
Thanks for feedback!
Hello @Yariv BE is the bug fixed now?
Hi Afia. Unfortunately, not yet... Very annoying issue :(
The fill is not filling colours to the vector it only colours outline of the shape.what can i do
Hi there :) See if the vector (icon you took from somewhere maybe?) outline is a fill or a stroke. Sometimes, what send to be a stroke is actually a fill that looks like a stroke, but it's actually not. It's a stroke that was converted to a fill. Let me know if that's the case?
Sir i need some help to solve my problem 🙏
Hi there :) What can i help with? Please le t me know 🙂
And not fixing this bug after you told them about it is unprofessional, we're f*cking paying.
Yep... thats definitely a point - and promised me twice actually that it will be fixed and it didnt happen. Weird...