Sometimes the wrong feature gets selected

[tyrasd]

Sometimes when clicking on, say the area of a building, iD selects a (large) background landuse polygon instead. To select the actual building one has to click on its outline. The building does show the hover-highlight only when hovering over its outline, not its inside. This happens not with all buildings inside the same landuse polygon, but can happen with both multipolygons and regular closed ways. After some panning around this bug usually disappears, but may reappear somewhere else.

To reproduce, take a look at this example location and try to select the multipolygon building in the centre or the building directly North of that.
http://openstreetmap.us/iD/release/#background=Bing&map=19.00/11.24400/46.41283

Tested in FF20 and Chrome23.

Could this be related to #1676?

[jfirebaugh]

Regressed in 1db9958.

[jfirebaugh]

This is difficult to fix. 1db9958 was an important optimization, but somehow all the SVG paths still need to be inserted in order of descending area.

[Stalfur]

Encountered same, seems harder to edit in current version than before (for those of us with powerful desktops)

[tyrasd]

Here is an example of a newby mistake very likely triggered by this bug: The user obviously wanted to select a building to mark it as a restaurant. Instead, he ended up selecting the background landuse multipolygon. And now we have an awkward kilometre long building. :(

[tyrasd]

This issue could at least be attenuated by implementing #1702 solving #542.

[jfirebaugh]

Yeah, I agree that error was probably caused by this bug -- we'll find some way to fix it.

Not sure that something like #1702 would help in this case. The area in question falls on the border of the landuse polygon so it would probably be visible.

[lsces]

Working in areas where a large number of areas overlap one another, there is a definite disadvantage to picking up an area information when there are several stacked areas. Droping back to only showing the information when hovering over the actual boundary would make things a lot more usable. Firebug goes beserk tracking things that are changing and often sits toggling between two areas even without the mouse moving.

[tyrasd]

Are there any plans of making a new release that includes this fix? It's been over a month now, and this bug seems to be really annoying out in the wild.

[jfirebaugh]

Yes, I'm planning to do a 1.2 release today.