Strange bug in xforms repeat in Orbeon 2018.1CE

Here’s a screenshot of the application I’m working on:

It’s essentially a master-detail view with a search function and result view and below a detail view of the selected concept. When a user changes the selection in the result the detail should change accordingly, so far so good. The user can define a value set using the buttons in the detail view. After each action the search result is validated against the value set definition, this no longer works because the index is moved to the last position after instance replacement. Storing and restoring the index position does not work in this case because the user can navigate (using the links in the detail view) to a concept not in the search result, hence the need for a separate nodeset-changed event to distinguish user actions from system actions. The way it is now (Orbeon 2018) there’s no distinction anymore as the index-changed event will now always fire when the nodeset is replaced, this is a significant change of behaviour from the last version. IMHO the index-chaged event should not fire when a nodeset is replaced.

Kind regards,

Gerrit