fw2jp

Thank you very much for your prompt response and for your willingness to address this issue.

I see, so there could be potential conflicts with our theme or plugins. I will investigate this possibility thoroughly.

I would like to inquire about a potential issue I noticed in the code changes between versions 4.4.3 and 4.4.4. In version 4.4.4, I observed that the e() function (sessionStorage check) is defined in the global scope, while the f() function is defined within a closure. This structural change might be causing scope access issues when the pageshow event handler attempts to call the e() function.

Here’s the specific code structure I’m referring to:

4.4.3 (working):

!function(e,n){for(var t in n)e[t]=n[t]}(window,function(e){
    function f(){...} // sessionStorage check function
    window.addEventListener("pageshow",e=>{f(e.persisted)});
})

4.4.4 (problematic):

function e(){...} // global scope
!function(t){
    function f(f){...} // within closure
    window.addEventListener("pageshow",e=>{f(e.persisted)});
}

Could this scope management change potentially be related to the TypeError: e is not a function error we’re experiencing? I would be grateful for your thoughts on this matter.

I will continue testing on our end and look forward to the updated version you mentioned. Thank you again for your time and effort.