Browser: Chrome 27.0.1453.15 beta-m
OS: Windows XP SP 3
Hmm. I didn’t even realize I was in the beta channel for Chrome! (It’s not my primary browser, Opera is.)
I’ve had no trouble with Noscript (or the Chrome equivalent) when running Highlights. There were no extra exceptions that had to be made for it to operate correctly. Addons, on the other hand, needs to have googleapis.com allowed in order to work.
Tim: before someone jumps in and suggests it be removed, I would like to see the u-turn highlighting remain in the script.
Most segments shouldn’t have it enabled, and it seems to really mess up the routing system when it is… so being able to spot that easily and quickly (the shift-Z trick doesn’t display u-turns that are enabled or disabled) is a good thing. Perhaps softening the language in the left-hand bar about fixing it would be good, but I think it still needs to be identified.
+1 to doctorkb ^
I don’t scan the streets with the script as a general rule, but it’s nice that it alerts me to potential problems I wouldn’t otherwise notice.
Is Chrome beta working for you? I also have Chrome beta (and Ghostery) and scripts have recently stopped working.
Did you update your scripts to the latest versions? There’s a new WME as of earlier this week which broke some of the scripts, but the authors have released updates.
Works just fine. I only use Chrome for a few sites (Waze, Facebook, Foursquare editing and Google Street View) since those are crap on Opera. I don’t use Ghostery on Chrome, but I do use some other extensions like a translator and WME Add-Ons and they work OK.
Is there a source for older versions of these scripts? I would like to go back to 1.6.0 and see if it works. That was the last known working version for me, I think.
If you dig around my script pages on Userscripts.org you should be able to download an older version to try.
Could be coincidence that something in Chrome changed at the same time… Anyone else using Chrome beta, either with problems or without?
via mobile
I believe that is an incorrectly named road. looking at the screenie it says “St Andrew St” That will come out in TTS as “Street Andrew Street”. think it needs a “.” after the first ST. and the dash will go away.
Is it possible to have these in one place or name them with their version numbers built into the name? for those who prefer to use the older version for what ever the reason.
You can get them all at http://userscripts.org/scripts/versions/141050 - but they’re not named with the version number in that list.
You know, actually I’ve seen it before. it all comes together. Thanks 
orbitc was kind enough to send me a few of the old files he had — 1.6 and 1.5 — and they don’t work, either. Just like 1.6.2 the checkboxes don’t do anything and the drop down boxes for Filter by City and Highlight a Road Type are empty.
I’m not overly familiar with scripts and Chrome but if you guys know of something I can check, maybe we can figure something out. Otherwise, I’m going back to a stable release to try again.
Works very well for me.
The only missing feature is highlighting of junctions: highlight when all turns are disallowed or when all turns are not allowed.
FYI moving from Chrome Beta to Chrome brought me back functionality of Colour Highlights and JNF but not URL Overview. Still delving.
I’m going to go back to the main release channel, too, then. I just hope whatever’s causing the scripts not to work is fixed on Chrome’s end by the time this beta is released to everyone, or we’ll all be back at square one.
Edit: Went back to main release, which for some reason has an even higher number: 27.0.1453.47 m. Scripts still not working. Time to do a complete uninstall/reinstall I think.
Edit #3: After a complete uninstall and re-install, everything is working now. How strange.
Maybe the color of u-turn highlight should be changed from red to something else like blue or green, because red means error for most of us, and u-turn are not always errors now that we are able to control them in the editor.
Yes, I am considering doing exactly this. 
I’m pretty sure this has something to do with the bootstrapping functions that most of the Javascript scripts are using to initalize. My rationale for this is that I’ve done a side by side comparison of running highlights-1.6.3 in Chrome prod and beta, and what I find is that it shows the sources of the two as fundamentally different in the sources tab.
Prod:
(function (unsafeWindow) {
---The entire contents of the highlighter script here---
})(window);Beta:
---The entire contents of the highlighter script here---I think Chrome Beta and Canary somehow does not like the bootstrapper function, as written currently. I can also note that after loading WME (in a state where highlights-1.6.3 is not in the extensions tab at all), I can paste the entire contents of the script into the console, and it suddenly works fine – until I reload or otherwise leave the page.
Found some time to include a few fixes: Beta v1.6.3
- Nodes with U-turns on them are highlighted cyan (not red)
- Fixed highlighting of Landmarks by city to honour invert option
- Support for new variable lock rank, with darker shades for higher ranks (Beta editor only)
I’m quite tempted to remove the U-turn highlights altogether as a) the editor shows it directly and b) I’m still not convinced selfcons cause routing problems (if all other roads are correct).