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
Make sure to add all the information needed to understand the bug so that someone can help. If the info is missing we'll add the 'needs author feedback' label and close the issue until there is enough information.
Describe the bug
When unbinding a, imagemapster clears the map information. During this process, it adjusts its internal map_cache, however there is a bug when manipulating the indexes of the remaining maps in the cache.
This issue only manifests when there are multiple maps under imagemapster control. After the bug is triggered, imagemapster will not correctly manage its internal cache and behavior will be unreliable.
To Reproduce
Steps to reproduce the behavior:
Apply imagemapster to multiple maps (e.g. 0,1,2)
Check the internal data structure map_cache[i].index property and it will correctly indicate 0,1,2
Unbind a map "in the middle of the array of maps" (e.g. 1)
Check the internal data structure map_cache[i].index property and it will incorrectly indicate [0]=0,[1]=2 when it should be [0]=0,[1]=1
Expected behavior
The map_cache[i] index should correspond to the index of the map in the cache
Screenshots
N/A
Desktop (please complete the following information):
N/A
Smartphone (please complete the following information):
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Make sure to add all the information needed to understand the bug so that someone can help. If the info is missing we'll add the 'needs author feedback' label and close the issue until there is enough information.
Describe the bug
When unbinding a, imagemapster clears the map information. During this process, it adjusts its internal map_cache, however there is a bug when manipulating the indexes of the remaining maps in the cache.
This issue only manifests when there are multiple maps under imagemapster control. After the bug is triggered, imagemapster will not correctly manage its internal cache and behavior will be unreliable.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The map_cache[i] index should correspond to the index of the map in the cache
Screenshots
N/A
Desktop (please complete the following information):
N/A
Smartphone (please complete the following information):
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: