Yes I do.
>> I have, on multiple occasions, introduced bugs that are orders of magnitude wackier than this.
Those would make a nice blog post. I've done some stupid things and seen some unexpected results, but I've never encountered the likes of this "accidentally" incrementing price thing. ;-)
It could be that some local taxes or fees comes out to $10, and the client code does `price += taxes` on page load.
There could be code to round up to a $10 increment, and then subtract 2 cents so the prices are all $X9.98, but the rounding logic is incorrect. Since this is JS, they will be using floating point prices. That is a minefield in itself.
I'm not saying it's definitely a bug. But it trivially could be.
* Modify value to give local amount, not realising it's modifying a cached value
* Never test refreshing doesn't change the price
But why would ANY price be determined in part by the users browser. It gets it right the first time, so why would page reload do anything different? This makes no sense.
> gets it right the first time,
Maybe, you don't know.
It may be adding $10 the first time too.