Hi, Mark.
We’ve seen this happen when a user’s browser does not have JavaScript enabled.
I’ll mark this ticket as Pending Fix, which means this thread should receive a reply once the applicable fix has been released. I cannot guarantee when it will be fixed as it’s in the development team’s hands now. They need to assign it, code it, test it, and schedule it for release.
I apologize for this issue and appreciate your understanding and patience.
As a temporary solution that might work for you, here’s a code snippet to implement <noscript>
https://gist.github.com/cliffordp/9edebb79954507935ddb8a9b323ae1b5
Please let me know if this solved the issue for you.