Passive event listeners

Re:Passive event listeners by onion2k on Wednesday August 16, 2017 @10:51AM (#15027882)

The change we're discussing here is something that the developer will need to explicitly add to their code;

By marking a touch or wheel listener as passive, the developer is promising the handler won't call preventDefault to disable scrolling.

Shitty developers who are lazy aren't likely to add that to their code if it 'works' without it. They are shitty after all. They won't care about a janky scroll on their webpage. Heck, they probably won't even test different ways of scrolling. Therefore it's fair to think this change is for awesome developers who test things and find that there's a problem, and need a way to fix it.

[ Parent | on HN ]

Re:Passive event listeners by syberspace on Wednesday August 16, 2017 @11:23AM (#15028182)

yes, passive listeners are great. What I don't want in my browser is a static analyzing tool as the first comment I answered to suggested

[ Parent | on HN ]

Re:Passive event listeners by Piskvorrr on Wednesday August 16, 2017 @11:58AM (#15028518)

Well...that's a bummer, as modern JS virtual machines used in browsers all use some sort of predictive code path model, and such static analysis is an integral part of this.

[ Parent | on HN ]