gecko handles OBJECT incorrectly for native image types

VERIFIED FIXED in M4

Status

()

defect
P2
normal
VERIFIED FIXED
21 years ago
20 years ago

People

(Reporter: newt, Assigned: serhunt)

Tracking

Trunk
x86
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [OBJECT], )

Reporter

Description

21 years ago
I'm using the Win32 Gecko binary downloaded today (16 Dec 98) from
developer.netscape.com; build date was 11 Dec 98, I think, but "about:"
doesn't work.

On the page above (which will be replaced by a fully validated HTML 4.0
Transitional version as of early 17 Dec 98 PST), there are several
OBJECT elements that refer to various image types.  In most cases the
outer OBJECT points at a PNG, the inner OBJECT a GIF or JPEG, and inside
that (the inner OBJECT's contents) is an IMG PNG or GIF or JPEG.

Regardless of whether this version of Gecko has native PNG support, it
unquestionably has native GIF and JPEG support and should therefore,
according to the HTML 4.0 specification, render the OBJECT images (one
of them) as an image, not as a blank "OBJECT" box.  Note also that if
a PNG plug-in exists on the same system but outside the Gecko installation
tree (in fact, on a completely separate drive), that plug-in will be
invoked--and whatever you guys think, I don't believe that's proper
behavior (i.e., if I want the plug-in used by Gecko, I'll install it
under Gecko myself).  As it happens, the PNG Live 2.0b5 plug-in crashes
Gecko.

Btw, an alternate, strict HTML 4.0 version (using CSS) is available at:
	http://www.cdrom.com/pub/png/pngs-strict.html
as of tonight sometime.  The PNG Live 2.0b5 plug-in is available via a
link on this page, under the Netscape Navigator entry:
	http://www.cdrom.com/pub/png/pngapbr.html

Updated

21 years ago
Assignee: rickg → michaelp

Comment 1

21 years ago
I think this one is yours. Enjoy.

Updated

21 years ago
Assignee: michaelp → amusil
Component: Parser → Plug-ins

Updated

21 years ago
Assignee: amusil → av
Assignee

Updated

21 years ago
Status: NEW → ASSIGNED

Comment 2

21 years ago
Don't forget to implement the attribute TABINDEX for element OBJECT.

Comment 3

21 years ago
Setting all current Open/Normal to M4.
OBJECT doesn't seem to be supported at all for displaying images.  The page
http://www.rpi.edu/~randeg/smiles.html
makes it clearer, since it has "No." for alternative content.

Comment 5

21 years ago
per leger, assigning QA contacts to all open bugs without QA contacts according
to list at http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser
Assignee

Updated

21 years ago
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Assignee

Comment 6

21 years ago
Support for images in object tag is implemented now
Reporter

Updated

21 years ago
Status: RESOLVED → REOPENED
OS: Windows 95 → Linux
Reporter

Comment 7

21 years ago
If the OBJECT element *itself* is rendered, its contents (in the container
sense) must be ignored.  The 1999.03.10 fix takes care of rendering OBJECT
images themselves, but it doesn't stop there--an enclosed IMG image will also be
rendered.  In the referenced page above, this shows up as a pair of side-by-side
penguins at the top, one labelled "GIF version!", and also as a pair of
side-by-side icons near the middle of the page ("PNG" on a yellow background and
"GIF" on a blue background).  Please click on either of the two screenshot links
immediately below the penguin(s) for the correct appearance (at least
approximately).
Assignee

Comment 8

21 years ago
I think it does not render IMG image, it goes for the second OBJECT image, which
is obviously wrong, you are right.

Updated

21 years ago
QA Contact: 3849 → 4082
Resolution: FIXED → ---

Comment 9

21 years ago
Per screenshot from test page this still fails as mentioned, march 19 builds
optimized Seamonkey on Linux and PC - Mac has another problem preventing plugins
from loading.  Clearing fixed res.

Updated

21 years ago
QA Contact: 4082 → 3849

Updated

21 years ago
Whiteboard: [OBJECT]
This may now be fixed, except I'm not sure what you mention above about
problems on the Mac.  I think the original problem is fixed - see bug 4441.
Assignee

Updated

21 years ago
Status: REOPENED → RESOLVED
Closed: 21 years ago21 years ago
Resolution: --- → FIXED
Assignee

Comment 11

21 years ago
Marking it fixed for the originally reported problem

Updated

21 years ago
Status: RESOLVED → VERIFIED

Comment 12

21 years ago
Andrew -- you're great! Marking verified.
You need to log in before you can comment on or make changes to this bug.