Negative, Uzzer. Bugs (and the impact it has on faith/reliability in the product) are supposedly being run up the chain to Product and Dev teams after being witnessed (and hopefully documented by a kindly and patient Customer Service team member yesterday, but I'm still up a river as these bugs are persistent.
Here's a concise, less ranty list.
1) Standard Pre-fab Nav Menu Button alters color randomly when editing in Tablet viewport with Menu Open Selected... random color switches right in front of your eyes as you click in to Typography color, on a slight lag. Having to edit this color style in the first place because it randomly changed on its own.
2) Open Menu button in Settings panel does not RELIABLY producethe pseudo class of "Open" being added to the class for Nav Menu or any other nav object. Reliability is the operative word here - it works some of the time, not others (all presuming that you've designated a custom class to that child object) This is the standard logic - click the button, edit the styles of the "open" state, be it menu icon, the dropdown nav menu itself, the contents within. If you think you're editing something because you've clicked the button, but you're actually NOT because the system doesn't function properly, then you're working in a compromised environment.
3) In Preview mode, the only area in which to test changes you've made to dropdown menus, the dropdown menu in Smaller viewports do not reliably drop down, or they start open, then close upon click, and then do not re-open. I now consider this a feature as it is reliable - it happens about 75% of the time now, in my experience. Note that this will happen even with a fresh Navbar, not one that's been moderately styled.
4) Position and other stylings inherited by children from Parent objects will inexplicably shift and change. This takes place in the editor, especially when key-shortcut cycling through the elements as I investigate one thing or another that's not right. As it is NOT part of the webflow product to log or document every state and status of every element within the site and note the precise object/element, we can only assume that this platform unreliability will continue and that it is incumbent upon users to systematically document all their "coding" and style changes, lest the system decide to wonk out on us... Oh wait, isn't that what I'd do anyways in a classical development environment like Coda? Why am I paying so much for this platform again?
Okay okay, I apologize for that editorial. The frustration is real. And here's the rub... We're all individuals in this platform, with different levels of attention to the minute details, different powers of observation of the minutia, distinct cognitive abilities for pattern recognition, and different understandings of what's working an what's not. Furthermore, we have variable vocabularies and modes of expressing our observations. We professionalize ourselves so we have some common ground on which to relate, communicate and trouble-shoot, but we're all just shooting in the dark hoping to be truly understood. I personally tend to drill in to an issue relentlessly, and while my logic and conduct dictates that I blame self, first, platform last, I tend to observe things that would pass most people by. It's a total pain in the ass - everything seems broken, after a while. A good bug is one that's super hard to reproduce, and it's the age old dilemma of SaaS developers to support customers while at the same time maintaining the line that their product is "Totally great, guys " . That's all fine, except that there's a financial exchange; i pay for access to a platform, and service to support my success in it.
Dave Sloane spent three hours trying to help fix this bloody navigation thing and he saw all the bugs. He's failed to follow up in a timely manner with the things he said he'd follow up with (emails for how to do this and that, a re-do of my menu as he claimed he would explore and escalate the bugs he witnessed as I pointed them out in our screen-share sessions, and I'm going to have to assume at this point that I'm on my own. Is the bridge burnt and I'm no longer a valued customer because of my discontent? I don't know. I DO KNOW My client will NOT be happy with the lack of progress, and I'm going to have to keep quiet my concerns about Webflow because I was the one who advocated he go down this path on this platform (as opposed to Wix or Wordpress).
Okay, back to work.