Yep, that’s exactly the issue! I’ve fixed it so it no longer throws the TouchEvent error in Firefox. Thanks for flagging it.