Yes, I left it out as this issue has clearly escalated during the last couple of weeks, while we have not updated our Discourse codebase for some time. This might hint that the issue is on the Chrome side.
Also as @sam suggested, it is possible that there are actually multiple issues with similar symptoms. We have to narrow it down somehow.