Closed Bug 65455 Opened 25 years ago Closed 25 years ago

Object tag without type attribute does not display the alternative content

Categories

(Core :: Layout, defect)

defect
Not set
minor

Tracking

()

RESOLVED WORKSFORME
mozilla1.0

People

(Reporter: ejones, Assigned: serhunt)

References

()

Details

(Keywords: testcase)

Attachments

(1 file)

From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.17 i686; en-US; 0.7) Gecko/20010105 BuildID: 2001011406 An object tag that is specified without the type attribute will not display the alternate content contained in the tag. For example: <object><p>This is some alternative content</p></object> The above line will not display in recent builds of Mozilla. In older builds (Mozilla 0.7 for example) it caused a crash. According to section 13.3.1 of the HTML4 spec, it should display the text: A user agent must interpret an OBJECT element according to the following precedence rules: 1. The user agent must first try to render the object. It should not render the element's contents, but it must examine them in case the element contains any direct children that are PARAM elements (see object initialization) or MAP elements (see client-side image maps). 2. If the user agent is not able to render the object for whatever reason (configured not to, lack of resources, wrong architecture, etc.), it must try to render its contents. Reproducible: Always Steps to Reproduce: 1. View the test case in a recent Mozilla build. Actual Results: No content is displayed. Expected Results: The text "This line should be displayed in Mozilla." should be displayed. I have tested this on Linux at the moment, but I'm going to reboot and test it on Windows in a moment as well. I am also about to attach a test case.
COnfirmed: Platform: PC OS: Linux 2.2.16 Mozilla Build: 2001011508 Marking NEW.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: testcase
OS: Linux → All
Reassigning QA Contact for all open and unverified bugs previously under Lorca's care to Gerardo as per phone conversation this morning.
QA Contact: lorca → gerardok
qa contact updated.
QA Contact: gerardok → bsharma
changing the component to 'Layout'.
Assignee: clayton → karnaze
Component: HTML Element → Layout
QA Contact: bsharma → petersen
Target Milestone: --- → mozilla0.8.1
Assignee: karnaze → buster
Target Milestone: mozilla0.8.1 → mozilla1.0
Reassigning to Buster's list and marking mozilla1.0
*** Bug 67133 has been marked as a duplicate of this bug. ***
Reassigning to av since bug 67133 was assigned to him. See some debugging comments on that bug (which didn't reach the conclusion that this was the problem for quite a while).
Assignee: buster → av
I think all this needs is a simple fix to the logic in nsObjectFrame::Reflow.
Keywords: mozilla1.0
some related work been done in bug 797 might be useful
*** Bug 81846 has been marked as a duplicate of this bug. ***
The testcase WFM using Mac/2001082104. The testcase, however, lacks both a type and a data attribute. Adding a type attribute still results in a WFM condition for this bug. Would someone verify and mark this WFM? I recently opened bug 96976 about IFRAMEs and OBJECTs not displaying alternate content when Mozilla cannot fetch the data/src attribute URI.
Please note that although the first OBJECT testcase does display the alternate text, an equivalent IFRAME testcase (<iframe>foo</iframe>) does not.
WFM with Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.3+) Gecko/20010821
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
*** Bug 67133 has been marked as a duplicate of this bug. ***
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: