Leaflet: using zoom and drag the map renders wrong in the container

[jabaren]

Hello,

I'm not sure if this a bug, but sometimes when I'm dragging and scrolling (with mouse wheel) the the map sometimes doesn't render in the correct way, e.i :

At the end the map is shown in this way:

the url https://otile1-s.mqcdn.com/tiles/1.0.0/map/18/70026/123550.jpg response with 504 (it can't be my connection).

This happen in http://leafletjs.com/index.html:

I couldn't find the reason why is this happening and I don't know if it's a race condition between drag and zoom.

[IvanSanchez]

I'm not able to reproduce. Can you be more specific in the sequence of actions that trigger the bug?

Does this happen in a particular browser? Does it happen using 1.0.0-betas?

[jabaren]

I'm using :

Leaflet version 0.7.3.
https://open.mapquestapi.com/sdk/leaflet/v1.s/mq-geocoding.js
https://open.mapquestapi.com/sdk/leaflet/v1.s/mq-map.js

Chrome Version 43.0.2357.81
FireFox Version 42.0

Steps:
1.-Drag the map
2.-While the map is moving by the inertia, use the mouse wheel to zoom in or zoom out the map.
3.-Stop moving the map.

[IvanSanchez]

We don't maintain 0.7.3 anymore. Is the bug reproducible with 0.7.7?

[jabaren]

Ok, I'll check it

[jabaren]

It happens on version 0.7.7 (http://jsfiddle.net/ga7155bn/3/)

I think is an error on css translate3d(5307px, -336px, 0px);

the correct position should be translate3d(5167px, -336px, 0px);

[IvanSanchez]

I think this is a duplicate of #2360. @mourner, are you still interested in cherry-picking the changes and backporting to 0.7.x?

[jabaren]

Yes, I think it's a nice UX, Thanks. Cheers

[mourner]

@IvanSanchez yes, looks very likely, let's try cherry-picking this and seeing if it fixes this.

[alex-marin-sv]

Hello.
Any updates on this ? I am running into the same issue. Try this on 0.7.2 and 0.7.7. still same error. It happens when you move the map and zoom out or zoom in at the same time. I reproduced this on the demo map on leaflet.com. (image below). Thank you!

[JPustkuchen]

I can confirm this problem still exists in rc1.

[mourner]

Can you confirm that it exists in 1.0.0 final?

[perliedman]

Since we've had no updates and no reproducible test case for more than a year, I'm going to close this for now.

Happy to re-open if this is still an issue that can be reproduced.