Closed Bug 156199 Opened 22 years ago Closed 22 years ago

<object> alternative absent when data type not specified

Categories

(Core Graveyard :: Plug-ins, defect, P3)

Product:
Core Graveyard
Component:
Plug-ins
Platform:
x86
Linux
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED DUPLICATE of bug 157554
Milestone:
mozilla1.2beta

People

(Reporter: Jos.vandenOever, Assigned: peterl-bugs)

References

(
URL
)

Details

(Whiteboard: [object]) 

When in an XHTML document, an object is specified with an unknown content type,
the alternative is not rendered, unless the optional type="" tag is present.

Version: Mozilla 1.0
Yep.  Confirmed with a current trunk build.
Assignee: Matti → beppe
Component: Browser-General → Plug-ins
QA Contact: asa → shrir
Status: UNCONFIRMED → NEW
Ever confirmed: true
This is probably a dup of another OBJECT tag bug. The core problem is that our
code doesn't do anything but attempt to startup a plugin in any case where the
mime-type needs to be fetched from the HTTP header. If we get an error, we just
return from |nsPluginStreamListenerPeer::OnStartRequest|. We do not call
|CantRenderReplaceElement| for alternate renderings nor do do we replace with
iframe/image frames (bug 153920).
milestine,priority and eng
Assignee: beppe → peterl
Priority: -- → P3
Whiteboard: [object]
Target Milestone: --- → mozilla1.2beta
milestone,priority and eng

*** This bug has been marked as a duplicate of 157554 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
mass duplicate verifications . For filtering purposes, pls use keywd
"massdupverification"
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.