Activate Tab no longer works on legacy tabs/forms

[bvboas]

Preconditions (*)

1. Magento 2.4
2. Legacy Form with Left Tabs
3. URL with param: active_tab/TAB_NAME

Steps to reproduce (*)

1. Create a new record in a form with multiple left tabs
2. Select one, other than the first left tab
3. Save the form

Expected result (*)

1. Users should be redirected back to the form with the previous selected left tab active

Actual result (*)

1. Users are sent back to the form, and the first left tab is always selected

Media

1. Video example: https://imgur.com/a/pnb3Gh1

Other Info

• Replacing file contents of: vendor/magento/module-backend/view/adminhtml/templates/widget/tabs.phtml with the Magento 2.3 version, fixes the issue.

---

• [ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• [ ] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• [x] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• [ ] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant[bot]]

Hi @bvboas. 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 give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

  :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

:clock10: You can find the schedule on the Magento Community Calendar page.

:telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

:movie_camera: You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[m2-assistant[bot]]

Hi @ajijshekh123. 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: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• [ ] 3. Add Component: XXXXX label(s) to the ticket, indicating the components 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.

[ajijshekh123]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @ajijshekh123. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @ajijshekh123, here is your Magento Instance: https://aab21111c0983fea48aa2ca88b341131-2-4-develop.instances.magento-community.engineering Admin access: https://aab21111c0983fea48aa2ca88b341131-2-4-develop.instances.magento-community.engineering/admin_44ba Login: c0a3a192 Password: 24e666538c52

[ajijshekh123]

Hi @bvboas, I have verified your issue. This is not an issue. This is a Default Magento Feature. It is not required to redirect on the same tab. Let me close this issue. If you have any query you can reopen this issue/default feature.

Thanks.

[bvboas]

Hi @ajijshekh123 this is most definitely a Magento feature. It has been since version 1.

This bug was introduced by these two commits:

https://github.com/magento/magento2/commit/a3d9095b1352eb585399e7cce850112471955607#diff-926633484bdda3384356b3f61121a4e1

On line 34, the <li> element now has an ID attribute. The problem is that this ID is now duplicated, because the <a>element inside this <li> already has the same ID. And this now leads the "mage/backend/tabs" widget to fail loading the proper element

https://github.com/magento/magento2/commit/82f5a3696c55e65387fc330749e7267dcc269cf1#diff-926633484bdda3384356b3f61121a4e1

Added the CSS class 'no-display',

Please reopen this issue.

Regards,