Heard. Thanks @Pete_Hartnett
Time to wrap this thing up.
@Pete_Hartnett Thank you for being able to see the forest for the trees. The support tech assigned to our case would not even consider any thing not related to the custom widget, which resulted in a massive waste of time on all fronts.
We have not implemented Looper v2 yet as to observe the results of moving from firefox. Since getting the stations off firefox the client has experienced no further instances of the issue.
We opened our support ticket on August 22nd. It took until September 25th for the clients frustration to build to a point where it warranted bringing this to the community.
I bring this up because the clients confidence in Tulip support has been significantly diminished as a result of this case.
Thanks all who contributed to the solution.