Comment 2 for bug 1745708

I’m facing the same problem, and it seems to work in Chromium too, although the coordinates of the second textPath are incorrectly calculated in this last browser.