Bug 83970 – HTML object tag codebase attribute is not used as a base one for data URL

• Component: DOM
• Status: RESOLVED WONTFIX

HTML object tag  codebase attribute can not be rendered.

I must clarify that the picture is exist, you can directly use the 

   URL http://testfest.openmobilealliance.org/XHTML_Suite_3/Content/Flower_120x160.gif to access.

*** Bug 82705 has been marked as a duplicate of this bug. ***

also I the opera can render this feature as normal.

[Alexey Proskuryakov]

Created attachment 137353 [details]
test case

Attaching test case from duplicate.

[Alexey Proskuryakov]

Does this cause issues on any real web site? This is a very unusual way to draw an image.

(In reply to comment #4)
> Does this cause issues on any real web site? This is a very unusual way to draw an image.

yes this website is from the open mobile alliance. 

you can test it  through these steps. 

1. access  http://testfest.openmobilealliance.org/  
2. access  3c. XHTML TS 3 (TFP 2009/07/31)
3. access  •object_Data with Codebase

IE , and Chrome can not render, but firefox and opera can render

[Alexey Proskuryakov]

This is a test case, not an actual site users would go to.

As long as we're compatible with IE, the vast majority of browsers have interoperable behavior, so a very strong reason would be needed for us to change. I doubt that such an argument can exist in this case - using codebase argument value as base URL just seems like a bug in Firefox. I see no reason why location of code would be related to location of data.

(In reply to comment #7)
> This is a test case, not an actual site users would go to.
> 
> As long as we're compatible with IE, the vast majority of browsers have interoperable behavior, so a very strong reason would be needed for us to change. I doubt that such an argument can exist in this case - using codebase argument value as base URL just seems like a bug in Firefox. I see no reason why location of code would be related to location of data.


Why codebase should replace base value ,you can refer W3C specification

[Alexey Proskuryakov]

I checked the specification, and don't see anything like this. The specification is at <http://dev.w3.org/html5/spec/single-page.html>.

[Ian 'Hixie' Hickson]

According to the HTML standard (http://whatwg.org/html) the codebase attribute does nothing, as far as I can tell. Its only effect is on the .codeBase IDL attribute, which just reflects the codebase="" content attribute, that's it.

http://www.w3.org/TR/1999/REC-html401-19991224/struct/objects.html


I have read the specification on this URL page .
You can see this section:

Attribute definitions

classid = uri [CT] 
This attribute may be used to specify the location of an object's implementation via a URI. It may be used together with, or as an alternative to the data attribute, depending on the type of object involved. 
codebase = uri [CT] 
This attribute specifies the base path used to resolve relative URIs specified by the classid, data, and archive attributes. When absent, its default value is the base URI of the current document. 
codetype = content-type [CI] 
This attribute specifies the content type of data expected when downloading the object specified by classid. This attribute is optional but recommended when classid is specified since it allows the user agent to avoid loading information for unsupported content types. When absent, it defaults to the value of the type attribute. 
data = uri [CT] 
This attribute may be used to specify the location of the object's data, for instance image data for objects defining images, or more generally, a serialized form of an object which can be used to recreate it. If given as a relative URI, it should be interpreted relative to the codebase attribute. 
type = content-type [CI] 
This attribute specifies the content type for the data specified by data. This attribute is optional but recommended when data is specified since it allows the user agent to avoid loading information for unsupported content types. If the value of this attribute differs from the HTTP Content-Type returned by the server when the object is retrieved, the HTTP Content-Type takes precedence. 
archive = uri-list [CT] 
This attribute may be used to specify a space-separated list of URIs for archives containing resources relevant to the object, which may include the resources specified by the classid and data attributes. Preloading archives will generally result in reduced load times for objects. Archives specified as relative URIs should be interpreted relative to the codebase attribute. 
declare [CI] 
When present, this boolean attribute makes the current OBJECT definition a declaration only. The object must be instantiated by a subsequent OBJECT definition referring to this declaration. 
standby = text [CS] 
This attribute specifies a message that a user agent may render while loading the object's implementation and data. 


As far as I know, webkit, can support htlm4.01, and partial HTML5 is suported

I think the webkit should support html4.01 specfication . And if need develop HTML5 fearture further, it should also compatible with HTML4.01

As many pages are writed based on HTML4.01, Does webkit can not support HTML4.01 but only support HTML5 ??????????????

[Alexey Proskuryakov]

HTML5 supersedes all previous versions.

If you think that this is a mistake in HTML5, please get HTML5 changed (this is very doable when you provide strong reasons), and re-open the bug once it specifies the proposed behavior. Otherwise, it's just a bug in Firefox.

Please also note that WebKit does not support XHTML mobile profiles (I'm saying that because the test case has xhtml-mobile DTD). That should not be of importance in this particular case, because the difference is observable with DTD removed, too.

First I have not say that it is a mistake in HTML5 . And I say that webkit should compatible with html4.01.  If webkit can not render codebase ,why it is write codebase relative code in it?  
You just think it is a mistake in firefox, I feel a little pity .

I am just a reporter, have no right to tell you what to do. How to deal with this bug ,depend on your organization.  And I really hope webkit organization can fix this bug.