Image decoders handling more than one mimetype

RESOLVED FIXED in M16

Status

()

P3
normal
RESOLVED FIXED
19 years ago
18 years ago

People

(Reporter: tor, Assigned: pnunn)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

19 years ago
Currently image decoder components register a single mimetype,
which libimg uses to determine what streams to send its way (or
at least this is the way things are supposed to happen #41333).
The MNG component I've written handles both MNG (video/x-mng)
and JNG (image/x-jng) images (actually it can also handle
image/png, but that's another discussion).  We need some way
for a decoder to register multiple mimetypes.
(Reporter)

Updated

19 years ago
Blocks: 18574
(Assignee)

Updated

19 years ago
Status: NEW → ASSIGNED
Target Milestone: --- → M16

Comment 1

19 years ago
M16 has been out for a while now, these bugs target milestones need to be 
updated.
(Reporter)

Comment 2

18 years ago
Solved by registering two progids for the mng decoder.

Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED
Should this be documented somewhere?  Sounds like we need imglib extension
documentation ...
(Assignee)

Comment 4

18 years ago
Matty:
You volunteering? Super, we could use the help.
-p
Well, I don't really know the first thing about imglib.  All I'm really saying
is that we should make sure this little piece of imglib folklore is not lost.

Updated

18 years ago
QA Contact: elig → tpreston
You need to log in before you can comment on or make changes to this bug.