Spudhead
04-24-2006, 03:16 PM
This is getting silly.
So Microsoft release their IE update, and suddenly every <object> tag gets a little grey box around it, inviting users to click to activate. Way to render half a billion sites all but useless, Bill :mad:
Now we're frantically trying to find out how to get rid of it. Not a problem, say Macromedia (http://www.macromedia.com/devnet/activecontent/). Simply include an external JS file that writes your <object> tag for you, and you're back in control of your user interface. Woohoo indeed.
And then you try to work out what, exactly, your <object> tag should look like. And, being a forward-thinking little web developer, you want it to be XHTML. You want your badge from the W3C. And... you can't.
There is no way to code an embedded object that displays properly in the major browsers AND validates XHTML.
Well, none without a whole raft of issues of their own. Drew McLellan's Flash Satay (http://www.alistapart.com/articles/flashsatay/) approach is probably the tidiest, from a markup perspective, but you lose the auto-updating and streaming capabilities - which can be critical in some applications. Or you can use Geoff Stearns' FlashObject (http://blog.deconcept.com/flashobject/). Which is fine if you don't mind being reliant on users having javascript enabled, or indeed on slapping <script> tags all over your otherwise-pristine XHTML any time you want to embed a bit of Flash or Quicktime.
This SUCKS. If I'm wrong, then it only sucks a little and I'll shuffle off and continue my rant out of the public eye. But I think, from what I've read, that I'm right. And if this were a less polite forum, there'd be a whole string of less-than-wholesome words appearing right now. Most of them, sadly but predictably, followed by the word "Microsoft". :( :( :mad:
Opinions? Advice? Comments?
So Microsoft release their IE update, and suddenly every <object> tag gets a little grey box around it, inviting users to click to activate. Way to render half a billion sites all but useless, Bill :mad:
Now we're frantically trying to find out how to get rid of it. Not a problem, say Macromedia (http://www.macromedia.com/devnet/activecontent/). Simply include an external JS file that writes your <object> tag for you, and you're back in control of your user interface. Woohoo indeed.
And then you try to work out what, exactly, your <object> tag should look like. And, being a forward-thinking little web developer, you want it to be XHTML. You want your badge from the W3C. And... you can't.
There is no way to code an embedded object that displays properly in the major browsers AND validates XHTML.
Well, none without a whole raft of issues of their own. Drew McLellan's Flash Satay (http://www.alistapart.com/articles/flashsatay/) approach is probably the tidiest, from a markup perspective, but you lose the auto-updating and streaming capabilities - which can be critical in some applications. Or you can use Geoff Stearns' FlashObject (http://blog.deconcept.com/flashobject/). Which is fine if you don't mind being reliant on users having javascript enabled, or indeed on slapping <script> tags all over your otherwise-pristine XHTML any time you want to embed a bit of Flash or Quicktime.
This SUCKS. If I'm wrong, then it only sucks a little and I'll shuffle off and continue my rant out of the public eye. But I think, from what I've read, that I'm right. And if this were a less polite forum, there'd be a whole string of less-than-wholesome words appearing right now. Most of them, sadly but predictably, followed by the word "Microsoft". :( :( :mad:
Opinions? Advice? Comments?