Yeah, this is definitely not browser-dependent @codinghorror. We have this happening on both Chrome and Firefox. And I think Safari too. So it’s acting mostly like a site code problem, not a stupid browser problem.
1 Like
