I'm afraid this is invalid Philipp. ASV is wrong to forward function calls out to the containing HTML like that. You should be explicit if it's the function in the containing HTML that you want to call. Add "top." to get the right scope. top.func(...);
But if it's in some iframe in-between I have to find the correct number of parent-calls? I thought that it would be marked as INVALID. But it's a use-case that works with the "old" version (and with IE), so I believe it's some kind of regression.
By "old version" do you mean an old version of moz with *native* SVG? If so that would be a very bad bug. I'd want to track down when this got "fixed" and check that there really was a fix, rather than an accidental change. If you mean ASV in Firefox, it's ASV that was at fault. To answer your question, you would use 'parent' instead of 'top'. To go up one doc level: parent.func(...); To go up two doc levels: parent.parent.func(...); Etc. Unfortunately 'parent' is broken in ASV, hence why I suggested using 'top'. If you have to work around this you'll have to use 'top' then drill back down towards the SVG to the doc containing the function you want to access.