...

View Full Version : -FIXED- Embed Tag



JustinMs66
05-28-2007, 02:27 AM
W3 dosn't like the <embed> tag. But i used it with all proper formats!
why dosn't it like that? and how do i fix it?

-edit-
i fixed it by using javascript :-) FIXED!!!

_Aerospace_Eng_
05-28-2007, 03:31 AM
Can you show us the javascript you are using? The embed tag was never part of the standard btw.

felgall
05-28-2007, 04:06 AM
There is no need to use the proprietary embed tag at all. You may need different object tags for IE and other browsers but you can nest one inside the other.

Adding invalid HTML markup using JavaScript doesn't make the HTML valid, it just means that you have hidden invalid code from the validator and that the final code still wouldn't validate.

rmedek
05-28-2007, 05:22 AM
There is no need to use the proprietary embed tag at all. You may need different object tags for IE and other browsers but you can nest one inside the other.

I disagree, especially for embedding Flash content. This post by the author of SWFObject puts it quite well, I think: http://blog.deconcept.com/2006/08/16/embedding-flash-content-using-web-standards-yes-again/

IMO, this is a case of compliancy to web standards overlooking the reality of browser capability at the moment.

felgall
05-28-2007, 10:26 AM
See http://alistapart.com/articles/byebyeembed for a version that works on all browsers released in the last 10 years and which does not require an embed tag. You just need one object tag for IE and a second object tag foer standard compliant browsers.

rmedek
05-28-2007, 10:45 AM
Yes, but the article I linked to addressed several areas where using strictly object runs into issues:




“Click to activate” in IE. The only way to get around this is to use Javacript.
No plugin detection. If I have Flash Player 6 installed, and I visit a site that uses Flash 9 content, my player will go ahead and try to play that swf anyway. I could end up seeing half of the content, or broken content, or who knows what. Do you really want to show your users broken content?
Issues in older Safari versions: Safari pre 1.2 will completely ignore param tags, which are often used to pass information to the plugin. This means broken content for your users.
Support for the object tag varies widely from browser to browser. Do you think that just because you work around all the quirks in the 3 main browsers today, it will still work when the next new browser is released?
Using Flash Satay or other ‘object only’ methods will not stream your Flash movies to the user - this means extra work for you in creating a ‘loader’ swf
JAWS will ignore it.


I'm all for following w3c recommendations but I still don't think browser support for the object tag is stable enough to recommend using object only.



EZ Archive Ads Plugin for vBulletin Copyright 2006 Computer Help Forum