When working in multiple tabs within the same category (e.g., item list), switching pages in one tab may unexpectedly change its filter to match the last opened tab. This can cause confusion, incorrect data views, and extra steps for the user to restore their intended filter.

Example steps to reproduce for item list view:
1. Open the item list view in the first browser tab with a filter set to hostA;
2. open the item list view in a second browser tab with a filter set to hostB;
3. in the first tab (hostA), navigate to page 2 (requires multiple items);
4. observe that the filter in the first tab changes to hostB.

The filter in the active tab is overwritten by the filter from the last opened tab. This affects not only items, but all frontend object lists since early versions. Multiple tabs can be opened in quick succession (e.g., via middle-click). Whichever tab is opened last updates the filter in the user profile. So from a user perspective, it is not correct for the active filter to change due to actions in another tab.

Additionally when paging, most list views only include only action and page (sometimes context) in the URL, while item list includes more (all?) filter parameters - which has no effect when switching pages.

Paging does not include filter_set=1. Adding it might resolve the issue. But CProfile class needs to make sure values are saved to DB only if values are changed, so that every page change doesn't a database write.

There's also a minor difference in configuration and monitoring sections. In configuration if only one host is set in filter, it is kept after pressing the "Reset" button. But in monitoring section like Latest data page, pressing "Reset" clears all the filter including selected host. Therefore in configuration section there's a similar case with the "Reset" button. Same scenario:
1. Open any list view with filter in the first browser tab with a filter set to hostA;
2. open any list view with filter in a second browser tab with a filter set to hostB;
3. in the first tab (hostA), click "Reset" button";
4. observe that the filter in the first tab changes to hostB.