User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:63.0) Gecko/20100101 Firefox/63.0 Firefox for Android Steps to reproduce: 1. Open maps.google.com or babylonjs-playground.com/#12WBC#69; 2. Use two fingers to zoom-out. Actual results: The map zooms very in and then zooms out slowly. This phenomenon occurs with the same results in both Google Maps and Babylonjs. Expected results: It should've only zoom-out'd to the amount indicated in the delta between the fingers. No zooming-in required.

This is done using the touch screen on my Surface Book.

Hi, I've managed to reproduce the issue above on the latest Nightly 65.0a1 20181123100103 on Win10 x64 using a Surface Pro 4 i5. I am assigning a component to this issue in order to involve the development team and get an opinion on this.

Masayuki, does this look like a P2?

Sorry for the long delay to reply. I'm still not sure what happens with this. When I test which events are fired with touch screen of SurfaceBook 2, I see pointerdown, touchstart, pointerdown, pointerdown, touchstart -> (pointermove/touchmove) -> pointerup, touchend, pointerup, touchend on https://d-toybox.com/studio/lib/pointing_device_event_viewer.html with preventing default of touchmove and touchend. The default action of this operation is Zoom Out, but Google Maps prevents this default. So, they handle these events directly. Chome fires: pointerdown, touchstart, pointerdown, touchstart -> (pointermove/touchmove) -> pointercancel, pointercancel, touchend, touchend. Google Maps is important and this report requires more investigation. So, I think that this should have higher priority than usual.