You MUST read the "[Guidelines] How to request and search for new features" before posting here.

If you think you've found a BUG, use the appropriate WME version release thread found in the Waze Map Editor forum (parent of this forum).

Post Reply
Forum rules
You MUST read the "[Guidelines] How to request and search for new features" before posting here.

If you think you've found a BUG, use the appropriate "Official Feedback" thread found in the Waze Map Editor forum (parent of this forum).

Problem selecting horizontal segments

Post by Chris_CA
Many times, I cannot select segments that are horizontal (east/west) or near horizontal (say, less than 20 degrees or so).
Refresh/save/zoom in or out/move the map around does not usually make a difference.
Turned off all extensions. Same.
This happens using both FireFox & Safari on Mac OS and has been happening for + 6 months so it's not just the latest editor. Does seem a bit more prevalent as of last month or so.

If I grab an intersection or end node, drag it up or down, then I can select the segment, make changes then move the intersection/end node back to where it was.
Any one seeing something similar opr know of a fix?
Chris_CA
Area Manager
Area Manager
Posts: 128
Has thanked: 3 times
Been thanked: 24 times

POSTER_ID:10960558

1

Send a message

Post by AlanOfTheBerg
Haven't seen this on any browser but FF. But I mostly use Chrome on both Mac/Win for WME.
AlanOfTheBerg
EmeritusChamps
EmeritusChamps
Posts: 23627
Has thanked: 568 times
Been thanked: 3479 times
Send a message
Wiki Resources: Map Editing Manual | alanoftheberg@gmail.com
Oregon-based US Ex-Global Champ Editor | iPhone13Pro - VZ

Post by AlanOfTheBerg
dbraughlr wrote:If this is a bug with Firefox, I would like to report it. But I need to be able to define exactly what is wrong.
I've wondered if this could be the case, too. The code is loading vector objects and I would think, logically, that the browser would be responsible for determining when an object is being hovered over or clicked on.
AlanOfTheBerg
EmeritusChamps
EmeritusChamps
Posts: 23627
Has thanked: 568 times
Been thanked: 3479 times
Send a message
Wiki Resources: Map Editing Manual | alanoftheberg@gmail.com
Oregon-based US Ex-Global Champ Editor | iPhone13Pro - VZ

Post by alexs001
I gave up on editing in Firefox for this very reason. Safari doesn't seem to have this problem.
alexs001
Waze Global Champs
Waze Global Champs
Posts: 1742
Answers: 9
Has thanked: 197 times
Been thanked: 505 times
Send a message
Local Champ: Canada
Area Manager: Okanagan Valley, BC / Newfoundland and Labrador

https://s.waze.tools/c6.png https://s.waze.tools/s0500.png

Post by Dan_Olsson
I only use FF (mostly because of it's powerful addons i.e. Adblock Plus etc).
I agree that the problem is somewhat annoying, but can be easier to handle by clicking as near to a node as possible. Just a tip...
Dan_Olsson
Area Manager
Area Manager
Posts: 65
Has thanked: 9 times
Been thanked: 3 times
Send a message
AM Helsingborg/Landskrona etc (in Sweden)

Post by dbraughlr
I am surprised that there aren't more editors who use Firefox. It seems that the bug could be fixed just for us quite easily by making the selectable area thicker for horizontal segments.

I would be willing to hold my control key to decrease selection sensitivity. A fine workaround would be to allow me to adjust somewhat which way is north.

Perhaps a Greasemonkey script could be made to show a handle on each horizontal segment to act as a selection target. Such could be useful to editors using other browsers in other scenarios like multi-select with very short segments.

If this is a bug with Firefox, I would like to report it. But I need to be able to define exactly what is wrong.
dbraughlr
Posts: 569
Has thanked: 164 times
Been thanked: 98 times
Send a message
Ѭ

Post by dbraughlr
AlanOfTheBerg wrote:The code is loading vector objects
If someone could describe the exact technical description or point me to the code, I would compose an error report.

What weighs against this being a Firefox bug is that zooming out (Shift ↑) on the map view solves the "bug" if the road is "primary street" or higher which suggests that the problem is the line-height (thickness) in pixels. WME makes some things just too small.

Zooming in the browser view (Ctrl + or Alt-vzi) does not get around the problem with the line being too thin to select - which also points to the bug being with the line-height set by WME.
dbraughlr
Posts: 569
Has thanked: 164 times
Been thanked: 98 times
Send a message

Post by Riamus
I see this often in FF, but can usually get around it by zooming in or out a little. It can be annoying when it just refuses to let me select it, but I have always managed to do so without having to move any nodes or do anything to the road. As a note, I've found that selecting multiple segments at once can make it easier to select a segment that isn't letting you select it. Then just deselect the segment(s) you don't need.
Riamus
Posts: 1051
Has thanked: 61 times
Been thanked: 200 times
Send a message
https://www.waze.com/wiki/images/5/5a/W ... M_only.png
Previously Area Manager: Michigan - Northern LP.
Waze running on Samsung Galaxy S21+.

Post by Twister-UK
This appears to have been a known Firefox issue for some time now... https://bugzilla.mozilla.org/show_bug.cgi?id=676001
Twister-UK
Waze Local Champs
Waze Local Champs
Posts: 4695
Answers: 2
Has thanked: 743 times
Been thanked: 4735 times
Send a message
Chris (not to be confused with Chris or Chris, or even Tim, Stu, or any of the other champs team...)
AM SE England & Shetland Islands, UK Local Champ, WME Beta Tester & ScriptMangler
WME/Livemap enhancement scripts @ GreasyFork


https://chizzum.com/greasemonkey/images/beta.pnghttps://chizzum.com/greasemonkey/images/s0400.pnghttps://chizzum.com/greasemonkey/images/c5s.png