Poligons move instead of zoom (when they should zoom as well)

[VyacheslavLukin]

Issue presented on the attached screencast

[AlNedorezov]

@VyacheslavLukin, I was not able to reproduce the described issue. I am using release v1.5.
Is it a common behavior, you are experiencing with zoom-in, zoom-out buttons?
Please share the following information relating to the described issue:

• the version of the system you are using,
• was the issue spotted during the acceptance of the markup, or during the markup process itself,
• are there any error messages in the chrome console after zooming images,
• used OS,
• used browser and its version.

[AleksandrShepelev]

We use version 1.5
Sometimes during the acceptance I noticed contours on wrong place (like on Vyacheslav GIF).
But bug is not reproduced every time.

[VyacheslavLukin]

Moreover, sometimes we see pictures like following

As you can see this is very similar to the GIF. I doubt that person who marked picture, places polygons "in the air". However, we could not accept this picture, or can we? Maybe it's representation issue?

[VyacheslavLukin]

To answer your questions:

• Ubuntu Linux 16.10
• During acceptance
• there is the error message
  
• Google Chrome | 59.0.3071.115 (Official Build) (64-bit)
  Revision | 3cf8514bb1239453fd15ff1f7efee389ac9df8ba-refs/branch-heads/3071@{#820}
  JavaScript | V8 5.9.211.38

Information for the user from toloka:
OS - windows 10
Browser - Chrome 59.0.3071

Another user for the same issue:
OS - IOS 10.10.3
Browser - MOBILE_SAFARI 10.10.3

One more:
Windows 10
Opera 46

[AlNedorezov]

@VyacheslavLukin, thank you!
We will look into it.

[AleksandrShepelev]

I found how to reproduce it in chrome (windows):

1. increase zoom by app tool.
   

2. mark a car

3. decrease zoom in browser (not an app tool)
   

polygons will move. Same happens in many combinations of browser zoom and your tool zoom.

[AleksandrShepelev]

in acceptance mode, there is a way to "fix" moved markups (but I don't know, if it can really fix it or not):

1. Moved markup:
   

2. increase zoom in app:
   

3. decrease in browser (I've repeated cycle 2-3 two times to achieve result):
   

can we fix it that way and accept or they will be of a bad quality?

[AleksandrShepelev]

Finally, we caught the bug.

1. Create new pool.
2. Markup one picture with one zoom level (default)
3. Move to next picture
4. Markup second picture with "+" zoom in app
5. Move to next picture with zoomed current picture
6. Markup third picture without zoom again.
   result: polygons ok - polygons moved - polygons moved

so, it probably means that zoom state is saved between pictures