magento / magento2

Prior to making any Submission(s), you must sign an Adobe Contributor License Agreement, available here at: https://opensource.adobe.com/cla.html. All Submissions you make to Adobe Inc. and its affiliates, assigns and subsidiaries (collectively “Adobe”) are subject to the terms of the Adobe Contributor License Agreement.
http://www.magento.com
Open Software License 3.0
11.53k stars 9.31k forks source link

"Clear Shopping Cart" button not working in Internet Explorer #24491

Closed andrew-ebsco closed 5 years ago

andrew-ebsco commented 5 years ago

Preconditions (*)

  1. Magento Commerce 2.3.2
  2. PHP 7.2.21

Steps to reproduce (*)

  1. Open Magento 2 site in Internet Explorer
  2. Add item to the cart
  3. Click Clear Shopping Cart button

Expected result (*)

  1. All items are deleted from the shopping cart
  2. The cart page is refreshed showing no items

Actual result (*)

  1. The page refreshes and all cart items are still in the cart

The issue is caused by line 18 of app/code/Magento/Checkout/view/frontend/web/js/shopping-cart.js. The on click handler for the Clear Shopping Cart button checks if event.detail is 0 before proceeding. There is a bug in Internet Explorer 11 that causes the event.detail attribute to always be 0. As a result, you cannot clear the cart in IE.

Here is the IE bug report explaining that event.detail will not be fixed: https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/16710370/

m2-assistant[bot] commented 5 years ago

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

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.3-develop instance - upcoming 2.3.x release

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

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


andrew-ebsco commented 5 years ago

@magento give me 2.3-develop instance

magento-engcom-team commented 5 years ago

Hi @andrew-ebsco. Thank you for your request. I'm working on Magento 2.3-develop instance for you

magento-engcom-team commented 5 years ago

Hi @andrew-ebsco, here is your Magento instance. Admin access: https://i-24491-2-3-develop.instances.magento-community.engineering/admin Login: admin Password: 123123q Instance will be terminated in up to 3 hours.

andrew-ebsco commented 5 years ago

I was able to confirm the issue in a vanilla Magento instance using the Magento Blank theme. The Luma theme removes the Clear Shopping Cart button.

m2-assistant[bot] commented 5 years ago

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


m2-assistant[bot] commented 5 years ago

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

m2-assistant[bot] commented 5 years ago

Hi @dmytro-ch. 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:

magento-engcom-team commented 5 years ago

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

Issue Available: @dmytro-ch, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

magento-engcom-team commented 5 years ago

Hi @andrew-ebsco. Thank you for your report. The issue has been fixed in magento/magento2#24499 by @edenduong in 2.3-develop branch Related commit(s):

The fix will be available with the upcoming 2.3.4 release.