43
edits
Talk:SeaMonkey:First Release: Difference between revisions
MNG
m (→SVG) |
Pweilbacher (talk | contribs) (MNG) |
||
| Line 26: | Line 26: | ||
* I just tested a SVG-enabled nightly build of Seamonkey. While the support is not complete, IMO it is definitely enough to have it '''built by default, but turned off'''. This way, interested users can simply turn it on via about:config (svg.enabled -> true, doesn't even need a browser restart), giving web developers something to play (and learn) with, and could lead to valuable feedback to the people working on SVG. And remember: as Seamonkey isn't Firefox, we don't have a five-megabyte download size limit! What do you all think? --[[User:Jens.b|Jens.b]] 13:10, 17 Mar 2005 (PST) | * I just tested a SVG-enabled nightly build of Seamonkey. While the support is not complete, IMO it is definitely enough to have it '''built by default, but turned off'''. This way, interested users can simply turn it on via about:config (svg.enabled -> true, doesn't even need a browser restart), giving web developers something to play (and learn) with, and could lead to valuable feedback to the people working on SVG. And remember: as Seamonkey isn't Firefox, we don't have a five-megabyte download size limit! What do you all think? --[[User:Jens.b|Jens.b]] 13:10, 17 Mar 2005 (PST) | ||
== MNG == | |||
Any more thoughts on MNG? There are still lots of voters for [https://bugzilla.mozilla.org/show_bug.cgi?id=18574 Bug 18574] and from previous discussions it always seemed to me that there is quite some overlap between MNG wanters and Seamonkey lovers. I am running in the configuration where MNG is even used to decode PNG images since mid of last year, and since November 2004 or so (libmng 1.0.8?) I didn't have any more display problems at all, and no crashes. For the "first release" I would recommend not replacing the PNG decoder but just to add the MNG/JNG decoder which has fairly low risk. | |||
--[[User:Pweilbacher|Peter Weilbacher (paepse)]] 08:38, 22 Mar 2005 (PST) | |||