[Checkout Block] In the editor, the block does not reflect the Admin taxes settings

[ralucaStan]

Prerequisites

• I have carried out troubleshooting steps and I believe I have found a bug.
• I have searched for similar bugs in both open and closed issues and cannot find a duplicate.

Describe the bug

In the Editor the Checkout Block does not reflect the way tax settings are reflected in the Order summary depending on the tax settings: Display prices during cart and checkout

• Prices excluding of taxes: editor and store view are in sync
• Prices including of taxes: editor and store view are not in sync. The editor shows the view for Prices excluding of taxes

Prices including of taxes

• Admin setting

• Store view: Notice the text under total

• Editor view: Notice the missing text under the total & the Tax rows that does not show in the Store view

Prices excluding of taxes

Here things work as expected

• Admin setting

• Editor view

• Store view

Expected behavior

The editor view should reflect how things look on the Store view.

• Prices excluding of taxes: editor and store view are in sync - no change needed
• Prices including of taxes: the editor should remove the Taxes inner block and show the taxes information under the Total at the bottom of Order summary

Actual behavior

The editor shows 1 layout for both scenarious.

Steps to reproduce

1. set up taxes for your store
2. switch between the Display prices during cart and checkout options
3. notice how taxes are displayed in the Checkout Block in the Editor/store

Note: I only followed the recommended WooCommerce tax setup, where Prices entered with tax, Display prices in the shop and Display prices during cart and checkout have the same value. Ultimatelly the Display prices during cart and checkout should impact the output in the Editor

WordPress Environment

n/a

Isolating the problem

• I have deactivated other plugins and confirmed this bug occurs when only WooCommerce plugin is active.
• This bug happens with a default WordPress theme active, or Storefront.
• I can reproduce this bug consistently using the steps above.