Checkout/Tax: Unaligned prices in cart

[deBhal]

Steps to reproduce

1. Make sure there's a plan or domain or something in your cart
2. Open `http://calypso.localhost:3000/checkout/${SITE}?flags=show-tax&total_tax_display=A$12.34&display_taxes=true&total_cost_display=A$348.34`
3. Have a look at the text alignment in the cart (Don't worry that they don't add up):

I think the ideal would be to align prices using both the separator and the currency symbol, e.g.:

A$ 336
A$  12.34
--------
A$ 348.34

Maybe adding the missing cents if one of the other values has them.

We're already going to use a table here, and the lib/format-currency::getCurrencyObject() function will break down the price for us (see cart-item.jsx), so this shouldn't be very hard to do, but we can put it off until the core functionality in place, so I'll mark it low priority.

[davipontesblog]

Moved to Checkout Redesign for triaging.

[michaeldcain]

Confirmed that this is still an issue with the new Checkout flow. It's pretty low priority, given that you need to start with a zero decimal cart subtotal and a taxable location, and it's not as significant in the new design, but I'll add it to the Shilling backlog.

To reproduce:

• add a WPcom zero decimal plan to your cart
• set your location to a taxable one (ie. 10001)
• look at the cart summary under the payment method step

[github-actions]

This issue is stale because it has been 180 days with no activity. You can keep the issue open by adding a comment. If you do, please provide additional context and explain why you’d like it to remain open. You can also close the issue yourself — if you do, please add a brief explanation and apply one of relevant issue close labels.

[github-actions]

This issue is stale because it has been 180 days with no activity. You can keep the issue open by adding a comment. If you do, please provide additional context and explain why you’d like it to remain open. You can also close the issue yourself — if you do, please add a brief explanation and apply one of relevant issue close labels.

[github-actions]

This issue is stale because it has been 180 days with no activity. You can keep the issue open by adding a comment. If you do, please provide additional context and explain why you’d like it to remain open. You can also close the issue yourself — if you do, please add a brief explanation and apply one of relevant issue close labels.

[cuemarie]

Hi @michaeldcain ! Kitkat is working on reviewing issues that have been marked [Status] Stale for a long time, and manually closing them, as part of this project: pdqkMK-14B-p2 .

This issue falls under that category, but I see you've recently filed it within Shilling's backlog board. Do you think this warrants leaving open for Shilling to get to, despite it's stale status and age? Let me know your thoughts!