1092535 - SVG element disappears on click/animation

Status: RESOLVED WORKSFORME

(Core :: SVG, defect)

Description

[uzuri.wolf]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:33.0) Gecko/20100101 Firefox/33.0
Build ID: 20141027150301

Steps to reproduce:

Twas asked to file this as a separate bug from https://bugzilla.mozilla.org/show_bug.cgi?id=969270.

If you visit http://theredsetter.com/cs171/ and click the big red button you'll be presented with a svg large node diagram.  Click on any one of the four colored circle labels to see the circle disappear.   To see what it *should* do (and what it was doing until recently), filter the results using "show only" and try again.    If you remove your filter, it will also go back to working as expect.


Actual results:

Circle labels disappear.


Expected results:

The circle should have rotated.  The nodes do, but the labels do not.  Filtering makes them work again.

Comment 1

[Robert Longson [:longsonr]]

Really needs a reduced testcase to make progress. Seems to be something to do with setting transforms but the patches in my tree don't help.

Comment 2

[uzuri.wolf]

I'll see if I can come up with a limited version, though it may have something to do with the fact that this particular vis is as heavy as it is -- if you check old versions of the vis (http://theredsetter.com/cs171/assetlist.html) some of the older ones don't give a problem.  Maybe some sort of memory overload going on?

Comment 3

[uzuri.wolf]

Hi folks, I believe I've stripped this down to its bare minimum.  ALL that exists now is the rotation code -- here's the new link: http://theredsetter.com/cs171/snapshots/test20141120.html  No nodes, no links, no extraneous animation or transforms, whole thing rings in at 250KB, most of which is the d3 library and the json feed.

Interesting side effect of snipping things down is that I discovered that if you DOUBLE click to rotate, you may very well get your circle back.  Once it's back the rotation works perfectly and it won't disappear again (unless you refresh the page).  No errors thrown.

Comment 4

[Robert Longson [:longsonr]]

seems OK now as far as I can tell.