I was searching for an existing thread about it but didn’t find any…
Indeed it seems to be a Chromium issue (but also in Chrome on Android…) so will have to wait…
But to be honest, while it might be “triggered” by something Chromium did, it still seems that there’s something off with this SVG code (as a sign of it… check what happens when you open this SVG with this online editor http://vectorpaint.yaks.co.nz/ - which randers all my smaple SVGs all good. It bsically shows only the i! So the i is treated diffrently for some reason.)