Context Navigation

Changes between Version 1 and Version 2 of Ticket #19136, comment 44

v1	v2
11	11	> Still, I think there should be a test in `combinations.mapcss`.
12	12	Personally, I think, using `highway` as area is a incorrect mapping and `area:highway` should be used but, sadly, that train departed a while ago.
13		JOSM allows only `service` and `pedestrian` as multipolygon. `footway` and `path` might be ok, as otherwise, people will use `pedestrian` which is wrong in many cases. Still, I do not like it at all and it reminds me about the mess, we have with `landuse` even though `landcover was proposed and used years in advance but was never supported by many applications including JOSM.
	13	JOSM allows only `service` and `pedestrian` as multipolygon. `footway` and `path` might be ok, as otherwise, people will use `pedestrian` which is wrong in many cases. Still, I do not like it at all and it reminds me about the mess, we have with `landuse` even though `landcover` was proposed and used years in advance but was never supported by many applications including JOSM.
14	14	Often this is mapping for the renderer as `width` nor `area:highway` are used or correctly rendered. Speaking about `pedestrian`, this even hides a lot of other features as it is rendered on top of them without transparency.
15	15	Routing is another problem and including a multipolygon in a route relation does not work at all.