Okay, I can make this happen completely predictably, now. It's a slightly different error, but I'll bet money the two are related -- and the result (segments don't load) is exactly the same.AlanOfTheBerg wrote: For some reason, the browser data seems to be getting corrupted and it can't figure out where the view on the map is located? Weird.
Go to this Permalink:
https://www.waze.com/editor/?zoom=10&la ... FFTFTTTTFT
Now. Zoom out one click at a time, not moving where you're centered. When you get to the second to last out, you will get:
Code: Select all
Uncaught TypeError: Cannot read property 'countryID' of undefined
Waze.Control.Chat.OpenLayers.Class.getTopCity WME.min.js:1
Waze.Control.Chat.OpenLayers.Class.onMergeEnd WME.min.js:1
OpenLayers.Events.OpenLayers.Class.triggerEvent OL.min.js:1
Waze.DataModel.OpenLayers.Class.mergeObjects WME.min.js:1
Waze.Controller.OpenLayers.Class.onFeatureRead WME.min.js:1
Waze.Protocol.OpenLayers.Class.handleRead WME.min.js:1
(anonymous function) OL.min.js:1
(anonymous function) OL.min.js:1
OpenLayers.Request.runCallbacks OL.min.js:1
f.onreadystatechange OL.min.js:1
c.dispatchEvent OL.min.js:1
b OL.min.js:1
_object.onreadystatechange
It's like a bounds problem. When it gets far enough out that there are two countries in view, and it can't decide which is the right one, it doesn't 'pick one of the two', say; it just barfs out.
Although I can't prove it yet, I'd lay money on that the same kind of 'undefined' error happens near state borders, and near city borders, at respectively lower zooms. If I find an example, I'll follow up with it.
Re: Map Editor major ver (Nov 5, 2012) Official Feedback