unfortunately not, in fact, I managed to do this, digging on Scrolltrigger codebase yesterday and I even disabled visibilitychange and DomcontentLoaded, because I can manage those by my own in my context provider, but keeps firing the event, its kinda spooky, I attached a video of the problem, as you see, in the video the size of the elements doesnt change; also the first time that I tried to scroll the spooky resize doesnt happens, it happens latter, unconsistenly, its like Scrolltrigger adds a eventListener on window resize and everytimes the resize occurs it happes the spooky action even if autorefreshevents are just those you provided, I even experimented that issue in ScrollTrigger webpage, everytime mobile navbar hides, the animations inside the boxes calls a request animation frame, is there a way to overcome this?, im tired about my client complains
https://drive.google.com/file/d/19r3uzfIjY3zm5--RTB0pZ_bVooNxfRMF/view?usp=sharing
P.D. Samsung internet behavior is wayyyyy more spooky than chrome because the resize is more agressive since samsung internet has 2 navigation bars
P.D.D I finally managed to work around this, the problem appears to be that the browser itself causes those spooky blinks on resize events, I used the chrome remote devtools to debug this feature inside my phone and I couldnt find any hint in scrolltrigger code, so I decided to use the old trustable (body fixed and scrollable), so the navbar will not hide but also my experience will look pretty homogeneus