mapbox-gl-js version: v0.45.0
browser:

Demo Github Page Using v0.45.0
Demo Source
Note that in the demo above when you try to pinch and zoom on the "Capitol Hill Fountain"
it goes off center instead of remaining between the fingers.

Demo Github Page Using v0.42.2
Demo Source
Note that in the demo above when you try to pinch and zoom on the "Capitol Hill Fountain"
it stays between fingers. However, you are unable to pan with more than one finger.
Target should remain centered between the user's fingers without removing the ability to pan using more than one finger.
Target moves off center as the user zooms into it.
I am able to reproduce this error on my setup as well.
This bug, along with #6668, feels like major blockers for any production upgrades from 0.44.2 and below.
This makes using pinch zoom pretty crappy on mobile. Any update on a potential fix here?
Friendly ping. Any plans for a fix?
I have a simple solution waiting for a pull request which fixes this nicely 馃槑
You can try it out here: https://beta.ilmailukartta.fi/
(https://beta.ilmailukartta.fi/js/mapbox-gl.js)
Awesome!
closed by #7191
This is now much improved! Thanks! There's still a little glitch at the start of the pinch gesture... it seems to first move the map for a certain threshold of pixels, and then it computes the correct centre, jumps a little, and from there on in the pinch works fine.
Any thoughts on that initially little "jump"
Yeah, it's basically because of this: https://github.com/mapbox/mapbox-gl-js/issues/7196
If you move the map with one finger and then add a second finger, multitouch event overlaps with the single touch event and creates the glitch..
Also might be related to a fix I made for https://github.com/mapbox/mapbox-gl-js/issues/1832 - try setting setting clickTolerance option when you create the map to 0.
Hello
I'm encountering exactly this issue when using mapbox-gl as node_module import.
npm i mapbox-gl
import mapboxgl from 'mapbox-gl'
Updated package today for double check.
Does this require a new issue to be opened?
You mean the original issue? How to reproduce?
Hi @Mindcraft1 this was fixed as of v0.49.0 so if you have that installed, it should work as expected. You haven't really given enough information for us to help you out here. If you can confirm that you have the correct version installed and are still seeing a bug, you can open a new ticket with all the information in the template filled out and a minimal reproduction of the bug (in JSBin for example) so that we can diagnose what is going on.
Hi I opened #7397
Most helpful comment
This bug, along with #6668, feels like major blockers for any production upgrades from 0.44.2 and below.