here is the errors related with this ticket, since not able to reproduce from the local env, shift focus to other tickets now, will back later https://docs.google.com/spreadsheets/d/1qVRqsfTWYSmx9ed5T9MlhaLpKk4sqCGo/edit?usp=sharing&ouid=109990517551911357524&rtpof=true&sd=true

Checking a few UA strings on this site shows this is not Safari but Chrome. So far I've only seen version 100. That version is old but apparently still supported.

Possible next steps, if they're considered to be worth the effort, might be to try to find specific places in the code where this could be happening, and counting how many such errors we get?

Thanks!!

I searched some recent logs for "Client side error", and found what seems like a relatively small number of errors, though many of the ones documented by @AnnWF here seem no longer to be occurring. (Thanks for that thorough research btw!! :) )

Looks like there are a few others... The total volume does not seem especially concerning, and they're probably mostly edge cases. Still, I think they could bear further digging when we get the chance.

Conclusion

• The error indicated in the task description is actually not from Safari, but from a relatively recent, still-supported Chrome version.
• I'd recommend separate tasks for reviewing and classifying client-side errors, and (if others agree, I think we might actually already have this) reviewing our client-side error monitoring to make sure would catch anything catastrophic quickly.

Thanks!!