You were not alone.

The epic takedown post of the issue on stackexchange which proved it is below, I ended up at it from somewhere on social I think.