[_]: fix/checkout-tax-flash-flash-on-billing-country-refetch - #2103
Merged
Conversation
Deploying drive-web with
|
| Latest commit: |
a773b23
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://4e4e97fb.drive-web.pages.dev |
| Branch Preview URL: | https://fix-checkout-tax-flash.drive-web.pages.dev |
jaaaaavier
approved these changes
Aug 6, 2026
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Restores
postalCodein the debounced price refetch triggered by billing address changes inCheckoutViewWrapper, and guards the effect so it only fires once both country and postal code are known.Why
Since
9cc570d47("checkout fixes"),billingCountryis populated immediately from IP geolocation on page load (before the user enters anything), which fires a refetch of the price ~500ms later using onlycountry(nopostalCode, nouserAddress). That refetch returns a different tax amount than the initial fetch, so the tax line item flashes on screen and then disappears. The actual charge is unaffected (postal code is read from the Stripe confirmation token at payment time), so this was a display-only regression.