I have tested this item ✅ successfully on 5d62196

RTC

Sorry why should we hard code the default to 20? and what's the problem with our configuration option? don*t we use the same functionality in com_content?

It is not hard coded to 20. It uses the list_limit defined in global configuration. But as also shown below I dont get the same layout - and shouldnt the button be called search not filter?

I only looked at the code

-			$limit = $app->getUserStateFromRequest('global.list.limit', 'limit', $app->get('list_limit'), 'uint');
+			$limit = $app->input->get('limit', $app->get('list_limit', 20), 'uint');

and getuserstatefromrequest should do the same as input->get but also set the user preference in the session.

Edit: I miss read this as remove of the default, but it removes the com_contact .xml options if i'm not wrong?

don*t we use the same functionality in com_content?

Nope. We do not have a articles__num as Options in the xmls for articles List Layouts

The contact specific field option in the xmls (contacts_display_num) are unecessary as it is only used to force a specific limit which is ALWAYS set, which created the original issue

before the patch we had in Contacts CategoryModel:

		$numberOfContactsToDisplay = $mergedParams->get('contacts_display_num');

		if ($format === 'feed')
		{
			$limit = $app->get('feed_limit');
		}
		elseif (isset($numberOfContactsToDisplay))
		{
			$limit = $numberOfContactsToDisplay; // As this is always set, it forces that limit...
		}
		else
		{
			$limit = $app->getUserStateFromRequest('global.list.limit', 'limit', $app->get('list_limit'), 'uint');
		}

20 is indeed basically a default.
Same code is used for frontend Articles Model concerning the category list.

and shouldnt the button be called search not filter?

That's what it is called for articles list.

Folks, I basically have done all these contacts related frontend list refactoring PRs based on what we already have for articles.
For example, there is a debate here about the use of a fieldset or not.
#30868
Taking out the fieldset element would also change the display, pushing the list limit to the right for the contacts lists. Articles may need more refactoring.

As requested modified to use back getUserStateFromRequest
No change in behavior.

I have tested this item ✅ successfully on daf7d61

@HLeithner
Good to go.