That is very strange - that error is triggered by server-side events, not browser type.
I'll look into it.
That is very strange - that error is triggered by server-side events,
not browser type.
I'll look into it.