@cyberdave and @Tom,
It’s great to see advanced features continue to be added to Webflow, but I have to put in a strong vote for a couple of rounds of QC cleanup on the product. This bug is so embedded in months and months of work that I have done that trying to re-create the pages without it is a practical impossibility. I have had the luxury of being able to turn away from that project for a while, and hoped that this would get fixed in the interim, but apparently not.
I am experiencing a number of buggy behaviors now in Webflow that are really impinging on my ability to get work done in it. I haven’t taken the time to document and report them yet for two reasons:
- As long as I’m working in sites that include this nested symbol bug, it seems like all bets are off - anything I see could have that at its root.
- It really does feel like the Webflow team has elected to prioritize adding features vs. product stability.
For the many people who are using Webflow for relatively simple pages and sites, these things are probably not an issue, so perhaps I’m an outlier, and it doesn’t make sense to fix issues that not many people are encountering – yet.
I would hate it if that were the case, because the Webflow UX is far and away the best of all the wysiwyg html editors I’ve checked out, and I want to rely on it as my main tool.
Nested symbols are second nature to many Illustrator and Photoshop users, and provide a level of control and power that is indispensable once you get used to it. I really hope that you get this bug prioritized, and that you go the extra mile to make the fix support for nested symbols as opposed to the alternative, protecting the user from inadvertently creating them. But until one or the other happens, it’s a serious bug that really does threaten to bring my Webflow days to a close if I’m forced to put in weeks of effort to rebuild the projects from scratch.