For me personally – although I understand perfectly well why this is happening – it is a huge shame that Core Developers are not fighting for this functionality.

However, I’m more looking forward to the theme.json file in version 3.0 with the hope that there will be more native solutions for CSS responsive blocks options, rather than just clamp() for typography, which is not perfect anyway.

I’m also looking forward to normalizing the tools and the Responsive Controllers preview itself.

For now, however, in terms of navigation, it is anyway – even with a plugin – to register nav menus and use the old system, as this one we will quickly and efficiently import into the new solution in the future.

Translated with http://www.DeepL.com/Translator (free version)