id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
24096	Child() is not working in match_expression of presets (although the documentation suggests that it should)	goodidea	team	"According to the JOSM documentation for tagging presets (https://josm.openstreetmap.de/wiki/TaggingPresets), any (valid) search expression should be able to be used for `match_expression`. At least that's how I understand the text in the documentation:
''
match_expression=""search expression""
additional criteria for matching primitives, specified in JOSM search syntax. (since r17662)''

However, `child()` does not seem to be supported in a `match_expression` (although it works fine in a search expression in JOSM!)

Examples:

* A preset for a node with `match_expression=""child highway=*""`(or `match_expression=""child (highway)""`) **never** matches in JOSM (or has a false result). No matter if the node is a connected with a highway way or not.
* A preset for a node with `match_expression=""-child highway=*""`(or `match_expression=""-child (highway)""`) on the other hand **always** matches (or has a true result).

(I tried all possible syntax notations…)

Is this a bug, a missing feature, or just a documentation flaw (something like only a subset of the expressions possible for search expressions can be used in `match_expression`)? If the latter is true, the documentation for `match_expression` should be made clearer and specify exactly which type of search expression can and cannot be used.

But my main question is: would it be possible to allow `child()`? for `match_expression` as well? That would be great and very helpful.

In the latest Vespucci version, for example, this is supported for presets and is used in [https://github.com/simonpoole/beautified-JOSM-preset Simon Poole's ""beautified-JOSM-preset""] (which is suitable for JOSM and Vespucci) for traffic_sign nodes (nodes connected to a highway should have a `direction=*` tag with `forward|backward`, whereas separate nodes should have a compass direction as a value for `direction=*` – for this you need 2 different presets to clearly distinguish this and offer corresponding values ​​for direction, e.g. in a combo).

Currently these presets work very well in Vespucci, but not in JOSM (see also this GitHub issue: https://github.com/simonpoole/beautified-JOSM-preset/issues/477)."	defect	new	normal		Core			preset match_expression child