On 3/7/07, Dan Bond <dan dot bond at gmail dot com> wrote:
> Figure that's because you've got the Adobe SVG plugin installed, which
> I don't think people have an issue with. The issue is with the Mozilla
> implementation of SVG and how it's rendered. Somewhere in the back of
> my mind I seem to remember something about some implementations not
> holding as strictly to the spec as they should (what's new), is it
> that the m0n0 SVG has been written to work with the Adobe plugin
> because it's the dominant solution?
There were changes made in m0n0wall when Firefox's built in SVG
support first came out so it worked right with it. Those changes were
provided by a Firefox developer, IIRC. It currently works fine with
either the current Firefox's SVG or Adobe's SVG. (except for the guy
running Windows 98, sheesh, who runs that crap anymore... I can't say
I'm surprised it doesn't work on 98, and there's no telling what the
issue may be).
My guess is it's a bug in Firefox 3.0 (it is alpha, after all), or
they changed something so m0n0wall is going to need another change.
Either way, unless another Firefox dev pops up with a fix, I wouldn't
expect it to get looked at until Firefox 3.0 is much closer to