A filter value whose comparison operator is preceded by a space is read as a pattern

The filter values of the getChanges macro, and of the change search behind it, may be prefixed with a comparison operator: versions=">=9.0". The operator is read from the very first characters of the value, so a value written with a space before it is not read as a comparison at all.

versions="8.3%, >=9.0" – which is what a reader typing a list of filters into the custom report form naturally writes – therefore asks for the changes whose version is like the text ">=9.0", which matches no change, and says nothing about it.

Trimming each value before looking for its operator would fix it, and cannot break a filter that works today: a value whose operator is preceded by a space matches nothing as things are.

Found while moving the search to Java (RN-114), where the behaviour was deliberately kept as it was so that the port changed nothing.