New road segment disappears after drawing geometry

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

  1. Draw a new road staring at an existing node between two segments
  2. Finish drawing by double clicking on last node (as usual)
  3. The new road vanishes in thin air

I would expect the new road segment to be in the map, unsaved.

Environment where the bug occurs…:
ROW
Permalink:
https://waze.com/editor?env=row&lat=7.25055&lon=-2.36732&zoomLevel=17
Browser name and version:
Chrome 137.0.7151.56 (Mac)
Are you using scripts? Please detail which ones.:
Map Overlays
WME Toolbox
WME Advanced Closures
WME Junction Angle Info
WME Permalink to several maps - Norwegian edition
WME RA Util
WME Route Speeds (Mapomatic fork) - currently disabled in the scripts options
WME Street to River plus (mod)
WME Map Editor Magic (deactivated in tampermonkey)

Screen recording:

2 Likes

I reproduced it in incognito mode on first try. It happened for the first time this afternoon today. And has happened several times, but not always.

I am beginning to suspect the Adobe extension to be causing trouble:

1 Like

I can reproduce the error in incognito mode regardless of the toggle on/off on the Adobe extension. Perhaps a restart of Chrome is necessary? Or to remove the extension entirely using the “remove” button?

Hi @CuttySpark,

Thank you for your report. We have an internal ticket open to investigate this issue. It does not seem to be related to a specific browser or scripts/extensions.
I will let you know once we have more information and after the case has been reviewed.

Best regards,
Olesya

I’m having this same issue. It worked fine in practice mode, but the road disappears when in the actual editor. I tried on Chrome and Safari.

Steps to reproduce this issue:
When you create a long road (maybe 1 km long), after you double-click to keep the segment, the segment disappears from the WME.
It doesn’t occur with small segments.
Here is a video of the bug:

WME Beta Permalink:
https://beta.waze.com/en-US/editor?env=row&lat=20.66159&lon=-101.34604&marker=true&zoomLevel=20
This bug occurs in:
ROW
WME Beta version number:
v2.299
Are you using scripts? which ones?:
No scripts

1 Like

This issue has been reportedly fixed in WME beta v2.302

3 Likes

Hello @CuttySpark @velezss @Bleaudoggie,

Could you please check whether you still experience the issue? It should be fixed in production as well.

All the best,
Olesya

I’m still having the issue. It works in practice mode, but not in the actual editor.

I am not able to reproduce the bug.
Best,

1 Like

Hi Olesya,
I loaded WME and logged in using incognito mode and tried to add a new road starting at a node between two segments. (This one: https://waze.com/editor?env=row&lat=5.85911&lon=0.36896&marker=true&zoomLevel=16&nodes=254715912 )

The new segment disappeared just as before. So not fixed in that test.

Hi @Bleaudoggie,

Thank you for your update. Is there any chance you could capture this bug in a video?

Best,
Olesya

Hi @CuttySpark,

Thank you for your response. I have tried drawing a segment from the node you have provided, but I am not sure where to finish drawing in order to reproduce the issue. I have tried different ways, but so far all my attempts have been successful regardless of the segment length or bbox. Would you be able to record a video showcasing the problem?

Best regards,
Olesya

Hi Olesya,
I put the new recording in the same shared folder. Can you reach it?

Kind regards
CuttySpark

Hi @CuttySpark,

Thank you, I can access the new recording. I will have to test it further, as I have not been able to reproduce the issue yet.

All the best,
Olesya

Here’s a video. I’m using Chrome Version 138.0.7204.93 (Official Build) (arm64), but I also see the issue in Safari.

1 Like

Same for me. In practice it works, in real edit, it isn’t.

1 Like

Hi @Bleaudoggie @Raitis_speedy,

Thank you for your input. I have double-checked your use case, and it has not been fixed in production yet. I will provide an update once the fix is available.

Best regards,
Olesya

1 Like

Hello there @Bleaudoggie @Raitis_speedy,

We have had a fix deployed in production for this particular use case.
Would you be able to check whether the issue is still reproducible for you?

Thank you,
Olesya

Hi @CuttySpark,

Could you please let me know if you are still experiencing this issue? If so, is it occurring in the areas you mentioned before? It is not reproducible for me in the location you reported initially.

All the best,
Olesya