I believe this may be our Content Security Policy blocking access to the link within our frames, due to the difference in hostname. Can I have you submit a ticket on this so we can work on getting this replicated in-house? There may be something development can implement to have these handled a little differently. Thanks!

I have created a ticket.  Thank you Kyle.

Thanks Shannon! Just following up here so anyone else searching can see the update as well. This error does look to be working as expected right now, and I'm going to meet with development to see what can be done to smooth out this behavior. Have a good one!