SearchBuilder predefined searches and stateSave=true

jpu

When configuring a page with a predefined Searchbuilder search and the Datatable option stateSave=true I experience inadequate behavior in a sense that the predefined search is executed but the stored search is shown. Following test scenario:

1. first time page load => predefined search is executed and the predefined search condition is shown on the page
2. delete the predefined search condition and add an own SearchBuilder condition => new search condition is executed and shown with correct search condition
3. leave the page and then re-enter the page
4. Now the predefined search is executed but the search condition that is shown is the one stored in the state (from step 2)

In this situation the shown results do not match with the shown searchbuilder condition.

I do have the Datatable (server-side) option search.return set to 'true'. I would expect that:
- if search.return==true, the predefined search is executed , the stored condition is shown but not yet executed. The stored condition is only executed after triggering the search again.
- if search.return==false, then I would expect the last loaded condition to be executed and shown. It is unclear to me in which order the predefined search and the stored search are loaded and shown by the extension.