Pro 6.0 b4 upgrade from 5.1.5 issue: responsive hiding classes not applied to nav in header

Just upgraded on another site from 5.1.5 to Pro 6.0 b4, and noticed that the responsive hiding classes are not being applied correctly to the Navigation Collapsed element in my header.


At smaller sizes, the Navigation Inline element is hiding as expected

This is occurring both in the editor and on the front end and persists after clearing the site cache and the Cornerstone System Cache.

This may be related to another oddity I have just noticed with this element. Although it is behaving like a Navigation Off Canvas element, it is showing up in the inspector and dev toolkit inspector as a Navigation Collapsed element.

@kory This is the same issue I have as discussed in another thread so I guess I am no longer the only one with this issue.

To add to this, and the last point regarding the naming of the element, this site was built pre Pro 4.3.0 when the new way of working with dropdown, modal, and off canvas elements. I don’t now have any access to a pre Pro 4.3.0 site, so I can’t check this thoroughly, but when that update happened, it was not necessary to re-build the Navigation elements, so what was the off canvas navigation standalone element remained as such, and any future additions used the new modular system.

It is one of these old off canvas navigation elements that is now not having its breakpoint hiding classes applied.

Here’s what I’m seeing in the inspector for this old element:
image

And here’s what a newly added Navigation Off Canvas element looks like:

Hope that helps to shed some light on the matter.

The majority of sites I manage were built pre Pro 4.3.0 and have been incrementally updated and upgraded over the years, so there could be many others who will come across this issue on upgrading to 6.0. Is there any way of doing a deep reconfiguration from one element to another. applying all relevant styles from the old off canvas navigation element to the new modular set up? This could mean you no longer need to keep all the backwards compatibility in place, though it may not be feasible at all (certainly not for this cycle so close to the finish line!)

Further to this, I was able to find a way of quickly replicating the issue:

Add a Navigation Collapsed element.
In the dev tools inspector, find the legacy_region_detect toggle and set it to true.
Try applying the breakpoint hiding options.
They will not be applied and the element will not hide correctly

Thanks, @arthurodb…we’ve been kind of chasing this one a bit as mentioned above, but haven’t been able to replicate. I will put in some notes on this and see if I can figure out what’s going on so we can address it. All of the details you’ve provided will be a huge help!

I can confirm I have another site with this issue that I tested today.

This seems to be exactly the same as mentioned above. The element is marked as a “Navigation Collapsed.” This is the same in the other site with issues. This particular site was built in 2020. This seems to be the only real upgrade issue on this site which utilises a ton of conditions and pulls data from Salesforce into the builder with a custom looper.

The site in the other thread was also built around the same time - specifically 2020/10/06

Removing the hidden break points in the “Customize” section and adding them again has no effect. The only way to resolve this is to rebuild the element.

2 Likes

This will be fixed in the next release. Please contact me if you have issues. Thanks for testing the beta!

I can confirm that on upgrading this test site from Pro 5.1.5 to Pro 6 RC1 this issue remains.

Apologies for the issue. Do you have a site we could access in a secure note?

Yes, it is in the original thread I created about the issue.

Here is the link to my thread with a secure note. I posted in this thread as it had a bit more details and you guys had mentioned it was fixed which it isn’t.

Sweet thanks a bunch, we’ll take a look and get that fixed.