BoredFish wrote:I am having a similar but different problem that is possibly related. With the "editable areas" checked the entire map is dark. I unchecked all other layers except editable areas, disabled all scripts and plug-ins and it does show a thing grey line outlining my driving areas. When zoomed in and layers turned back on I can still edit in these areas but the entire map is darkened making the edges of my editing area nearly indistinguishable from the rest of the map.

****Update

The above problem was in Firefox, after switching to Chrome the problem disappeared. Also noted that Firefox is forcing the url waze.com/en-GB/editor/
Whereas Chrome is using waze.com/editor/
Even taking out the "en-GB/" it redirects back to it.

Nimbus- wrote:

afrenchpress wrote:

BoredFish wrote:I am having a similar but different problem that is possibly related. With the "editable areas" checked the entire map is dark. I unchecked all other layers except editable areas, disabled all scripts and plug-ins and it does show a thing grey line outlining my driving areas. When zoomed in and layers turned back on I can still edit in these areas but the entire map is darkened making the edges of my editing area nearly indistinguishable from the rest of the map.

****Update

The above problem was in Firefox, after switching to Chrome the problem disappeared. Also noted that Firefox is forcing the url waze.com/en-GB/editor/
Whereas Chrome is using waze.com/editor/
Even taking out the "en-GB/" it redirects back to it.

My issue is in Chrome. I discovered that if I turn the Places layer off, everything is good again. But that means that I can't add places or deal with URs that need Place help.

Similar issue for me as well in both Chrome and Firefox. It only happens in one of my editable areas, however.

taco909 wrote:Do the elevations match?
When a segment is first drawn, and frequently freshly edited, it will appear at elevation "nul"
I've encountered this bug and it's always been due to one of the segments being at elevation nul or different from the other (whether intentionally or in error).

Remember, the "bridge" function also increases elevation by 1, so bridging a segment may prevent the creation of an intersection with another using the tool.

ohad-ron wrote:@Alan - not sure I understand, and not sure this is what we intended.
Can you please provide a permalink to a segment I can 'select entire street' from and see?

ohad-ron wrote:@Alan - not sure I understand, and not sure this is what we intended.
Can you please provide a permalink to a segment I can 'select entire street' from and see?

top_gun_de wrote:After pressing F5, the changes are saved, but the current position in WME is gone.

taco909 wrote:

Machete808 wrote:Anyone hear any intel on a delay in NA tile updates? INT has been daily, NA not since 5/27. I'm usually not this impatient, but there's a particular issue at the moment ... so i wondered.

5/27 was also delayed... 5/24 was the last before that.
I had done some paving and completed the work in WME on Saturday but it didn't render until Thursday. Only two small segments of the paving actually showed in the app after the 5/24 update.