Can't move map (error: coordinates must contain numbers)

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

This Error is somehow related to Map Notes, when disabling notes, I can move the map

Hello @ypcyc,

Thank you for your report. The issue has been reported internally, we are working on it. I will keep you posted on the progress.

Kind regards,
Olesya

1 Like

Hi @ChrisDeBirk,

This is the bug I mentioned earlier and wanted to follow up on.

By the way, thank you for your help on chat earlier.

Regards,
Nataliia

1 Like

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)

Environment where the bug occurs…:
ROW
Permalink:
https://waze.com/de/editor?env=row&lat=50.21291&lon=8.89516&zoomLevel=14&mapComments=292871
Browser name and version:
Chrome Version 135.0.7049.115 (Offizieller Build) (64-Bit)
Are you using scripts? Please detail which ones.:
Many, but disabled them.

Good morning,

the problem is there for a longer time but could be solved by force reloading the page.

This work around does not help anymore. So I refreshed WME frequently, in this case I opened a new tab. Problem persists.

Initially I could adapt the MC, but then it failed completely.

It’s not about moving the mal, it’s about changing the border of the MC

1 Like

This is a really weird bug :hushed_face::upside_down_face:. Moreover, there is another :exploding_head: detail:

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

Additional video with console opened as well.

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.

Is this a…:
Standard bug
Steps to reproduce this issue:

  1. Follow link to area with comment:
    https://www.waze.com/editor?env=row&lat=5.57636&lon=-0.23788&marker=true&zoomLevel=15
  2. Check that you can move the map a bit around
  3. Select the map comment (&mapComments=362687)
  4. Map can’t move anymore.

Environment where the bug occurs…:
ROW
Permalink:

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)

1 Like

Here is the screen recording.

Just checked. Same happens in Safari And Opera.

Another map comment with that issue.

https://waze.com/de/editor?env=row&lat=49.87197&lon=8.93334&zoomLevel=18&mapComments=325495

1 Like

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.

Best,
Olesya

Reported fixed in WME beta v2.302

2 Likes

Hello all,

The issue seems to have been fixed in production as well. Could you please verify on your end?

Thank you and regards,
Olesya

1 Like

I approve. This issue seems to be solved. :white_check_mark:

1 Like