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?
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.
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.
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.
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.
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…