Open nicraMarcin opened 4 years ago
Agree with this solution, +1
Also agree.
I have the same issue in Chrome latest, breaking my mobile version (scroll doesn't work at all), but I see it's being worked on. Thanks a lot!
@matiyin I also noticed the performance penalty on mobile. But for mobile, there should be no need for polyfil
like this.. instead I use a conditional component when detect it is touchable device.
This has already been PR-ed: https://github.com/mdbootstrap/perfect-scrollbar/pull/945
Apart from your proposed fix, it also uses feature detection, so it continues to work as intended on older browser versions, without support for the new syntax. Details here.
Also of note is that https://github.com/mdbootstrap/perfect-scrollbar/issues/873 had been open for a while asking for an option to set the listeners' passive
value.
According to https://caniuse.com/mdn-api_eventtarget_addeventlistener_options support for the options/boolean is pretty widespread - implementing the options feature detection doesn't seem too important?
You can add via CSS
touch-action: none;
to your scrolling container. That helped me to get rid of the error
This error continues. How can I avoid the warnings in the browser console?
I don't see the PR that was mentioned in this issue anymore and the current head doesn't have a fix yet.
A little more concerning is that there hasn't been any commit activity since 22 March 2022, so not sure if we will see a fix in the near future.
Any update on this issue? Is it really that hard to fix? :)
Any updates here? Would be great to get this
Using
perfect-scrollbar
in chrome produces a lot of Violation issuesadding
{passive: true}
should resolve this issue