"This item has weight" switcher is not sensitive to weight changes

[TomashKhamlai]

When the product is virtual Merchant cannot set the weight before he hasn't switched to "The item has weight" and from this point, the issues sounds pointless. But there is another way to update weight from Magento UI with virtual configurable variants

Preconditions (*)

1. Explanation to Configurable product is not display shipping information on checkout page #23957 and Merchant will have problems with shipping if price of configurable is $0.00 and configurable variation has weight #23912

Steps to reproduce (*)

1. Create Configurable Product.
   Fill name, SKU and price = 0.00
   Leave everything else as is
   Click Create Configurations button
   Select attribute color
   black - $1 - 1000, white - $2 - 1000
   Click Generate Products
   Click Save Product
2. Verify that the product variants are of virtual type
3. Edit configurable product
   Click "Edit Configurations"
   End generation process without any changes
   Change the weight of all variations to 1 and set the quantity of the first variation to 0 in the configuration grid of the product edit page
4. Save the product

Expected result (*)

1. Qty change to 0 leads to the "Out of Stock" state of the product
2. Weight change leads to the "This item has weight" state and the virtual product is simple product now.

Actual result (*)

1. Qty change to 0 leads to the "Out of Stock" state of the product
2. Weight change does not lead to the "This item has weight state" however the weight was saved even in grey color (disabled input)

[m2-assistant]

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

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

@TomashKhamlai 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]

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).

  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.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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]

✅ Confirmed by @engcom-Bravo
Thank you for verifying the issue. Based on the provided information internal tickets MC-18856 were created

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

[m2-assistant]

Hi @arushibansal013. 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.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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.