You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a very minor issue, but I figured it was best to call it to your attention.
On Chrome 56+, touch events cause an error: Unable to preventDefault inside passive event listener invocation. touchmoveHandler @ baguetteBox.js:107. This is apparently due to a change the Chrome developers made where touchstart and touchmove events on the window, document, or body elements are now passive by default.
I haven't noticed any functionality problems, but it does cause the console to spit out a bunch of errors whenever you swipe. This can apparently be fixed pretty easily by using the touch-action: none CSS style instead.
Just a heads up!
The text was updated successfully, but these errors were encountered:
Thanks for reporting that!
I fear that touch-action: none won't fire the event at all and we use it for the swipe gesture. I'm gonna look into it and find a better solution.
This is a very minor issue, but I figured it was best to call it to your attention.
On Chrome 56+, touch events cause an error:
Unable to preventDefault inside passive event listener invocation. touchmoveHandler @ baguetteBox.js:107
. This is apparently due to a change the Chrome developers made wheretouchstart
andtouchmove
events on thewindow
,document
, orbody
elements are now passive by default.I haven't noticed any functionality problems, but it does cause the console to spit out a bunch of errors whenever you swipe. This can apparently be fixed pretty easily by using the
touch-action: none
CSS style instead.Just a heads up!
The text was updated successfully, but these errors were encountered: