We have many times have listen about event bubbling in javascript which propogate an event from child element to parent element. So, to avoid such event bubbling in our page we use ...
this means either: location events should always wait until the next turn before deciding how to treat the event, because it might be a promise or might not be (maybe, but this is a breaking change) ...
In fact, this is why this other fullPage.js issue was raised. It seems your Chrome is interpreting the event listener as passive. But clearly mine doesn't and neither the ones in Browserstack. I would ...
Some results have been hidden because they may be inaccessible to you
Show inaccessible results