Commenting on: AJAX3D - cross-browser html object how to
Comments
Beware of trying to do the right thing and use the OBJECT tag in some Web2.0 apps. In particular, Myspace strips out OBJECT tags (and all Javascript) from all user-contributed content, but allows the EMBED tag. Thus Myspace is training a whole generation of HTML coders to use the old construct, which is likely to remain supported by the major browsers and used by a large amount of content.
I have updated my favorite way of using the html object tag, still not including embed, in latest web3d blog.
I am still refusing to use the old html embed element. Sure it probably works to a limited extent in most web browsers, but is ultimately doomed for use in the wild - especially when the time finally comes that coders of web browsers agree how to handle the html/xhtml object element, attributes, and params.
One aspect is me wanting the ability to specify the X3D player, just as I wish to specify the host web browser. With html/xhtml hosts, it is just simple differences, some based on security and history, that make it just a bit harder for us to get the good stuff in there using othewise reliable modern html/xhtml host browsers.
X3D applies in many different host platforms, and each will have small differences. It may be that no single web3D X3D content delivery tool will ever dominate the www user base, or even be the overwhelmingly author-preferred X3D player out there in the wild. In that case, a web author shouldn’t worry much about which host/player combo represents their object, but probably still must learn some basic capabilities and preferences of the host, and of the host of the host, and,, as you point out, on up to the ultimate content host, then code accordingly.
Best Regards,
Joe
Post your comments
Note: All comments are moderated by the webmaster. Until then, the comment won't appear on the entry. Thanks for waiting.