Bug #97185
closed
backend searchbox in list view stays open
0%
Description
When an editor uses the searchbox in listview and then switches to another page in the page tree, the searchbox stays open and the previously used search is performed on the new page.
This is a pretty unexpected and nasty behaviour, because the elements on the new selected page are filtered.
A lot of editors complain about this behaviour. It was not the case in TYPO3 8.
Updated by Oliver Bartsch about 2 years ago
- Status changed from New to Needs Feedback
Hi, thanks for your report. I think this issue has already been fixed. Could you please check if the issue still exists for you in the current main branch or the current LTS version (v11)?
Updated by Oliver Weiss about 2 years ago
Oliver Bartsch wrote in #note-1:
Hi, thanks for your report. I think this issue has already been fixed. Could you please check if the issue still exists for you in the current main branch or the current LTS version (v11)?
Hi Oliver,
thank you for your answer. The problem has not been fixed in 10.4.26
Do you have a link to another bug issue or a patch?
Updated by Andreas Kiessling almost 2 years ago
A client reported the same issue to me:
There was a change labeled as regression https://github.com/TYPO3/typo3/commit/1cfc588be7b85cca40756574d350ee7da74a7396
But judging from the code in v8 and v9, this never worked since the value is overridden from _GP
v8: https://github.com/TYPO3/typo3/blob/9e1c91aed86490f75730ae186504bd900057107e/typo3/sysext/recordlist/Classes/RecordList.php#L219
v9: https://github.com/TYPO3/typo3/blob/57944c8c5add00f0e8a1a5e1d07f30a8f20a8201/typo3/sysext/recordlist/Classes/Controller/RecordListController.php#L279
The origin of this fix is in #94898 and describes a different usecase: search for something, open the record to edit, save/close -> search is reset
I'm not sure what the expected behaviour should be. As for the editing: keeping the filter would be good. Switching pages otoh should probably drop the search value.
Updated by Riccardo De Contardi over 1 year ago
I think this issue is still reproducible on 11.5.16
Updated by Oliver Weiss over 1 year ago
This issue seems to be fixed. I cannot reproduce it in Version 11.5.21.
Updated by Riccardo De Contardi over 1 year ago
- Target version deleted (
next-patchlevel)
Hi @Oliver Weiss and thank you for your feedback. Do you mind if I close this issue as solved?
Thanks
Updated by Riccardo De Contardi 12 months ago
- Status changed from Needs Feedback to Closed
I think it's safe to close this issue now.
If you think that this is the wrong decision or experience the issue again please open a new issue with a reference to this one.
Thank you