Won't fix [31396] Tooltips in world map doesnt disappear in some circumstances

[Dony]

Game version: v1.103-beta.1-(ffbd638) (2020-04-08 20:25)
HTML5: no
Game world: zz1
Browser + version: Firefox Quantum 75.0 64-bit
Flash Player version: 32.0.0.344
Operating System: Windows 10
Screen resolution: 1920x1080
Account name: Dony
Humans or Elves: Elf

Reproducibility: 5/5 (1/5 = happened once; 2/5 = happens randomly; 3/5 = happens sometimes; 4/5 = happens often, but not always; 5/5 = happens always)

Quest title: none

Current situation:
In some circumstances tooltips in world map stays there and doesnt disappear

Expected:
Tooltips should disappear in that circumstances

Reproduction steps:
1. Enter world map
2. mouse over Relic button
3. move with mouse pointer really fast to left or right side
4. observe that tooltip with relics stays on screen, you can scroll world map through it, or you can click to enter city through it

 

[Loynis]

Confirmed

 

[Loynis]

This doesn't happen when you open the world map for the first time after logging in. Starting from the second visit and later on, the bug is there. And not only relic button is affected but also the other three buttons are (Navigate to Scout, Show Provinces Overview, Navigate to city).

Besides, HTML is also affected, but with different behaviour. The tooltip does not appear at all.

So, i would like to alter the reproduction steps a little bit:
1. Login
2. Open world map
3. Mouse over Relic button, or the other 3 buttons mentioned above
4. After tooltip appears, move with mouse pointer really fast to left or right side
5. Observe: Nothing wrong
6. Go back to city, or open research tree
7. Open world map again
8. Mouse over Relic button, or the other 3 buttons mentioned above
9. (HTML). Observe: Tooltip does not appear
9 (Flash). After tooltip appears, move with mouse pointer really fast to left or right side
10 (Flash). Observe: Tooltip stays on screen, you can scroll world map through it, or you can click to enter city through it

 

[Marindor]

This issue was discussed and we currently don't see the need to act on this issue as complexity and solution heavily outweigh the benefit of fixing it. Therefore we will now archive this bug report thread as such.