This bug is a old regression and happens on Linux only. (Recent regression of Nightly34.0, see Bug 1055968.) This bug happens Firefox28.0, 29, 30, 31, Beta32, Aurora33.a2. The bug was fixed in Nightly29.0a1 once. However, the problem reappeared when the merge was performed from Nightly29.0a1 to Aurora29.0a2.  Progression window in Nightly29 Bad: http://hg.mozilla.org/mozilla-central/rev/711f08b0aa1d Mozilla/5.0 (X11; Linux i686; rv:29.0) Gecko/20100101 Firefox/29.0 ID:20140109030203 Fixed: http://hg.mozilla.org/mozilla-central/rev/37516445a0b5 Mozilla/5.0 (X11; Linux i686; rv:29.0) Gecko/20100101 Firefox/29.0 ID:20140110030650 Fixed pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=711f08b0aa1d&tochange=37516445a0b5  Last Good in 29 in Nightly: http://hg.mozilla.org/mozilla-central/rev/44ba69cacd7e Mozilla/5.0 (X11; Linux i686; rv:29.0) Gecko/20100101 Firefox/29.0 ID:20140203030203 First Bad in 29 in Aurora: https://hg.mozilla.org/releases/mozilla-aurora/rev/977eb2548b2d Mozilla/5.0 (X11; Linux i686; rv:29.0) Gecko/20100101 Firefox/29.0 ID:20140204004003 Steps To Reproduce: Open http://www.w3.org/TR/SVG/images/text/toap01.svg
It doesn't seem to display correctly on Firefox 31 on a Mac.
Could it be bug 941585
It broken again after uplift to Aurora34.a2 from Nightly34.0a1 I do not understand that it become broken immediately after uplift to Aurora from Nightly
status-firefox34: --- → affected
Summary: SVG Text on a path is broken on Release, Aurora and Beta → SVG Text on a path become broken immediately after uplift to Aurora from Nightly
:bas.schouten, Why does it become broken immediately after uplift to Aurora from Nightly?
Where is this broken right now?
(In reply to Bas Schouten (:bas.schouten) from comment #5) > Where is this broken right now? It works as expexted on Nightly37.0a2, Aurora36.0a2 and Beta35.0. But It is broken on Firefox esr31.0.3 and Firefox34.0.5. -> Mark wontfix
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.