New Editor version 2.229

[Nataliia_Staff]

EDIT: Our apologies for releasing this version during Memorial Day- we messed up and we are very sorry. This has been noted for future releases.

Hi Everyone

We hope you’re all doing well.

We’ve just released a new version of WME prod, v2.229.

Below you can find a summary of the release.

Known issue:

• Venues - Layers: Venues loaded for PURs stay displayed on map
  New features/enhancements:

1. Major update to Map Problems: We have just released a major update to feed closure map problems handling in WME. This version includes adding more detailed information to map problems and an ability to convert a map problem into a closure. See more details in the release notes document.
2. Attributing closures to partners: We’re happy to announce a small but important change to WME: Starting today when adding a closure provided by a partner, you will be able to indicate that the information came from a partner. Additionally, any closure created from partner data will clearly display its provider in WME, making it easier to troubleshoot and escalate issues.
3. Suggest an Edit: with this version, we’ve added the ability to display approved suggestions on the map and allow filtering for segments.
   4. Suggest an Edit: added an explanatory icon to indicate when a suggestion is loading
4. Suggest an Edit: added a tooltip that informs the editor that they cannot resolve suggestions if there are unsaved suggestions.
5. Permanent Hazards: we removed pedestrian crossing from the WME menu.

Performance improvements:

• We are introducing some improvements for further zoom levels: we fixed some issues with clearing unused objects.
• This should improve zoom/pan operations around zoom 17 and below since we will load less objects.
• We also added more events for better analysis of performance to be able to detect such issues.

Bug fixes:

We’ve released 11 bug fixes.

1. Closures: Finished closures aren’t appearing again after zooming in - fixed.
2. Real time closures on turns: Node should be clickable even with the turn closure icon - fixed.
3. Footer: The Live map link has no spacing between it and the edge of the screen - fixed.
4. Footer: The imagery credit has html tags that appear as text - fixed
5. PUR - Missing CSS for Location (Geometry) / Stop Point - fixed.
6. Koi Fish bug when moving node - fixed.
7. Permissions error when splitting segment linked to Roundabout / Intersection with junction box - fixed.
8. Lanes width: Apply button should be disabled after applying and becomes active with any new change -fixed.
9. Permanent Hazard: PH’s directions are affected by Path’s direction and closures - fixed.
10. Closures: Closed node from Finished closure is showing for segment even if Active closure has open node - fixed.
11. Map traffic events: Failed to load closures under the event - fixed.

You can read more here.

[doc]https://docs.google.com/document/d/e/2PACX-1vTUib3RZRHDxp-ZfUZn0N63dYDZ70R5DtuC1MUaZsDaM4eovcWgCYgiT-mi4I4nKGNG1WBZL3F2-wTw/pub[/doc]

We look forward to hearing your feedback!

Thank you,
Nataliia

[Fkzy]

What is the meaning of “brief” in “brief new version”?

[Nataliia_Staff]

Hi Fkzy,

This was just a typo on my part. I’ve corrected the sentence.

Thank you for noticing that!

Regards,
Nataliia

[J0kerNL]

Hi,

On the editors profile there is still something wrong with a string

https://prnt.sc/kDoxcvCtDb3w

Your sincerely,

[temp2123454333]

for some reason this ‘ur’ i reported yesterday showed the device as “carplay” but i reported this through the app hence the comment in the ur, which is not possible in-car? (i was using carplay just a few mins before i parked up, but i closed the app manually (already a known bug) then re-opened it, to report this ‘ur’)

ur permalink: https://waze.com/en-GB/editor?env=row&lat=53.47021&lon=-2.32938&zoomLevel=18&mapUpdateRequest=22367105

[kamonu]

Hi Nataliia,

Thanks for the attention to performance issues. Hard to say if it is today better than before.

Working mostly on zoom level 18 I encounter:

• now and then the drawing of a new segment stops without double clicking.
• drunken cursor: sometimes it is hard to draw the segment lines as intended: the cursor moves more or less related to the mouse movement.
• it is still commendable to restart Chrome completely after some minutes of mapping new segments and places to stop the delayed response to mouse movements and clicks.

Best regards,
Dirk

[temp2123454333]

at zoom level 22, the map disappears?

[temp2123454333]

the left bracket ‘[’ looks different to the right side?

permalink: https://waze.com/en-GB/editor?env=row&lat=53.58074&lon=-2.04946&marker=true&zoomLevel=19&segments=334350401,334350402(unavailable attachment: Screenshot (3981).png)
(unavailable attachment: Screenshot (3980).png)

[jm6087]

@Temp2123454333

at zoom level 22, the map disappears?

I am not seeing this issue.

[jangliss]

Not sure I noticed it in beta (or maybe an earlier version?), but “Map Comments” from the side menu got renamed to “Map Notes”, but the top button to actually put comments on the map is still called “Comments”.

[Nataliia_Staff]

@J0kerNL

Hi,

On the editors profile there is still something wrong with a string

https://prnt.sc/kDoxcvCtDb3w

Your sincerely,

Hi J0kerNL,

Unfortunately this issue still remains. I will ping the team.

Regards,
Nataliia

[Nataliia_Staff]

@Temp2123454333

for some reason this ‘ur’ i reported yesterday showed the device as “carplay” but i reported this through the app hence the comment in the ur, which is not possible in-car? (i was using carplay just a few mins before i parked up, but i closed the app manually (already a known bug) then re-opened it, to report this ‘ur’)

ur permalink: https://waze.com/en-GB/editor?env=row&lat=53.47021&lon=-2.32938&zoomLevel=18&mapUpdateRequest=22367105

Hi Temp2123454333,

Thank you for the report. The likely reason is that the information about your device was taken from your last navigation session, which was using CarPlay. Let’s keep an eye on this issue and recheck when you have a chance.

Regards,
Nataliia

[Fkzy]

@Temp2123454333

the left bracket ‘[’ looks different to the right side?

permalink: https://waze.com/en-GB/editor?env=row&lat=53.58074&lon=-2.04946&marker=true&zoomLevel=19&segments=334350401,334350402Screenshot (3981).png
Screenshot (3980).png

I believe it is caused by something on your computer.

[Nataliia_Staff]

@kamonu

Hi Nataliia,

Thanks for the attention to performance issues. Hard to say if it is today better than before.

Working mostly on zoom level 18 I encounter:

• now and then the drawing of a new segment stops without double clicking.
• drunken cursor: sometimes it is hard to draw the segment lines as intended: the cursor moves more or less related to the mouse movement.
• it is still commendable to restart Chrome completely after some minutes of mapping new segments and places to stop the delayed response to mouse movements and clicks.

Best regards,
Dirk

Hi Dirk / kamonu,

Thank you for these observations. Could you please record a video next time you encounter performance issues? Please remember to disable all scripts beforehand.

Regards,
Nataliia

[Nataliia_Staff]

@Temp2123454333

the left bracket ‘[’ looks different to the right side?

permalink: https://waze.com/en-GB/editor?env=row&lat=53.58074&lon=-2.04946&marker=true&zoomLevel=19&segments=334350401,334350402Screenshot (3981).png
Screenshot (3980).png

Hi Temp2123454333,

Could you please recheck this case with all scripts disabled?

Thank you in advance!
Nataliia

[Nataliia_Staff]

@Temp2123454333

at zoom level 22, the map disappears?

Hi Temp2123454333,

Could you please elaborate on what you mean in this case? Are you unable to see segments and places?

Thank you in advance!
Nataliia

[jonv-uk]

@jangliss

Not sure I noticed it in beta (or maybe an earlier version?), but “Map Comments” from the side menu got renamed to “Map Notes”, but the top button to actually put comments on the map is still called “Comments”.2024-05-27_21-03-04_chrome_hWMrCJAbTy.jpg

It’s part of the changes to Unify Action Areas

[kamonu]

@Nataliia_Staff

@kamonu

Hi Nataliia,

Thanks for the attention to performance issues. Hard to say if it is today better than before.

Working mostly on zoom level 18 I encounter:

• now and then the drawing of a new segment stops without double clicking.
• drunken cursor: sometimes it is hard to draw the segment lines as intended: the cursor moves more or less related to the mouse movement.
• it is still commendable to restart Chrome completely after some minutes of mapping new segments and places to stop the delayed response to mouse movements and clicks.

Best regards,
Dirk

Hi Dirk / kamonu,

Thank you for these observations. Could you please record a video next time you encounter performance issues? Please remember to disable all scripts beforehand.

Regards,
Nataliia

Hi Nataliia,

See https://youtu.be/BA4aX23ipmg.

A short video recorded during mapping of a segment. An example where the drawing of a new segment stops without double clicking.

Regards,
Dirk

[mudge42]

After a closure is attributed to a partner and saved, it is no longer possible to edit the partner. Is this intended? (Editors are not infallible :))
Thanks.

[kamonu]

Hi Nataliia,

Still now and then the bug “There is a problem with the highlighted segment and node.”

See video https://youtu.be/-0ih_5KWxfc

Location: https://waze.com/editor?env=row&lat=23.53874&lon=104.67837&zoomLevel=17

Best regards,
Dirk