The grid’s Default View dropdown is showing as blank

[lubnaboghara]

Preconditions (*)

Tested on this versions:
1. Magento 2.4.6-p4
2. Magento 2.4-develop branch

Description (*)

When navigating to any grid page, such as the product or order grid, the user can create new views by selecting the 'Default view' dropdown menu. However, after creating a new view and naming it 'filter', it is saved in the database but not displayed in the dropdown menu. Additionally, upon refreshing the page, the entire view section becomes blank.

This issue triggers an error in the console, specifically a TypeError that states "number 0 is not a function."

Screenshot 1: Before refreshing the page

Screenshot 2: After refreshing the page

Steps to reproduce (*)

1. Access the Magento admin panel and navigate to any grid.
2. Navigate to the "Columns" section and select or deselect any field.
3. Click on the default view dropdown menu and then select the "Save View As..." option.
4. Name the view as 'filter' and then press Enter. You may notice that it does not appear in the dropdown menu.
5. Subsequently, after refreshing the page, all the views disappear.

Screenshot 3:

Screenshot 4:

Screenshot 5:

Screenshot 6:

Expected result (*)

1. Naming a view as ‘filter’ should not cause any issue and should show the default view dropdown correctly.

Actual result (*)

1. Naming a view as 'filter' results in the default view dropdown showing as blank.

Additional information (*)

File path: vendor/magento/module-ui/view/base/web/js/lib/knockout/bindings/i18n.js

After debugging the issue, I discovered that, In the ‘execute’ function of the 18n.js file, it translates the text using ‘$.mage.__(original)’. Therefore, when naming the view as ‘filter’, it converts it into the function ‘ ƒ filter() { [native code] } ‘.

In the ‘setText’ function, it sets the texts in the element, but it seems to be triggering an error. It's unclear why it's converting the word "filter" into a function.

Screenshot 7:

Screenshot 8:

[m2-assistant]

Hi @lubnaboghara. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

Hi @engcom-Bravo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Bravo]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @engcom-Bravo. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @engcom-Bravo, here is your Magento Instance: https://41a888d2ca8788cfc7543c96cecf406f.instances-prod.magento-community.engineering
Admin access: https://41a888d2ca8788cfc7543c96cecf406f.instances-prod.magento-community.engineering/admin_958b
Login: 6a7e2369
Password: 98e8a613012e

[engcom-Bravo]

Hi @lubnaboghara,

Thank you for reporting and collaboration.

Verified the issue on Magento 2.4-develop instance and the issue is reproducible.Kindly refer the screenshots.

Steps to reproduce (*)

• Access the Magento admin panel and navigate to any grid.
• Navigate to the "Columns" section and select or deselect any field.
• Click on the default view dropdown menu and then select the "Save View As..." option.
• Name the view as 'filter' and then press Enter. You may notice that it does not appear in the dropdown menu.
• Subsequently, after refreshing the page, all the views disappear.

Naming a view as 'filter' results in the default view dropdown showing as blank.

Hence Confirming the issue.

Thanks.