fvwazing wrote:Read again, gettingthere. The poster Brshk is not the victim of some Auto-Capitalisation-routine. Some editor before him misspelled a cityname.

Timbones wrote:

CBenson wrote:Same here, it only happens on one of my computers. The computer that does it for me is running Vista, the Win 7 machine is fine.

That's it exactly: works fine for me on Win 7, but not on Vista (with Chrome).

For the last month I have been using a spare computer. My primary PC is dead, after letting the local authorized Lenovo service center replace a cracked plastic cover, so that I would not void the warranty by doing so myself. Now the hard drive is wiped out, and the computer will not power up at all. So when I get it back (or hopefully a new replacement) and reload everthing, the issue with Chrome may not exist.  I know... that is a lot of wishful thinking.

FreeMan12 wrote:

gettingthere wrote:There is no insight into who has modified turn restrictions. We have asked Waze to add this visibility (at least for the last modified turn for a junction) but they have not.

Having read this, I realize someone else could have made the changes, however I think it would be highly unlikely, unless someone's just trying to mess with me!

This segment (600 S, just west of Devaney) was just edited by me a few days ago. As I went through, I was checking everything for turn restrictions, 1-ways, etc, since I know there are none on these county roads (been driving this one nearly daily for 20 years, I'm pretty confident of this fact). Now, 4 days later, there's a turn restriction on westbound 600 South. I'm as confident as I can be that I would have removed that when I last looked at it on the 24th.

Something's not saving right, or there's an issue in the database. I'll leave the restriction set for a few days so someone can take a look at it, but then I'll fix it, since it's a route I use very regularly, and I don't really want waze trying to get around it.