Autofill search field behaviour

[ianleeder]

Did something change on the search field behaviour? I have one site running UIOMatic 3.1.9.660, and if I enter a search term, navigate away and back, the field is empty.

I have another site running UIOMatic 5.1.4, and if I search, navigate away, and navigate back, the search field is pre-populated and my view is filtered.

[TimGeyssens]

what do you prefer? 😄

[ianleeder]

Personally I find it very misleading coming back to a page that is pre-filtered. It's not obvious that a search filter has been applied.

Is there a way to disable this behaviour? Even if it's in code, can you point me to it? I'm running from a fork at the moment anyway.

[timaaltra]

probably in the list view controller

[ianleeder]

Thanks @timaaltra, I found it in /src/UIOMatic/wwwroot/backoffice/uiomatic/list.controller.js:

$scope.searchTerm = state.searchTerm;
$scope.searchFilter = state.searchTerm;

I still find this "feature" disconcerting, as the search box is subtle, and the list doesn't indicate that it is filtered in any way.

I'm happy to close this "question", but not sure if you wanted to leave this as a prompt to revisit the implementation, or create a config entry to enable/disable this.

[JasonEleventeen]

Thanks @timaaltra, I found it in /src/UIOMatic/wwwroot/backoffice/uiomatic/list.controller.js:

$scope.searchTerm = state.searchTerm;
$scope.searchFilter = state.searchTerm;

I still find this "feature" disconcerting, as the search box is subtle, and the list doesn't indicate that it is filtered in any way.

I'm happy to close this "question", but not sure if you wanted to leave this as a prompt to revisit the implementation, or create a config entry to enable/disable this.

I added this feature a few years ago for a customer. The use case they had was opening an object for editing, and then clicking back cleared their search. When they were several objects deep, this became unworkable for the user as they lost the context of where they were. This was a simple fix that kept them happy. It might be more of a UX issue that it's not obvious a filter is being applied.