@TechieNotNetie @downey this is fascinating, thank you. i have actually started seeing that error as well despite using a fully updated firefox; i suspected it was my scriptblocker for some reason and can only assume from your comment that i was right. interesting but frustrating.