« 2005-02-21 Weekly Update | Main | 2005-02-28 Weekly Update »
February 21, 2005
Important SVG Build Change
Bug 258511 was just checked in, which provides a preference to enable and disable native SVG support. By default this is set to disable support. To enable native support, you need to set the "svg.enabled" preference to true.
For those unfamiliar with mozilla preferences, here are the steps you need to follow. This only needs to be done once, after which it will be stored in your profile.
- Go to the url "about:config"
- Type "svg" in the filter field
- Double-click the "svg.enabled" line so that the value is "true"
Posted by tor at February 21, 2005 6:13 PM
Comments
svg.enabled is not in my about:config what must I do?
Posted by: aasgier at February 21, 2005 6:32 PM
Is this required for the Firefox + SVG trunk builds aswell or is this a seamonkey-only setting ?
Posted by: Peter van der Woude at February 21, 2005 7:22 PM
If "svg.enabled" is not in about:config then you are using a build prior to the preference checkin. This is a common change to firefox and seamonkey.
Posted by: tor at February 21, 2005 7:34 PM
so what are these SVG "security" issues?
Posted by: m00 at February 22, 2005 10:57 AM
Just to post this here rather than the above listed bug...Does this mean that tinderboxen will start building with --enable-svg by default now (for suite or FF)? In the bug there was some talk about what the drivers wanted which sounded strange to Boris. I am just curious if we can get some feel on SVGs role in upcoming releases? It has been hinted that during 1.8/1.9 it will be included, but I have always thought that FF will never include it other than as an XPI. They won't even dynamically link against the GRE, so I am guessing they will not want the codesize gain that SVG will give them. What do I know though....
Posted by: modok at February 22, 2005 5:28 PM