Is this a…:
Standard bug Steps to reproduce this issue:
Open WME try to move the map.
In DevTools I see “Uncaught Error: coordinates must contain numbers”
Environment where the bug occurs…:
ROW Permalink:
Browser name and version:
Edge Version 135.0.3179.73 (Official build) (64-bit) Are you using scripts? Please detail which ones.:
None, tested in Incognito without scripts
Is this a…:
Standard bug Steps to reproduce this issue:
Move a point of an area object, no reaction and
Uncaught Error: coordinates must contain numbers
at a (third_party-dfaf9ce015e06ba9.js.gz:2:3431302)
at third_party-dfaf9ce015e06ba9.js.gz:2:1640260
at third_party-dfaf9ce015e06ba9.js.gz:2:2884270
at s (third_party-dfaf9ce015e06ba9.js.gz:2:2883897)
at l (third_party-dfaf9ce015e06ba9.js.gz:2:2884142)
at g (third_party-dfaf9ce015e06ba9.js.gz:2:1639706)
at m._onMouseMove (third_party-dfaf9ce015e06ba9.js.gz:2:1214837)
at r.handle (third_party-dfaf9ce015e06ba9.js.gz:2:3686839)
at r.mousemove (third_party-dfaf9ce015e06ba9.js.gz:2:3686555)
at initialize.triggerEvent (third_party-dfaf9ce015e06ba9.js.gz:2:309399)
That is weird. It seems like it has something to do with that particular MC from what I can tell.
Whenever I select that MC, I can’t move the map. I deselect the MC and can move the map.
I select a MC that is just to the west of this one and no issues moving the map either.
I tested in my area as well with no issues. I even copied the comments in your MC to see if somehow it may have something to do with it ~ no issues.
I also tried adding an AP under a portion of it to mimick your area somewhat and no issues either
The uncaught error mention aby Alpha_VA happened after I selected that particular MC (but not until I moved my cursor and the count kept increasing every time I moved my mouse until I deselected the MC.
When I selected the MC to the west, I didn’t get the error.
Browser name and version:
Chrome v. 135.0.7049.115 Are you using scripts? Please detail which ones.:
No scripts, tested in incognito mode.
(“Something went wrong” when adding 9 MB screen recording)
Thank you for your input @Alpha_VA I have updated the internal ticket accordingly. The fix is still in the works. I will let you know once it has been finilised.