Admin: Page Actions Buttons floating left instead of right

[pawan]

Preconditions and environment

• Magento version: 2.4.7
• Anything else that would help a developer reproduce the bug

Steps to reproduce

• Login to Admin
• Go to Stores >> Settings >> Configuration OR Customers >> All Customers >> Add New Customer
• Now scroll page
• On sticky header, Page Actions Buttons floating left instead of right

Expected result

• On sticky header, Page Actions Buttons should float to right

<img width="1345" alt="Screenshot 2024-05-07 at 11 58 03 AM" src="https://github.com/magento/magento2/assets/22196227/e2df443d-9748-4b3d-b984-43da8c749246"]

Actual result

• On sticky header, Page Actions Buttons floating to left

[img width="979" alt="Screenshot 2024-05-07 at 11 56 13 AM" src="https://github.com/magento/magento2/assets/22196227/8a21d9a4-8960-4352-a394-c1b322a7a0d9"]

Additional information

No response

Release note

No response

Triage and priority

• [ ] 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.
• [ ] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• [X> Severity: S4 - Affects aesthetics, professional look and feel, "quality" or "usability".

[m2-assistant[bot]]

Hi @pawan. 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. :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, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant[bot]]

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: :point_down:

• [ ] 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.

[pawan]

@magento I am working on this

[m2-assistant[bot]]

Hi @engcom-Dash. 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).
• 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!

---

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

[engcom-Dash]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

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

[magento-deployment-service[bot]]

Hi @engcom-Dash, here is your Magento Instance: https://3ff75f205a9068027c2ff9187e56b9f2.instances-prod.magento-community.engineering Admin access: https://3ff75f205a9068027c2ff9187e56b9f2.instances-prod.magento-community.engineering/admin_8846 Login: 63c61b65 Password: 753617dd4099

[engcom-Dash]

Hi @pawan

Thanks for reporting and collaboration.

Verified the issue on magento 2.4 dev instance and 2.4.7 instance and the issue is reproducable.

On sticky header, Page Actions Buttons floating to left. Hence, we are confirming this issue.

Steps to reproduce

1. Login to Admin
2. Go to Stores >> Settings >> Configuration OR Customers >> All Customers >> Add New Customer
3. Now scroll page
4. On sticky header, Page Actions Buttons floating left instead of right

[github-jira-sync-bot]

:white_check_mark: Jira issue https://jira.corp.adobe.com/browse/AC-11919 is successfully created for this GitHub issue.

[m2-assistant[bot]]

:white_check_mark: Confirmed by @engcom-Dash. Thank you for verifying the issue.
Issue Available: @engcom-Dash, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[engcom-Bravo]

Hi @pawan,

Internal team has started to work on it

Thanks.

[pawan]

@engcom-Bravo i already created PR https://github.com/magento/magento2/pull/38713. Can we review and merge it ?

[engcom-Bravo]

Hello,

As I can see this issue got fixed in the scope of the internal Jira ticket AC-11919 by the internal team Related commits:https://github.com/search?q=repo%3Amagento%2Fmagento2+AC-11919&type=commits

Based on the Jira ticket, the target version is 2.4.8-beta1.

Thanks