6.3.3 Bug - Mobile Nav Button Styling

Updated from 6.2.9 to 6.3.3 on a few websites and noticed the styling of the mobile nav button changes/breaks. I cleared cache but it didn’t fix it. Reverted back to 6.2.9 and everything works as it should.

2023-07-26 09_58_55-960×2079_ IMG_2691

====

2023-07-26 09_58_35-Downloads

Correct styling before updating to 6.3.3

2023-07-26 10_03_06-960×2079_ IMG_2694

====

2023-07-26 10_03_19-960×2079_ IMG_2693

Is this the default X headers? If there is custom css styling this could you send that to me? If that’s not the case could you send me your theme options in an export?

Hi @charlie, these sites are running PRO theme and the headers were built using PRO’s header builder. The customization was done using the tools that the header builder provides. A link to the website’s exported theme options are in the secure note.

I think I need a template of your header. The theme options questions were if it was an X header as it might be a stack update issue. I can’t think of anything related currently to this besides the transparent background breakpoint fix. Does adding in the following give you any more clues? Anyway we could get a staging site up with this issue? Thanks

add_filter("cs_debug_css", "__return_true");

Hi @Charlie, A link to the download the header templates of those two websites are in the secure note. Unfortunately I do not have extra server resources to create staging websites at the moment.

Thanks for that. It’s caused by the custom element shim and I will fix that for this element. Have a great weekend!

You’re welcome @charlie , I appreciate your help in identifying and trying to fix the issue.

1 Like

It’s what we are here for. Upon a second look I think we need to remove this part of the Pro4 shim, and add to our migration guide. This is not fixed in 6.3.4, but I think we’ll be making another release this week when we address this. You can also fix the issue by setting a class name to Customize > Class. It doesn’t have to be a class you will use.

Pro 6.3.6 fixed the issue, thanks team Themeco!

1 Like

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.