Hi Ian, I'm not a big fan of that approach - while it will allow your pages to validate - after the javascript has run then the page will still be invalid XHTML.
Unless there is a major reason to be XHTML then I normally use HTML 4.01 - even if only on the pages with flash included. Mark Stanton has written some pretty good comments on this before - http://www.mail-archive.com/wsg%40webstandardsgroup.org/msg00572.html Cheers, Mark On Thu, 23 Sep 2004 02:22:32 +0100, Ian Fenn <[EMAIL PROTECTED]> wrote: > Hi Mark, > > > A bit late maybe but I recently did some browser testing on this: > > http://markl.f2o.org/experiments/flashvars/ > > http://markl.f2o.org/experiments/FlashTransparent/ > > Many thanks! Your results look similar to mine. I've been testing for two > days. Aargh! > > Unfortunately it seems the best solution is to use JavaScript to detect the > existence (and correct version) of flash and then use document.write to > deliver the appropriate object or embed. Only safari seems to have a > problem. > > All the best, > > -- > Ian > > > > ****************************************************** > The discussion list for http://webstandardsgroup.org/ > > Proud presenters of Web Essentials 04 http://we04.com/ > Web standards, accessibility, inspiration, knowledge > To be held in Sydney, September 30 and October 1, 2004 > > See http://webstandardsgroup.org/mail/guidelines.cfm > for some hints on posting to the list & getting help > ****************************************************** > > ****************************************************** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
