Testing with 1.3 there are a few editing issues with the Nav block:
Nav menu blocks cannot be previewed / edited in the editor
Nav Dropdown blocks do not accept child blocks via any means (copy/paste, adding via the + button or adding via the editor toolbar button). This also makes existing child blocks contained within these blocks uneditable. (This issue may have also been present in 188.8.131.52.5)
This is fairly urgent for us as we are midway through a release
react-dom.min.js?ver=18.2.0:10 TypeError: n?.menuSelected?.includes is not a function
at e (index.js?ver=1.3:3:3420064)
at wt (react-dom.min.js?ver=18.2.0:10:47637)
at js (react-dom.min.js?ver=18.2.0:10:120584)
at wl (react-dom.min.js?ver=18.2.0:10:88659)
at bl (react-dom.min.js?ver=18.2.0:10:88587)
at yl (react-dom.min.js?ver=18.2.0:10:88450)
at il (react-dom.min.js?ver=18.2.0:10:85274)
at ol (react-dom.min.js?ver=18.2.0:10:83831)
at v (react.min.js?ver=18.2.0:10:3385)
at MessagePort.ce (react.min.js?ver=18.2.0:10:5527)
And yes custom content is toggled - this was all working fine when we created it a couple of weeks ago and the nav dropdown still works (we had already added the Menu child block to it prior to the bug being present).
Thanks for that information. I can reproduce the WordPress menu issue, and will have a fix for this in the next update (if you need this in priority, please contact support so that we can forward a temporary fix to you).
As for the custom dropdown, I recall this already being an issue on your end if I’m not mistaken? Do you have a staging area where I can maybe take a look?