New WME v2.331

[rompompom]

The scripts tab has no spacing / indent on the right and left side anymore:

Seems like width has been set to 100% instead of 90%, or something like that.

[EloheiYishi]

Seems like it is script dependent now, maybe the idea was to remove excessive padding.

[Nataliia_Staff]

@EloheiYishi

This change between the rows is very inconvenient for the work flow. Please remove the tick mark, as we already have the coloring, which is quite sufficient. If the tick is needed, please add it to an accessibility features option in the settings.

Hi @EloheiYishi,

Thank you for the feedback. I will pass it on to the team to discuss possible ways to improve.

Regards,
Nataliia

[Nataliia_Staff]

@rompompom

The scripts tab has no spacing / indent on the right and left side anymore:

@EloheiYishi

Seems like it is script dependent now, maybe the idea was to remove excessive padding.

Hi @rompompom,
Hi @EloheiYishi,

Thank you for flagging the problem. I am checking on it with the team.

Regards,
Nataliia

[MatthiasGor]

@Nataliia_Staff

@MatthiasGor

@krzycholub

Thank you for the feedback. This topic has been raised in previous versions, so we will open a feature request and I’ll make sure to highlight its importance to the team.

Regards,
Nataliia

Maybe it’s worth considering a mechanism that will allow our to accept or reject individual suggestions?

At the same time, consider the possibility of moderation, along with the possibility of blocking edits by L5 and L6.

[Wcrhu]

Hello,

Sorry for the late feedback.

From my point of view, I have identified three main issues:

1. More than one map suggestion can be attached to the same segment. After reviewing and accepting the first one, the second (and any subsequent) map suggestions disappear because the segment ID changes. In such cases, I have to manually complete the remaining wide-scope edits.

2. Less experienced editors often propose multiple types of edits within a single map suggestion. Some of these changes are correct, while others are incorrect. This is another situation where I have to manually adjust or fix the edits.

3. Even experienced editors (L2, L3) frequently submit map suggestions. While they usually fill in most segment properties, they often forget important details (for example, not setting the segment direction, which then remains set to “none” by default). This significantly lowers the quality of their edits and again requires manual correction on my part.

Very often, I do not have time to ask the editor to complete their work, because the corrections would only be made after map compilation. Since map suggestions are available, many editors do not request a level downgrade to apply fixes themselves.

As a result, I usually reject such edits with the comment: “Please request a level downgrade on Discord.”

Best regards,
Darek

[MadanKPradhan]

@Wcrhu

More than one map suggestion can be attached to the same segment. After reviewing and accepting the first one, the second (and any subsequent) map suggestions disappear because the segment ID changes. In such cases, I have to manually complete the remaining wide-scope edits.

Are you referring to this issue?

Older Suggestion Void & Overlapping Saving Error

Is this a…: Standard bug Steps to reproduce this issue: Steps: Suggest road alignment edit Add new road in the same segment previous suggestion were reported. Environment where the bug occurs…: ROW Permalink: https://waze.com/en-GB/editor?env=row&lat=26.45563&lon=87.26071&zoomLevel=20 Browser name and version: Google Chrome Version 142.0.7444.60 Are you using scripts? Please detail which ones.: No Case 1: Older Suggestion Void Case 2: Overlapping Saving Error

[Nataliia_Staff]

@MatthiasGor

Maybe it’s worth considering a mechanism that will allow our to accept or reject individual suggestions?

At the same time, consider the possibility of moderation, along with the possibility of blocking edits by L5 and L6.

Hi @MatthiasGor,

Thank you for sharing this idea. I will add it to the feature request for the team.

Regards,
Nataliia

[Nataliia_Staff]

@Wcrhu

From my point of view, I have identified three main issues:

1. More than one map suggestion can be attached to the same segment. After reviewing and accepting the first one, the second (and any subsequent) map suggestions disappear because the segment ID changes. In such cases, I have to manually complete the remaining wide-scope edits.
2. Less experienced editors often propose multiple types of edits within a single map suggestion. Some of these changes are correct, while others are incorrect. This is another situation where I have to manually adjust or fix the edits.
3. Even experienced editors (L2, L3) frequently submit map suggestions. While they usually fill in most segment properties, they often forget important details (for example, not setting the segment direction, which then remains set to “none” by default). This significantly lowers the quality of their edits and again requires manual correction on my part.

Very often, I do not have time to ask the editor to complete their work, because the corrections would only be made after map compilation. Since map suggestions are available, many editors do not request a level downgrade to apply fixes themselves.

As a result, I usually reject such edits with the comment: “Please request a level downgrade on Discord.”

Hi @Wcrhu,

Thank you for sharing your point of view and providing detailed feedback. I will make sure to pass it on to the team.

Regards,
Nataliia

[Wcrhu]

@MadanKPradhan

Are you referring to this issue?

Exectly!

I experience the same thing.

[Nataliia_Staff]

@EsdrasFarao

I made a video reproducing the error. When I open Street View, the image loads from the last location I visited. I have to drag the pin again to get the map to show the correct image for the current location.

Hi @EsdrasFarao,

Thank you for providing those details and the video recording.

My apologies for missing your previous message. I have added your case to the internal ticket and asked the team to investigate it.

Regards,
Nataliia

[GabiruX]

SV bug still here. Just work normaly when I press the update button.

[Nataliia_Staff]

@GabiruX

SV bug still here. Just work normaly when I press the update button.

Hi @GabiruX,

Does the issue happen only for locations that you check using the ‘See in Street View’ button?

Thank you,
Nataliia

[tbrks]

Unfortunately it still happens when dragging the street view pin onto the map. The only difference after this new version is it only puts the street view panel itself in the old location and thankfully does not pan the WME map anymore.

[turbomkt]

@Nataliia_Staff

Does the issue happen only for locations that you check using the ‘See in Street View’ button?

The See in Street View button also has this issue.

[locojd1]

Thank you @Nataliia_Staff for the support with the SUG really appreciate it.
Also just wanted to ask if there is any update about the issue with the PIN in WME, where you search for a city or different location you will get the PIN showing the location and before as soon as you move the Map it used to disappear, but now it just stays on the Map and it doesn’t dissapears unless you reload the page. which is a unwanted behaviour and this is been happening for quite a while in production and in this new release too.
Also the issue with the street view jumping from location, still occurring not all the time but still happening as mentioned above.
thank you for your help

[temp2123454333]

hi, it seems my suggestion was approved, but i have still not recieved any email or in-app notification alerting me? the edit history shows 24 January, 2026, but it is currently 00:08 on 25/01/2026? https://waze.com/en-GB/editor?env=row&lat=53.46654&lon=-2.13592&zoomLevel=17&segments=123322541

edit: it seems I have received the notification but after 8 hours.

[Nataliia_Staff]

@locojd1

Also just wanted to ask if there is any update about the issue with the PIN in WME, where you search for a city or different location you will get the PIN showing the location and before as soon as you move the Map it used to disappear, but now it just stays on the Map and it doesn’t dissapears unless you reload the page. which is a unwanted behaviour and this is been happening for quite a while in production and in this new release too.

Hi @locojd1,

Thank you for highlighting these issues. I will ping the team for an update.

Sorry for the inconvenience and thank you for your patience.

Regards,
Nataliia