Groups | Blog | Home
all groups > flash (macromedia) > august 2004 >

flash (macromedia) : embedding flash with XHTML standards? Flash Satay


limeybloke
8/10/2004 11:36:53 PM
Hi can anyone shed light of this subject?

Flash Satay
http://www.macromedia.com/devnet/mx/dreamweaver/articles/flash_satay.html

There's been a few reports on the web, suggesting this technique, however you
get this terrible, 'no image' area for a split second while it loads the whole
movie, unless you create movies within movies it doesnt work. And doing that is
a big pain when the site already has multiple movies loading.

can anyoen suggest how to embed flash into a XHTML standards web page?
alexxxita
9/14/2004 10:45:50 PM
Same here.

Flash Satay was suppose to rersolve my problem but it is not. When using
XHTML, the swf take a bit to load and you can see a red X when you enter the
page. I use the Macromedia Flash Satay article principle: using a swf container
of 1k to load the real swf but still it does not work. We can see the red X
when you load the page.

Can you help?

example: http://softwares.visicommedia.com/en/

Thank you

Jeckyl
9/15/2004 8:54:35 AM
don't bother with XHTML ... if you follow the standard for XHTML then your
web page will fail on many many browsers and platforms.

you basically havea choice .. be strictly XHTML conforming .. or have a site
that actually works. You cannot have both. Truct me .. I've battled it for
months. There are browsers that just chuck up their hands with the doctypes
etc required for XHTML and refuse to work.

The best 'standard' I've found for getting your site to work with most
browser is HTML 4.0

This gives me a basic HTML page like this...

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
"http://www.w3.org/TR/html40/loose.dtd">
<html>
<head>
<title>Movie1</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body bgcolor="#FFFFFF">
<center>
<object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000"

codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.ca
b#version=XX,XX,XX,XX"
id="XXXXXX" width="XXX" height="XXX">
<param name="movie" value="XXXXXX.swf">
<param name="bgcolor" value="#FFFFFF">
<param name="quality" value="high">
<param name="allowscriptaccess" value="samedomain">
<embed type="application/x-shockwave-flash"
pluginspage="http://www.macromedia.com/go/getflashplayer"
width="XXX" height="XXX"
name="XXXXXX" src="XXXXXX.swf"
bgcolor="#FFFFFF" quality="high"
swLiveConnect="true" allowScriptAccess="samedomain"
[quoted text, click to view]
</object>
</center>
</body>
</html>

with XXX's filled in appropriately.

alexxxita
9/20/2004 6:39:05 PM
Thank but we know about HTML transitional code. We are looking for a solution
to the new standard : XHTML.

If Macromedia is using XHTML on its site without problems, there must be a
way. They should share the info with everyone since that might affect their
product popularity.

alexxxita
9/21/2004 12:30:50 AM
I understand what you saying. It's just that many designers have the obligation to use those new standards. I find it just unbeleivable that there is no work around. Maybe there is none for now.

Jeckyl
9/21/2004 9:29:43 AM
I have found from bitter experience that XHTML does NOT for many browser /
platforms. Ask your self why on earth do you reallly NEED to use it ..
isn't it better to havea web site that actually works,rather than one that
satisfies a standard that is not fully supported?

Did you look at www.macromedia.com .. it says it is actually XHTML
transitional .. but it does not pass XHTML standard validators .. because if
it did, it would not work.

If you save the HTML source for the www.macromedia.com page (cannot directly
submit the url to checkers) then you get these results

http://validator.w3.org/check
[quoted text, click to view]
Doctype: XHTML 1.0 Transitional
Errors: 98
This page is not Valid XHTML 1.0 Transitional!
[quoted text, click to view]

http://www.htmlhelp.com/tools/validator/upload.html
got LOTS of errors on the page

http://schneegans.de/sv/Default.aspx
threw up its hands at it

It really isn't worth the effort to be XTHML compliant if you want your web
site to actually be usable.

Jeckyl
9/21/2004 10:40:01 AM
I actually found (I am trying to remember the details) that just using XHTML
standard (I don't think it was transitional) caused one browser to simply
not display the page correctly .. in one case it would not position the SWF
correctly on the web page if I used XHTML .. but when I changed back to
earlier standard for the doctype, it works. Its a weird world out there in
internet browser land .. quite removed from the theoretical standards for
web pages.

For example, did you know that if you put a long comment tag in an html page
and view it on one of the Mac browsers (think it was IE), then that would
disable scrolling of a swf file in a web page .. if you split the comment
tag into smaller pieces, it works fine. Weird .. but that's life.

All the best in getting a solution for a fully compliant / valid XHTML page
that actually works on Mac and PC and with major browsers like IE, Netscape,
Safari etc etc. If you find a solution, please let us all know !!!

AddThis Social Bookmark Button