Still here: “Suppress unneeded junctions on screen [Available for Area Managers, Country Managers and level 5 editors]”
Are you an AM?
Unlike IE, Safari is standards-compliant and uses the same WebKit rendering engine as Chrome. Also unlike IE, WME works in Safari.
Safari is faster (in my perception) and far more resource-efficient (in fact) than Chrome on OS X. I use Safari for everything but Waze. Chrome is a battery hog; I could browse for 12 hours unplugged on Safari if I wanted to, even with a number of tabs open.
I used to edit in Safari back in the days of WazeBar, but that’s gone now. I’ve built Chrome into a little Waze ecosystem — my entire bookmarks bar is filled with Waze stuff, for example — so I won’t personally be going back to Safari for editing either way, but it’s perfectly reasonable for an editor to wish to use Safari.
I also reported Riga Airport center pin to google (as it caused totally wrong routing in waze)… but they replied that this is some border landmark and IS NOT GOING to be modified (are they crazy?), so I just have drawn a road in waze from correct entrance place to the approximate center point of googls airport landmark. Now people at least are routed to the correct entrance place.
FWIW, I just tried that as a test in my Waze app. I got as far as typing “Reno ai” and the very top selection it offered me was “Reno-Tahoe International Airport.” “Reno Airport” was the second item on that list. 
When I tap on the first item, it shows me a map where the marker is in the middle of the airport (which is how people are getting routed to the back side, since a road back there is closer to that marker). I know it well - it’s the GM marker for the item.
When I tap the second item on that list, I do get a pin at least on the PLR leading up to the terminal, so that one would get them close enough that they could find their way to the terminal. It must be an additional pin simply called “Reno Airport” that’s also on GM, because none of the place pins at the terminal in Waze say that (they all have the full name of the airport). And given the number of URs I’ve had to deal with on this subject, I’m going to guess that 99+% of average everyday drivers who use a nav app will select the first item on the list.
NONE of the Waze markers were on the list at that point.
Now, before you go on about “don’t use the auto-suggestions that show up as you type,” bear in mind that I’m talking about the experience for the average, everyday driver. NOBODY among average everyday drivers who is using a nav app is going to keep typing once what they want to see is on a list being presented to them as they type. It’s just not human nature.
From their standpoint and the way this impacts them, Waze is in fact not preferring its own data - it’s picking from GM data first.
So if the fine folks at Waze make it harder for a Waze editor to submit changes to Google Maps via GMM by not giving you a list that says that a GMM button, you’re going to get a certain number of editors such as myself who simply won’t bother even trying to go through the ordeal that is changing a place or address location in GMM - and thus the problem will persist.
Now in this particular case, we’re pretty much stuck anyway since Google has airports like that locked down and you can’t even move the pin and try to make an argument for moving it. So until Waze truly prefers its own data over Google’s, there will be some places which are going to continue to be a problem for drivers.
I’ve heard tell that it will prefer its own house numbers on a street over Google addresses - but only if a given house number location has been touched by an editor after a particular date (I don’t know what that date is). Which means that 99% of the map is still preferring Google addresses over Waze house numbers (if that’s incorrect and it’s using house numbers regardless of when they were last touched by an editor, then please let me know).
So, no, I really just don’t see how Waze is preferring its own data in any practical sense of the word.
It’s not. Not yet.
But it will be in 3.9 if all goes as planned.
Well, here’s to hoping it goes according to plan and that 3.9 is released soon. 
Thanks for that info.
I would like to request adding Safari support back.
If you need any help I’ll be happy to provide it, I have a Safari developer account and some experience with extensions.
PM sent!
The Chrome extension is now updated on Chrome Webstore. Enjoy!
Very BIG thanks to all
Is it me or Draw landmark is not working ?
I am able to draw landmarks with WME and Select in landmarks (Toolbox) is working.
I doubt it’s you who’s not working… 
But yes, the draw roundabout landmark function seems to be broken. Bug confirmed, will be looked into.
Great job to all of you guys who helped making the latest version work.
All work great for me!
(except roundabout landmark function but that’s a minor detail ;))
If you click on the toolbox “feature list” on the left hand side it still lists all the old possible links even though you cannot add them.
Not a big deal, just a visual clean up for the next release.
Yup, thanks, will do.
Just uploaded version 1.4.6.1 to Chrome Webstore, with following update:
1.4.6.1
Fix: Draw roundabout landmark
Firefox extension will follow very soon. Safari users need to be a bit patient, we’re giving our best to get their extension updated, but this will take some more time.
A question about the
message.
I’m being told that there is no evidence that non-consecutive roundabout id’s do cause problems. Perhaps this test should be removed?
FF 1.4.6.1 posted – trigger an update in your Extensions pane to automatically update to the latest.
There’s inconclusive evidence for both sides. You don’t have to rebuild the roundabout (i.e., that’s up to you, the editor), but it may represent a problem.
Fantastic Doctorkb. Your contributions are sincerely appreciated across the entire Waze community.