Community Forum

'codebase' is not valid attribute of element 'object'

Profile Image 3 Posts 3 Karma
twells posted this 27 July 2012

When I add this code for ScriptX to the body of my web page I get the following error message from Visual Studio 2010;

     <object id="factory" style="display:none" classid="clsid:1663ed61-23eb-11d2-b92f-008048fdd814" codebase="http://prd-pn-app/applications/_tbin/ScriptX/smsx.cab#Version=7,0,0,8"></object>

Validation (HTML5): Attribute 'codebase' is not valid attribute of element 'object'.

Does this matter and if so how do I fix it?

Thanks!

Profile Image 189 Posts 189 Karma
Jerry posted this 01 August 2012

>> Validation (HTML5): Attribute 'codebase' is not valid attribute of element 'object'. <<

Yep, that's what the spec seems to say. Ho hum. I'd ignore it for now, but check out the 'data' attribute for a bit of future-proofing.

Profile Image 3 Posts 3 Karma
twells posted this 23 January 2013

I was pulled off to other things but I'm back.  Reading the w3c spec for object the attribute "classid" is not supported for html5 and has no replacement.  The attribute "codebase" is unsupported and has no replacement.  As far as I can tell both tags are consolidated into the "data" attribute or perhaps the classid is passed via <param>.

Has anyone sucessfully done an html5 implementation of the object?  I'm perfectly willing to experiment but if the proper way has already been discovered I'd like to avoid duplication of effort.  Not that I have any complaints - I'm using the free version so I'm getting more than I paid for.

Thanks in advance for any help.

Profile Image 189 Posts 189 Karma
Jerry posted this 26 January 2013

Bearing mind how many 'object' tags there must be on existing content across intranets and the public web, I doubt if the W3C would be so stupid as to deprecate those tags without introducing an 'approved' replacement.

 

Having said that, corporate/commercial decision-making is not always evident in standards groups' creations.

 

Is this really, really an issue for you?

Post Edited 26 January 2013

Profile Image 3 Posts 3 Karma
twells posted this 29 January 2013

This isn't enough of an issue to want someone to burn a lot of time on.  As it is right now the factory object is still working and when it is published the browser doesn't display any errors.  I just had a bug with Visual Studio 2010 that was making this look like it was a problem but when the bug ironed out the VS stopped complaining so I guess what I'm saying is; thanks for the response and it is all good now.