It would appear that Waze has decided that U-Turns and dead-end U-Turns are not going to be editable any more. Personally, I think that’s a bad idea at intersections, since how can you indicate where a U-Turn is actually legal to perform for the routing engine? But that’s another topic.
Since that seems to now be the case, is there any chance that Validator can be updated to no longer highlight roads with “Unconfirmed turn at node {A|B}” when node {A|B} is a dead end?
I also had not see this script before you asked about it. I have now added it to the Wiki on the tool page.
I just tested this. You can still make it a hard no u-turn by clicking on the end node and typing “q”. This works while running JNF and without JNF installed. (I just tested both cases.) So you just need a keyboard to edit them.
Krikket
Huh. Well, I just tried doing the “q” thing when clicking on the end node, and I do have JNF installed - and it didn’t do anything… :?:
I don’t know. I’m running a non-standard system (Mageia Linux, Chrome (not native to Mageia), plus the plug-ins.) Try it after telling Chrome to disable the extension and reload the page? Maybe instead of a q-w for a junction, use a w-q?
Just random thoughts… [Edited to add the comment that if something doesn’t work, you can always undo it!]
Krikket
I did finally get q-w combo to work, so there’s that, at least.
Of course, if Waze truly doesn’t want us changing those anymore, I still think it would be a good idea for Validator to no longer flag those dead-ends with “unconfirmed turns.” But that’s just my opinion, 
And I just ran into an area where after I Q a junction, it get a save error. Noting I can do will let me Q or QW the junction in the last 30 minutes, but it was working fine up until that point.
This is the location if anyone else wants to try it on their system.
It appears to be very rare now, but specific to certain points. I guess we should move this particular line to a separate thread since I doubt it is Validator specific.
Don’t forget that WME Toolbox incorporates much of JNF, including the Q functionality, so test this with Toolbx and JNF both off. It will probably work anyway BUT with the side effect of making all junction traversals illegal (all red arrows).
I went straight with “V” unmodified
Does the keystroke automatically update? Mine had stayed at Shift-W (interfering with Waze’s new Shift-W for closing SV) until I manually changed it. I checked, and I did have 1.0.2.
Is it possiable to identify the geometric nodes (not the end points, but the ones in the middle) that are at 180 degrees? Would be good candidates for cleaning up.
For what it’s worth, I keep Toolbox turned off almost always because I’ve found (and had it confirmed on the forums) that it interacts badly with URO+ after a bit of time. If I need it for a specific function, I’ll turn it on, and then shut it off again.
So the use of exensions may also play a part…
Krikket
I will like to see the type of road connected to the A junction?
Is there an variable that expands the type of conected segment?
Is there a way to add non-approved speed and RL cameras (or even all cameras) to the custom search feature?
Is this still an issue for you or anyone else? Also, could you include the link to the thread that has this convo so I could look it over and see if I have had any issues like this?
Hmm. It is possible to search just for segments updated by User? I tried an option for CM, and it only searches for segments updated by User but with problems in them. How about any segments?
Few answers:
Thanks, will be fixed.
Validator does not save keyboard shortcuts, so I guess it’s another script saved that.
Thanks, added to my todo list.
There is no such a variable and it would be slow to implement and tricky to match. It’s better to implement such checks inside the Validator using Javascript, not just regular expressions.
Sorry, at the moment Validator analyze just road segments.
You can use a custom check to highlight all segments and then search for a specific username, i.e.
Template: 1
RegExp: /1/
It appears the latest update to beta has broken Validator 
When u zoom in, you see everything as shown in the image and validator throws the message that there are “too many issues reported”.
This behavior is not present in the normal version.
Same here
Shmupi
Same all…