3 ms·
> Is there any concern that limiting JavaScript's functionality could cause unexpected behavior? E.g., your credit card is charged upon checkout but next part o
by woodruffw 5y ago
> Is there any concern that limiting JavaScript's functionality could cause unexpected behavior? E.g., your credit card is charged upon checkout but next part of payment flow isn't triggered and your order isn't actually placed.
I thing this was a common concern with the first few generations of content blockers, one that's mostly proved to be a non-issue. It's not my space, but if I had to take two guesses:
1. Most analytics code is sufficiently flaky and unreliable to keep it far away from the critical concrete value path of someone actually paying with a card.
2. Most developers are probably running content blockers.