Lazy loads lead to switching mobile menu

Hey Jasmin;
Hard to say as I can’t investigate the problem “live”, but can you try if adding icon-home to the lazyload exclusion list helps?

frank

Hi Frank,
I tried it, but unfortunately it didn’t resolve the issue.
Jasmin

OK, do you have a Staging/ Developement/ Acceptance site where you could leave it broken for me to look into?

Yes, sure: https://spielwiese.packlisten.org/

Do you need a WP login or ftp access?

nah, no need for access, just want to look at what lazyload is doing in the frontend (HTML) ??

Alright, thank you for your time and effort! ??

Tested on Android with Chrome & Firefox but can’t seem to reproduce said behavior jazzminus, can you double-check?

Hm, that’s interesting! I am using Chrome and Safari on iOS 12.2 on iPhone 6. A friend showed me the issue in Chrome on Huawei with Android a few days ago.

and can you reproduce https://spielwiese.packlisten.org/ when you try now?

Yes, in Safari and Chrome.

can you share a screenshot of the broken state?

Sure! To reproduce I flush all caches (WP Super Cache and Autoptimize, also the browser cache).

https://spielwiese.packlisten.org/wp-content/uploads/IMG_1213.png is Safari on first load.
https://spielwiese.packlisten.org/wp-content/uploads/IMG_1211.png resembles Safari on second load (and when refreshing again and again).

https://spielwiese.packlisten.org/wp-content/uploads/IMG_1216.png is Chrome on first load.
https://spielwiese.packlisten.org/wp-content/uploads/IMG_1217.png is Chrome on second load (and when refreshing again and again).

OK, some tests:
* do you still see the issue with lazyload active but CSS optimization off?
* do you still see the issue with lazyload active but CSS optimization on but “aggregate CSS” off?
* do you still see the issue with lazyload active but CSS optimization and “aggregate CSS” on but with menu-plus/functions/css/navigation-branding.min.css added to the comma-separated CSS optimization exclusion file?

frank

Unfortunately I see the issue in all three cases.

Hm … an I presume the issue also persists if JS optimization is off?

Before digging deeper, can you on your non-prod site install the beta of 2.5.1? you can download it here, it has a lot of fixes for the lazyload functionality and just maybe this automagically fixes your issue too? ??