Some of them aren’t yet available on Transifex for us, editors of the localization teams, to localize them 
This is something that should be taken care of before going into production, but the fact is that some strings (mainly from new features) aren’t added to Transifex before going to production. This is something that needs to be care in advance while in beta … and for that, Waze Staff (also) needs to do their work 
I’ll have to check that out. I do use Bitdefender and I believe the anti-tracker add-on was installed (don’t remember if it was enabled or not though).
When a WME bug or feature request is shared on uservoice, how do the developers decide if/when to patch the bug or implement the new feature? Does the uservoice post have to meet a certain vote count?
Feature requests do have to receive a certain amount of votes (qty unknown) to be considered.
In previous WME production releases, you could begin typing a street/city name in any case and the results would auto-populate. The current WME production release requires the street or city name to be entered case-sensitive for the results to auto-populate. This slows down the workflow for editing segments and places. See the following (or click here) for a screen capture of the behavior:
Uservoice post: https://waze.uservoice.com/forums/59225-map-editor-suggestions/suggestions/46045591-revert-requiring-street-city-name-to-be-case-sensi
