234649 - MNG support should be an installer option

Status: RESOLVED WONTFIX

(Firefox :: Installer, enhancement)

Description

[Grey Nicholson (they/them)]

User-Agent:       
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.6) Gecko/20040206 Firefox/0.8

If MNG can't be supported by default in Firefox, it should be an option during
install (like an extension bundle)

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Comment 1

[José Jeria]

http://stud4.tuwien.ac.at/~e0225227/

Does average users know what mng is? 

Comment 2

[Glenn Randers-Pehrson]

That's how we've set up Firefox and Mozilla at mngzilla.sf.net.  We use the
enable-image-decoders option:

To add MNG support:
ac_add_options --enable-image-decoders=mng,default

to add MNG support and delete libpng (PNG support will be
provided via libmng):
ac_add_options --enable-image-decoders=mng,gif,jpeg,bmp,xbm

To get default behavior (no MNG, PNG provided by libmng):
omit the option.

Hardware and OS to "all"

Is this a dupe of bug#18574?  Maybe not because this is a FF bug.

Comment 3

[Grey Nicholson (they/them)]

(In reply to comment #1)
> http://stud4.tuwien.ac.at/~e0225227/
> 
> Does average users know what mng is? 
> 

I suspect most don't know what W3C standards compliance is, either. Besides,
"average users" should use the "Standard" install option.

Comment 4

[Glenn Randers-Pehrson]

Taking bug.

Comment 5

[Glenn Randers-Pehrson]

The "Full MNG-1.06+" patch that I attached to bug #18574 yesterday accomplishes
this.  If you prefer, you can retrieve the patch (zipped, gzipped, or bzipped)
from the "DOWNLOAD" area at http://mngzilla.sf.net

Be sure to use the "-p0" patch option and to run "autoconf" afterwards.  Then
use the configuration option described above in comment #2.

Comment 6

[Pham]

I've never seen an mng and they aren't that great.
you should dupe this to bug 214269 or wontfix it

Comment 7

[Glenn Randers-Pehrson]

I don't see how your conclusion follows from your never having
seen one.

Look at the "mayflower" MNG at
ftp://swrinde.nde.swri.edu/pub/mng/images/
using a MNG-capable browser.

It's about 4kbytes.  As a GIF it's hundreds of kbytes.

About this being a dupe of bug #214269: Does anyone have data telling
if the MNG extension supports MNG throbbers?  If it doesn't, then this
isn't a dupe because MNG support has to be bound into the internal libimg2
support, as it is at mngzilla.

Comment 8

[Grey Nicholson (they/them)]

(In reply to comment #6)
> I've never seen an mng and they aren't that great.
> you should dupe this to bug 214269 or wontfix it

The reason MNGs aren't common is because browsers can't display them; MNG is a
W3C standard, so it *should* be available.

I think it's really too early to say that this can't be fixed; could the MNG
Support for Firefox extension not simply become an extenson bundle?

Comment 9

[Michael Lefevre]

> MNG is a W3C standard

er... no it isn't. PNG is, but not MNG.

Comment 10

[Pham]

I don't know why MNG was removed, but I think that this shouldn't be an
installer option. MNG should just go with Firefox when it's good enough(as well
as the other svg installer bug)

Comment 11

[Simon Paquet [:sipaq]]

MNG can't be an installer option. If it is incorporated back into the tree it
will be a runtime option. Marking WONTFIX.

Comment 12

[Glenn Randers-Pehrson]

Why can't it be an installer option?  There is a configuration option

   --enable-image-decoders=png,gif,jpeg,bmp,xbm

To "optionally" install MNG, just add "mng" to the list.  To remove PNG
and have the MNG decoder provide PNG support, remove "png" and add "mng".

Reopening.

Comment 13

[Simon Paquet [:sipaq]]

sorry, I mixed something up. 
Because of the reasons you stated, mng will be a compile-time option if it
incorporated back into the tree. Making it an installer option would only be
possible if it could be integrated on runtime. Since this isn't possible, this
bug is WONTFIX.

See also bug 234648 for a similar problem.

Comment 14

[Grey Nicholson (they/them)]

Why can't the MNG support extension just be made into an extension bundle?

Comment 15

[Michael Lefevre]

I'm not sure it should or will be an installer option, but it can indeed be
integrated at run time.  I'm not sure the current code has been packaged as an
extension, but it's certainly been done previously, and is technically possible.

Comment 16

[Jeremy Hannon]

(In reply to comment #13)
> sorry, I mixed something up. 
> Because of the reasons you stated, mng will be a compile-time option if it
> incorporated back into the tree. Making it an installer option would only be
> possible if it could be integrated on runtime. Since this isn't possible, this
> bug is WONTFIX.

I can understand if this is a WONTFIX, but I don't believe you understood the
original point.  The mng code has been bundled into an extension for Firefox,
and can be download through the texturizer.net site.  This could be done though
the installer.  It may not be there by default, for the same reason the code was
originally removed (size), but I just wanted to make sure you WONTFIXed it
understanding the request completely.