Comment 6 for bug 1842749

@Matthias: I don't necessarily disagree with you -- this isn't even *really* my bug, I'm just acting as a liaison for my internal security team, since they don't have any visibility to upstream.

But, this is an issue that Horizon *can* easily fix, and I believe there is precedent (in a general sense) for taking steps to mitigate a possible security risk that could stem from something in our control. If we know that it is common for editors to badly handle CSV files, we can at least do our part to generate them in a way that's (hopefully?) more safe.