jasonh300 wrote:When you hover over segments they turn blue, but if you don't click on them, they normally turn white again as you move the mouse away.
AlanOfTheBerg wrote:Mike-1323 wrote:jasonh300 wrote:It's also possible that this new behavior is unique Int'l editor then. We've had the new infrastructure in place for several months. iainhouse, are you also using Firefox, or something else?
It's not unique to the int'l editor. I've seen this behavior for a couple days on the NA server.
I've been trying to nail down whether it's a userscript or not, too. Or related to the landmarks layer issues. A permalink usually fixes things a while, but it comes back. Turn off extensions seemed to clear it up, but then after 30 minutes of having the same extensions enabled, I haven't had the issue again.
davipt wrote:(...)I think it's happening only on Firefox(...)
[18:52:28.697] TypeError: wazeModel.cities.get(cityID) is undefined @ https://world.waze.com/editor/:105
[18:52:34.415] TypeError: e is undefined @ https://world.waze.com/editor/js/WME.min.js?v=785:1
[18:52:34.420] Empty string passed to getElementById(). @ https://world.waze.com/editor/js/libs.min.js?v=785:2
[18:52:34.696] TypeError: wazeModel.cities.get(cityID) is undefined @ https://world.waze.com/editor/:105
skbun wrote:douglasr007 wrote:The only way to "fix" it is to deselect the road segment, zoom all of the out, and zoom all of the way back in to the section you're editing and hope the segment can be changed when you select it again.
Also, I thought it was a conflict with WME Color Highlights script but it's definitely the server causing these issues.
Try this, because it doesn't seem to help whether landmarks in view have names or even addresses: just turn your landmark layer off and work like that.
I'm betting it'll be fine, until they fix this on their end. It doesn't seem to help whether landmarks in view have names or even addresses, which means that's a red herring, so there's really nothing we can do.
zs2cli wrote:Maybe already mentioned in the numerous posts above, too many to read, but incase it's not, the new editor does not work in Firefox.
CrackedLCD wrote:First, when selecting small segments with geometry nodes in between the A-B points, I'm noticing a big tendency for the cursor to not change from the crosshairs back to a pointer. When this happens, if I click anywhere on the screen, it places the geometry node at that spot.
CrackedLCD wrote:Second, I'm having occasional trouble inputting data like street names onto segments. I'll start typing and then it's like someone hit the escape key, cancelling the operation
jasonh300 wrote:The thing with the geometry node sticking to the mouse pointer has been around for a while, but now, you can click multiple times and it still won't let go. It also seems to do it a lot more frequently under certain circumstances, and it does seem to have something to do with rapidly trying to select multiple segments. I found that hitting Escape will get rid of it sometimes, and sometimes it will do it on its own. This is an extremely frustrating bug.
daknife wrote:Often the only solution for such a loop is to delete it as one piece, save your changes and then redraw. It's one reason such loops are such a big pain is that once created in the system, you can't edit them, you can only delete them.