Next Page button triggered when filtering Customer grid

[lucasjor-summa]

Preconditions

1. Magento 2.2.2
2. 20+ customers created in order to have many pages in Customer grid

Steps to reproduce

1. Go to "Sales -> Orders"
2. "Create new order"
3. Customer grid is displayed
4. Focus on any column filter (i.e. text box in email column)
5. Press ENTER to trigger the filter

Expected result

1. Filter's AJAX call is triggered
2. Results don't change because the filter input was empty
3. Grid is still showing the same page.

Actual result

1. Filter's AJAX call is triggered
2. Next Page AJAX call is triggered at the same time (see screenshots)
3. Results don't change because the filter input was empty
4. Grid is showing the next page now
   
   

[magento-engcom-team]

Hi @lucasjor-summa. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento-engcom-team give me {$VERSION} instance

where {$VERSION} is version tags (starting from 2.2.0+) or develop branches (2.2-develop +).
For more details, please, review the Magento Contributor Assistant documentation.

@lucasjor-summa do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

[lucasjor-summa]

I confirm that I was able to reproduce the issue on vanilla Magento 2.2.2 CE

@lucasjor-summa , thank you for your report.
We've acknowledged the issue and added to our backlog.

[magento-engcom-team]

Hi @lucasjor-summa. Thank you for your report.
The issue has been fixed in #17870 by @ronak2ram in 2.2-develop branch
Related commit(s):

• 964d4ef8763df82c7e47860acda7ab855d819b35
• 4150ad1ffd1061e342167fea15cabb3a51178c81
• 6fb0594ab4160c0ea47d58c45757dfde10861d6e

The fix will be available with the upcoming 2.2.7 release.