Closed Bug 108946 Opened 23 years ago Closed 19 years ago

OBJECT tag needs to handle invalid data attribute

Categories

(Core :: Layout, defect, P3)

defect

Tracking

()

RESOLVED FIXED
Future

People

(Reporter: rubydoo123, Assigned: peterlubczynski-bugs)

References

()

Details

(Keywords: testcase, Whiteboard: [PL2:P3][similar to bug 76594])

Attachments

(4 files)

This is extracted from the above URL. In the above URL, this is test #4 The CSS for the test is this: <style type="text/css"> span {background-color: #fcc} object span {background-color: yellow } object {border: thin red solid}</style> The actual test is this: <P>The type attribute says it is an unknown type, and it really is. You should see the alternate text instead (which starts "If you can read this,") <object type="image/foo" data="foo.foo"> <span>If you can read this, the browser has correctly ignored an image of unknown type. (This text should have a yellow, not pink, background, and have a red border)</span> </object> I will attach screen grabs for comparison shopping
Attached image MSIE6.0 screen grab (deleted) —
Attached image Opera5.2 screen grab (deleted) —
Attached image NSCP4.x screen grab (correct) (deleted) —
Attached image Mozilla6.2 screen grab (deleted) —
Ironically, NSCP4.x display the test correctly!
I bad! I copied the wrong code, here is the code for this one: <p> A missing image: you should see the alternate text (which says "Correct!): <object data="missing.gif"><span>Correct!</span></object>
Summary: Object element is not processed correctly when type is unknown → Object element is not processed correctly when missing gif
This is another example of the object not rendering the nested content, this is test #7 in the above URL: <p>The type attribute says it's a gif, but it isn't. Since the 'type' attribute is only advisory, it should not try to display the image, but display the alternate text instead (which starts "If you can read this,"): <object type="image/gif" data="foo.foo"> <span>If you can read this, the browser has correctly handled the case of an image that it couldn't handle despite the type attribute saying it was a type it could handle.</span> </object>
This is similar to bug 76594 but that one deals with the EMBED tag. For EMBED tag we should always render the plugin. However, for the OBJECT tag, we need to test if the URL is valid and if not, render the contents. The APPLET tag shouldn't do anything. This may be a difficult to fix for images and documents. Beth, what to do if the URL (data attribute) is missing?
Assignee: peterl → peterlubczynski
Keywords: testcase
OS: Windows 98 → All
Priority: -- → P3
Summary: Object element is not processed correctly when missing gif → Object element is not processed correctly when type is unknown
Whiteboard: [similar to bug 76594]
Target Milestone: --- → mozilla0.9.7
Status: NEW → ASSIGNED
Summary: Object element is not processed correctly when type is unknown → OBJECT tag needs to handle invalid data attribute
funny you should ask, we are working on that issue now in the WG -- I'll keep you posted
Component: Plug-ins → Layout
Keywords: mozilla1.0
Hardware: PC → All
Target Milestone: mozilla0.9.7 → mozilla1.0
Mozilla 0.9.8+ Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:0.9.8+) Gecko/20020215 I'm using the object tag to present SVG in a HTML doc and offer a png screen shot to non enabled browsers. The code being used is pasted below and it works except in Opera, Opera is picking up the SVG image. If I change from data to userid then all browsers get the png, even the SVG enabled. <object style="background-color:#99ffff; overflow: hidden; -moz-border-radius:5px; border: Fuchsia 5px ridge;" data="xmlimages/moz.xml" type="application/xhtml+xml" width="180px" height="86px" ><img src="images/toe.gif" alt="" border="2"/ > </object> To see this working go to either http://www.skeeter-s.com/svg/object-test_1.html or to the start page http://www.skeeter-s.com/svg/ It too contains an SVG image that is coming in via the object tag. To view the SVG one needs the right browser of course. Any ideas here?
Moving Netscape owned 0.9.9 and 1.0 bugs that don't have an nsbeta1, nsbeta1+, topembed, topembed+, Mozilla0.9.9+ or Mozilla1.0+ keyword. Please send any questions or feedback about this to adt@netscape.com. You can search for "Moving bugs not scheduled for a project" to quickly delete this bugmail.
Target Milestone: mozilla1.0 → mozilla1.2
Depends on: 157554
Whiteboard: [similar to bug 76594] → [PL2:P3[similar to bug 76594]
Target Milestone: mozilla1.2alpha → mozilla1.2beta
Whiteboard: [PL2:P3[similar to bug 76594] → [PL2:P3][similar to bug 76594]
Target Milestone: mozilla1.2beta → Future
Depends on: 96976
I just loaded the test case in Mozilla 1.5 (Win2K) and all tests were displayed correctly, including test #4.
everything that was left here should now be fixed by bug 1156.
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: