Magento2: Page Should be scrolled towards the message area after product is added to cart

[sudheer-gajjala]

Description (*)

Page Should be scrolled towards the message area after product is added to cart. So that the user can be acknowledged with the response message.

Expected behavior (*)

Currently the page is not scrolled towards the messages section so, he will be missing out the specific information.

Benefits

User can understand the event after he adds the product to cart.

Additional information

[m2-assistant[bot]]

Hi @sudheer-gajjala. 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.

@sudheer-gajjala do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• [ ] yes
• [ ] no

---

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

[m2-assistant[bot]]

Hi @sudheer-gajjala. 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_!

---

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

[m2-assistant[bot]]

Hi @shikhamis11. 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.

[magento-engcom-team]

:white_check_mark: Confirmed by @shikhamis11
Thank you for verifying the issue. Based on the provided information internal tickets MC-29883 were created

Issue Available: @shikhamis11, _You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself._

[krishprakash]

Hi @shikhamis11. I don't think this consider as an issue.
This is default magento behavior since magento 2.2.
Let me know your thoughts on this
Thanks.

[shikhamis11]

hi @krishprakash , Thank you for your feedback :)
yes at first look it seems to be default behaviour and not an issue but if we go for user perspective this seems to be a issue thats why I confirmed it.

[krishprakash]

@shikhamis11 another use case as per user perspective:
If user want to add to cart 2-3 products from same product row or after next row then every time user need to scroll down to that product row for add to cart that product.
As currently user can see the Add to cart button changed to added once click on it so user can know.

[shikhamis11]

@krishprakash
there can be multiple cases , I will discuss about it and update here.

[sdzhepa]

Hello @sudheer-gajjala and @shikhamis11, @krishprakash

Thank you for contribution and collaboration!

First of all, I want to say that I agree with each of you in this thread:

• This is default Magento behavior that was made intentionally and currently it is expected behavior
• Also, it sounds like nice to have an improvement for user experience
• On the other hand, user scenario _"If user want to add to cart 2-3 products from same product row or after next row then every time user need to scroll down to that product row for add to cart that product."_ make sense because it could create a bad user experience for other groups of merchants/users

Anyway, such functional changes/improvements should be discussed and proved by Magento Product Owner(PO) who is responsible for this functionality. I will discuss it with the PO and share the result here but I will be able to do it only after 1st of January due to Christmas Holidays

[m2-assistant[bot]]

Hi @sdzhepa. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• [ ] 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

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

• [ ] 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

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

[krishprakash]

mm20in

[krishprakash]

@sdzhepa any suggestion for this improvement.
Thanks

[sdzhepa]

@magento give me 2.4-develop instance

[magento-engcom-team]

Hi @sdzhepa. Thank you for your request. I'm working on Magento 2.4-develop instance for you

[magento-engcom-team]

Hi @sdzhepa, here is your Magento instance.
Admin access: https://i-26098-2-4-develop.instances.magento-community.engineering/admin_2684
Login: ffa537b9 Password: 5d681aedd2ee
Instance will be terminated in up to 3 hours.

[shikhamis11]

hi @krishprakash @sdzhepa
thanks for clarifications .. It was intentionally made to improve user experience so I am closing this issue .